Triple-A Developer DocsTriple-A Developer Docs
Triple-A dashboard

Choose your solution

View as MarkdownView this page as plain textOpen in ChatGPTAsk questions about this pageOpen in ClaudeAsk questions about this pageOpen in PerplexityAsk questions about this page
Connect to CursorUse these docs in CursorConnect to VS CodeUse these docs in VS Code

Triple-A offers three APIs that move money and a fourth that verifies identity. This page compares them so you can pick the one that fits your use case and know where to start.

Solutions at a glance

The table below compares the three APIs that move money.

Stablecoin PaymentsStablecoin PayoutsLocal Currency Payouts
DirectionMoney inMoney outMoney out
Who paysYour customer, in stablecoins or other digital currencyYou, in local currencyYou, in stablecoins or local currency
Who receivesYou, settled in local currencyA recipient (company or individual), in stablecoins to their walletA recipient (company or individual), in local currency to a bank account or mobile wallet
Typical useCheckout, account top-ups, invoicesPaying out in stablecoinsMarketplace seller payouts, withdrawals
DocsStablecoin PaymentsStablecoin PayoutsLocal Currency Payouts

A fourth product, KYC, verifies the identity of your customers or recipients. It doesn’t move money itself.

Which one do you need

Find the goal below that matches what you want to do.

  • If you want customers to pay you in stablecoins, use Stablecoin Payments. Customers pay through a Triple-A payment form (hosted, embedded, or by payment link), and you are settled in local currency.
  • If you need to pay people in stablecoins and you hold local currency, use Stablecoin Payouts. You fund the payout in local currency and Triple-A delivers stablecoins to the recipient’s wallet address.
  • If you need to pay people in their local currency, use Local Currency Payouts. You can fund transfers in stablecoins or local currencies, and the recipient receives local currency.
  • If you want to verify customers once and let them transact smoothly, add KYC.

If your product does more than one of these, you can use several APIs. They share one authentication mechanism.

How the solutions connect

The APIs share an account, authentication, and a host, but each has its own currencies. The following diagram shows what they share.

flowchart TD A[Triple-A account and credentials] --> B[Get an access token] B --> C[Stablecoin Payments] B --> D[Stablecoin Payouts] B --> E[Local Currency Payouts]

Authentication is shared. The same OAuth token and mechanism apply across Stablecoin Payments, Stablecoin Payouts, and Local Currency Payouts, and you create credentials once in the dashboard. See Authentication.

The host is shared. All three APIs get a token from the same Get an access token endpoint.

Currencies differ by product. Stablecoin Payments supports 143 presentment currencies and 30+ settlement currencies. Local Currency Payouts has separate lists for disbursement and pre-funding currencies.

Next steps

These pages are the best places to go next.