Skip to main content
Each product can have one or more payment links. Customers only need the public Anyway URL returned as paymentLinkUrl.
1

Create or open a product

Go to Business → Products and enter the product name, description, price, and currency.
2

Select the payment method

Choose the payment method and complete the requested setup.
3

Copy the Anyway URL

Publish the product and copy its paymentLinkUrl.
Selected payment-link response fields
Use the returned paymentLinkUrl as the checkout base URL. Do not parse or reconstruct its path. You may append URL-encoded query parameters when you need to carry correlation data through checkout.

​
Attach correlation data

Append string-valued query parameters to the payment link you send to a buyer:
Anyway preserves the first string value for each query parameter in the order’s merchantMetadata. The merchant_reference parameter has an additional role: Anyway also promotes it to the top-level merchantReference field, while retaining it in merchantMetadata.
A checkout URL may contain at most 20 distinct query parameter names, and its complete raw query string may be at most 4,096 bytes. merchantReference may be at most 255 UTF-8 bytes. If a parameter name is repeated, Anyway keeps only its first value. Checkout rejects a URL that exceeds these limits.
For the example above, order payloads contain:
Use a URL builder so names and values are encoded correctly. Do not put secrets or raw personal data in these parameters: they are visible to the buyer and may appear in browser history and request logs.

​
What happens at checkout

1

The buyer opens the link

The buyer opens the Anyway payment link.
2

Anyway starts checkout

Anyway creates a checkout attempt and keeps your order reference and metadata attached.
3

The buyer pays

The buyer completes the selected payment flow.
4

Anyway confirms the order

Anyway confirms the payment and creates or updates the corresponding order.
5

The sales record appears in Finance

For platform-collected Card / USD payments, the sale is added to your Finance ledger asynchronously.
If you configure the optional success URL, it must be a valid HTTPS URL. Anyway returns the buyer to it after confirmation and echoes the custom query parameters together with anyway_order_id, status, and the signed callback proof when available. The same correlation fields are available in order webhooks and Merchant API order responses. Verify the order status on your server before delivering high-value goods.
Query parameters and merchantMetadata are buyer-visible input. Use them for correlation and context, not as the sole authorization or pricing decision.
The Products list can filter PUBLISHED, DRAFT, and ARCHIVED items. Use a row’s action menu to publish or archive it. Open a product to edit its name or description, review existing payment links, create another link for a supported payment method, and copy a public URL. After creating a product, the app returns to the Products list and shows a success toast with Copy Payment Link. After adding a link to an existing product, it returns to that product’s overview and shows the same copy action. You can also copy a link from the overview.

​
Safe sharing checklist

  • Share paymentLinkUrl or a derived URL that changes only its encoded query parameters.
  • Keep merchantReference stable and unique in your system.
  • Use webhooks as the server-side payment signal.
  • Make fulfillment idempotent so the same paid event cannot deliver twice.
  • Compare the order amount and currency with your own product record.