Integration
Paths that combine. Start with the authenticated API: the others depend on the payload or checkout it generates.
| Page | When to use it |
|---|---|
| API | Generate the charge payload from your server. It is the starting point of any integration. |
| Checkout | Send the buyer to the payment page we host, by link or QR code. |
| PIX checkout | PIX QR only, on your site. Payment completes in the iframe; USDT lands in your wallet. |
| Iframe | Embed the checkout inside your own site. Requires allowing your domain in the console. |
| White label | Logo, brand colour and custom domain (CNAME to hosted.tonramp.io) on checkout and the console. |
| Merchants | Stores under the partner, TonRamp floor fee and commission split. |
| Webhook | Receive status changes in your backend instead of polling. |
| OpenAPI and SDK | Official schema and how to generate a TypeScript or Python client. |
Suggested path
Section titled “Suggested path”- Create your API key in the console and generate a test payload with
POST /v1/wallet/trp/generate. - Open the checkout with that payload and confirm your merchant name and the amount render correctly.
- Configure the webhook and fire a test, so you validate the signature before any real payment.
- Only then take real orders, releasing the buyer’s credit on the
completedevent alone.