Merchant Onboarding
Pick a product first: Checkout to accept USDT, sponsorship to top up addresses you control. Both share one API key.
Checkout: create an invoice
curl -X POST https://your-pontoon-host/api/v1/intents \
-H "Authorization: Bearer <API-KEY>" \
-H 'content-type: application/json' \
-d '{
"merchantOrderId": "order-2026-0001",
"chainKey": "tron",
"amountUsdt": "40.00",
"treasuryAddress": "T…",
"webhookUrl": "https://merchant.example/api/webhooks/pontoon",
"expiresInSeconds": 1800
}'Show the returned address to the buyer. Fulfil only after a verified checkout.paid webhook. Full state machine: /docs/hosted-checkout.
Sponsorship: five steps to live gas
Every call below is a real endpoint on this platform.
1. Create an API key
Sign in to the dashboard, open API Keys, click Create key. The key (a UUID) is shown exactly once — copy it. Enable/disable any time from the ⋯ menu.
2. Bind your user’s wallet
curl -X POST https://your-pontoon-host/api/v1/wallets \
-H "Authorization: Bearer <API-KEY>" \
-H 'content-type: application/json' \
-d '{"walletAddress": "0x…"}'EVM (0x…), Tron (T…) and TON (EQ…) addresses are all supported.
3. Fund your prepaid balance
Transfer USDC on Base to the platform solver with the credit calldata (see /docs/funding). The indexer credits your balance automatically within minutes. Executions debit this balance — the platform never fronts gas for you.
4. Sponsor an execution
curl -X POST https://your-pontoon-host/api/v1/sponsor \
-H "Authorization: Bearer <API-KEY>" \
-H 'content-type: application/json' \
-d '{
"idempotencyKey": "order-12345",
"walletAddress": "0x…",
"chainKey": "tron",
"targetAddress": "T…",
"requestedAmount": "65000",
"executeNow": true
}'Same idempotencyKey = same execution, never billed twice. The response includes the on-chain evidence and your toll (billing.platformFeeUsd).
5. Collect revenue
Configure an app-fee recipient in the dashboard (Revenue page), accumulate fees as your users transact, and claim with an EIP-191 signature — payouts settle in Base USDC. See /docs/payouts.
/api/v1/* · auth: Authorization: Bearer <api-key>. The dashboard session is for humans; the v1 API is for your server.