Payment Link (Checkout Page)
Cregis provides an industry-standard checkout interface via its API, allowing merchants to facilitate payments for their customers. Merchants can redirect users from their website's payment page to this checkout interface, and upon payment completion, users are automatically redirected back to the website. This reduces the development and manpower costs required for merchants to build a payment system.
Checkout Page Payment Process
On the checkout page, the payer can select one cryptocurrency to complete the payment. If the order currency differs from the payment currency, the system will automatically perform the conversion using real-time exchange rates. (Merchants can also restrict the accepted payment currencies via the
tokensparameter in the API.)
Payers can also review order details on the checkout page including the order amount, order number, product description, etc.

After selecting the payment currency, the payer will need to choose the payment network.

Once the selection is complete, the system will generate a payment address and a QR code. The payer can either copy the address or scan the QR code to complete the payment.

Payers may also choose to use a third-party wallet to scan the QR code for payment. After scanning, the third-party wallet will automatically fill in the currency, network and amount, allowing the payer to confirm the payment seamlessly.

After a successful payment, the page will redirect to a payment completion page. After 5 seconds, the user will be automatically redirected back to the merchant’s website (specified via the
success_urlfield in the API). If the order status is in an usual status, the payment completion page will also display the reason and automatically initiate corresponding processes such as sending emails for additional payment requests, partial refunds or full refunds.
If the payer does not complete the payment within the order's validity period, the order will automatically expire. By clicking the "Return" button, the payer will be redirected to the
cancel_urlsubmitted via the API.
Last updated
Was this helpful?

