Skip to main content
With payment requests, you can let your customers make one-time payments in the cryptocurrency of their choice.
  • Your customer sees a convenient webpage that guides them through the payment process.
  • You receive funds in the currency you requested, regardless of the customer’s payment currency.
  • CryptoProcessing takes care of conversion and edge cases, such as underpayments and overpayments.
Payment request step 1Payment request step 2Payment request step 3
When creating a payment request, you control its behavior by choosing the currency and the lifespan. The funds received via a payment request may be sent back via a refund, initiated either automatically or manually by you.

​
Currency selection

When creating a payment request, you specify the expected currency — the cryptocurrency you want to receive. However, your customer may find it convenient to choose another payment currency – the cryptocurrency in which the actual transaction will be made. If the payment currency is different from the expected currency, CryptoProcessing takes care of converting the funds automatically. This means that you receive the exact amount of the exact currency you requested. When doing so, CryptoProcessing applies a rate lock of 1 hour. Alternatively, you can choose a set currency (and/or network) your customer will be able to pay in. We recommend only doing this if your customer has already chosen their preferred currency somewhere on your site. The parameter is only available via API, see /payments/v1/requests. The payment currency is also used in refunds.
Currency selection

​
Lifespan and rate lock

There are two time constraints applicable to a payment request.
  • The lifespan is configured when you create a payment request. The customer’s transaction must be both created and confirmed within this lifespan, or the payment request expires.
  • The rate lock happens if the customer chooses the payment currency different from the currency you requested. CryptoProcessing locks the currency rates for 1 hour. The customer’s transaction must be both created and confirmed within this period, or the payment request expires. Note that if you forced selection of a payment currency, the rate lock will start immediately. This behavior is only available via API, see /payments/v1/requests.
When the payment request has less than 1 hour left before expiration, whatever its cause is, the customer will see a countdown timer on the webpage.
Countdown timer

​
Further reading

Integration guide for payment requests

Learn how to integrate the payment requests flow into your site

Test cases for payment requests

Walk through all scenarios to make sure your integration works correctly

/requests

API endpoint

payment_request

API callback
Last modified on June 15, 2026