Not recommended. Use Create Order and redirect the shopper to the returned payment_url instead.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
This endpoint is not recommended. For almost every integration, use Create Order and redirect the shopper to the returned
payment_url. Choose the checkout method only if the hosted invoice genuinely cannot cover your case and you accept the limitations below.
Displaying payment details on your own site
Calls from accounts without access to the checkout method return status code 422.
The checkout method returns the payment details of an order so you can display them on your own page instead of redirecting the shopper to CoinGate.
This is achieved by pre-selecting BTC, LTC, etc as the payment currency, and retrieving the pay_amount and payment_address parameters. These are sufficient for a customer to complete the payment, as well as to generate a QR code which a customer can scan with a mobile wallet.
What you give up with this endpoint
The response gives you payment_address and pay_amount and nothing else. Everything the CoinGate invoice does today becomes yours to build and maintain.
- Void refunds are on you. Overpayments, underpayments and transactions received on cancelled or expired orders are resolved through the refund form on the CoinGate invoice, which the shopper never sees here. You build that form and drive it yourself through Create Void Request and Get Void Request.
- No Binance Pay. It has a separate integration, Binance Checkout.
- No WalletConnect. Shoppers copy the address or scan a QR code you render.
- You supply shopper data. We never see the shopper, so Travel Rule and risk data must come from you in the shopper object.
- You build the payment page. QR code, amount display, expiry countdown, paid and expired states.
- New payment methods do not reach you. What we add to the hosted invoice is free for
payment_urlmerchants and needs code changes here.