Skip to main content

Checkout Overview

Checkout is an API-based low-code payment integration solution. It allows merchants to dynamically create payment sessions via a backend API and generate a secure hosted cashier page.

Unlike Payment Links, Checkout can be deeply integrated into your business systems, suitable for e-commerce cart checkout, SaaS dynamic subscriptions, or any scenario requiring real-time amount calculation based on user behavior.

Core Mechanism: Hosted Payment Page​

To ensure fund security and simplify frontend development, our Checkout uses a Hosted Payment Page model.

Workflow​

  1. Create Session: When a user clicks "Checkout" on your website, your backend server calls our API to create a Checkout Session.
  2. Redirect: The API returns a hosted page URL, and you redirect the user's browser to this address.
  3. Complete Payment: The user completes the crypto payment on the hosted page (using any asset supported by the platform).
  4. Callback & Redirect: After payment is completed, if a success redirect URL is configured, the user is automatically redirected to that URL, while the system notifies your server via Webhook to perform fulfillment.
Why not Embedded?

Given the specific nature of Web3 payments (requiring wallet signature invocation, cross-chain routing calculation), a hosted page provides the most stable and compatible payment experience while ensuring merchants do not need to handle complex wallet and on-chain interaction logic.

Flexible Product Construction​

Checkout offers high flexibility, supporting two ways to define products:

1. Reference Existing Product (Product ID)​

Directly use the Product ID created in the merchant backend "Product Library".

  • Use Cases: Standardized products, such as fixed membership plans, gift cards.
  • Advantages: Easy to manage images and descriptions uniformly; updating product info in the backend does not require frontend code changes.

2. Ad-hoc Products​

Define product name, image, and price directly in the request body when calling the API, without pre-creating in the backend.

  • One-time Logic: Products defined this way are one-time use, and they will not be saved to your backend product library.
  • Use Cases:
    • Dynamic Cart: User bought 3 different items, total price is calculated dynamically.
    • Personalized Service: Unique quote generated based on user configuration.

From an architectural perspective, Payment Link is essentially a static wrapper around Checkout Session.

  • Payment Link: The system pre-defines products and rules, generating a permanently valid URL. Every visit to this URL implicitly instantiates a Checkout Session in the background.
  • Checkout API: Gives you the ability to manually control every Session instantiation. You can customize different parameters (such as Order ID, User ID, Custom Amount, etc.) for each click.

Use Cases​

  • E-commerce Websites: Complete shopping cart checkout flow, requiring internal Order ID association.
  • SaaS Subscriptions: Dynamically calculate the initial fee based on the number of seats selected by the user.
  • Platform Business: Need to pass transaction metadata (Metadata) through to the settlement process.

Next Steps​

After understanding the basic concepts, please view the standard integration sequence diagram and detailed process.

View Integration Workflow →