NFT Checkout Overview

Belong NFT Checkout lets a store accept an on-chain payment and issue one NFT without moving its product catalog or order system into Belong.

The store keeps products, inventory, orders, returns, and physical fulfillment. Its backend creates a short-lived Belong checkout session for a verified order. The storefront opens that session with @belongnet/sdk, and the store receives a signed server webhook after the payment and NFT mint are confirmed on-chain.

The first payment rail is Thirdweb:

• crypto_wallet pays from the customer's Belong wallet;
• thirdweb_card can be enabled for eligible merchants and networks;
• each checkout shows only methods enabled in its server-created session;
• Crossmint and Transak are not used.

For an ERC-20 payment, a customer may first need a small amount of the network's native token to approve spending. Belong provides the wallet top-up path. After approval, the payment and NFT issue continue through the existing Thirdweb flow.

Integration flow

1. Create and deploy one NFT collection for the store in Belong CheckIn.
2. Obtain a server API key with checkout:create and checkout:retry permissions.
3. Create a pending order and verify its price in the store backend.
4. Create a Belong checkout session from that backend.
5. Pass only checkoutId and clientSecret to the storefront SDK.
6. Treat browser events as UI updates.
7. Treat the signed checkout.completed webhook as the source of truth for the order.

See Create a checkout and Quick start.