Tsara's stablecoin APIs support two integration styles: managed fiat-to-stablecoin payment rails and direct wallet operations. Choose the managed rail when the business outcome is a conversion or payout; choose direct wallet operations only when your application explicitly needs wallet and address control.
Base URL: /v1/stablecoin
Authentication: Authorization: Bearer <secret_key>
Managed payment rails
| Flow | Customer provides | Customer receives |
|---|---|---|
| Onramp | NGN through returned payment instructions | Stablecoin at a destination wallet |
| Offramp | Stablecoin through returned deposit instructions | NGN in a verified bank account |
Managed flows return a reference, payment instructions, quote information, expiry, and status. Store the business reference and Tsara reference together, then follow the resource until it is successful or failed.
Preferred routes:
POST /v1/stablecoin/onrampGET /v1/stablecoin/onrampGET /v1/stablecoin/onramp/statusGET /v1/stablecoin/onramp/ratePOST /v1/stablecoin/offrampGET /v1/stablecoin/offrampGET /v1/stablecoin/offramp/statusGET /v1/stablecoin/offramp/ratePOST /v1/stablecoin/offramp/quote
Compatibility aliases remain under /v1/stablecoin/wallets/onramp and /v1/stablecoin/wallets/offramp, but new integrations should use the preferred routes.
Direct wallet operations
Direct operations let you create Tsara-managed wallets and addresses, read balances, and send supported assets. These are secondary infrastructure routes and should not be substituted for onramp or offramp when a fiat conversion is required.
Operational guidance
- network and asset values must match a supported combination
- payment and deposit instructions expire; use the returned expiry
- treat
pendingandprocessingas non-final - use status endpoints and signed webhooks for reconciliation
- never infer a successful conversion from an on-chain submission alone