What the TransFi API does, how this reference is organized, and the one call to learn.
One API to move money across borders. Collect in 30+ countries, pay out to banks and wallets, hold many currencies, and move between local currency and stablecoin.
How this reference is organized
| Section | What is in it | Read it when |
|---|---|---|
| 🚀 Getting Ready | These basics, and the lookups you make first: MIDs, currencies, tokens, payment methods, limits | Before your first call |
| 👥 People | Senders, recipients, roles, KYC, KYB and verification links | Registering whoever pays or gets paid |
| 💸 Payments | Rates, orders, documents, Scan Pay, balances, virtual accounts and settlements | Moving money. Every flow starts at Create Order |
| 🧪 Sandbox | Simulation endpoints that exist only in sandbox | Testing |
Webhook events, with every status and what to do about it, are in the guides under Webhooks.
One call to learn
Every payment is POST /v3/orders. The orderType picks the flow:
orderType | What it does |
|---|---|
payin | A customer pays you |
gaming | A customer pays you through a custodial wallet created in their name |
payout | You pay a person or a business |
onramp / offramp | Your user buys or sells crypto |
fiat_prefund / crypto_prefund | You add your own money to your balance |
swap | You convert a balance you hold into another currency |
The flow guides show each one end to end. This reference specifies every field.
What every endpoint page gives you
What it does and when to call it · every parameter, with enum values explained · one runnable example · every response and what to do about it · links to the guide that uses it.
In this section
Authentication & Headers · Environments · Idempotency · Pagination · Rate Limits · Errors · API Version · Glossary · Enums · Build with AI