Migrating from invoices to payment requests

​

New endpoint, same authentication

​

Currencies with networks

• Inside currency, set iso to the code of the currency you want to receive. If it is a cryptocurrency, also specify the network_name.
• Inside the optional payment_currency, set iso to the code of the cryptocurrency you want the customer to pay. You may also specify the network_name — or omit it and let the customer choose the network themselves.

"currency": "EUR",
"sender_currency": "USDC",

"currency": {
  "iso": "EUR"
},
"payment_currency": {
  "iso": "USDC",
  "network_name": "ethereum"
},

​

Flexible payment lifetime

"timer": true,

"life_time_duration": 3600,

​

Two modes of currency pre-selection

• Standard mode (the default): the customer still sees a page that describes the requested amount, the conversion rate, the processing fee (if you pass the fees to the customer), and the total amount to pay. On the same page, the customer is asked to enter their email address and KYC data (unless you provided it yourself).
• Fixed mode: the customer skips the first step entirely and goes straight to the payment details. The customer’s email address and the KYC data must be provided by you when creating the payment request. This is the closest equivalent of an invoice with timer and sender_currency. The lifespan of a fixed payment request never exceeds 1 hour, because the rate lock timer starts immediately after creation. A fixed payment request generates a crypto address immediately, before any interaction with the customer. If you want to show it to the customer in your own interface, you can find it as payment_details.address in the API response.

"timer": true,
"sender_currency": "USDC",

"rate_mode": "fixed",
"payment_currency": {
  "iso": "USDC",
  "network_name": "ethereum"
},

​

Underpayment tolerance

​

Other changes

• A payment request doesn’t have a title but may still have a description. Similar to an invoice, the customer can find the description in the “Payment details” dialog on the payment page.
• The payment request API accepts url_store — a link that, if provided, will be displayed under the payment form as “Return to merchant”. See Backlinks.
• Unlike an invoice, a payment request cannot be canceled until either the payment arrives or the timer expires.
• There is an option to pass the processing fees to the customer.
• There is an option to limit the currencies available to customers.

​

Migration checklist