Choose Your Integration
Fiatsend exposes different surfaces depending on what you are building. Use this page to pick the right path before you read further.
Integration paths
| If you are building… | Use | Docs |
|---|---|---|
| Payroll, remittance, marketplace payouts to Ghana MoMo | Partner API (REST) | Partner API → Start Here |
| Merchant checkout: request payment from a FiatsendOne user | Partner API — payment intents | Payment intents |
| On-chain payouts, escrow, P2P, or contract calls | On-chain SDK (@fiatsend/sdk from fiatsend-sdk) | On-chain SDK |
| End-user app (send, receive, convert in FiatsendOne) | FiatsendOne (no public app API) | FiatsendOne |
Partner API vs FiatsendOne app API
The Partner API (https://api.fiatsend.com/v1) is the supported integration surface for businesses. Authenticate with API keys (fs_test_* / fs_live_*) from Fiatsend Console.
The routes under app.fiatsend.com/api/* power the FiatsendOne web app (Privy wallet login, custodial ledger, in-app flows). They are not documented here as a public integration contract and may change without notice. Do not build third-party products against those endpoints.
Two packages named @fiatsend/sdk
| Package | Install | Purpose |
|---|---|---|
| Partner API client | npm install @fiatsend/sdk (published from Partner API) | REST client for /v1/withdrawals, webhooks, rates |
| On-chain SDK | npm install @fiatsend/sdk viem (fiatsend-sdk monorepo) | Smart contract interactions on EVM chains |
Check the install source and import style in your project. Partner integrators should use the REST client documented in REST SDK.
Related pages
- Networks & assets — which chains apply to deposits vs settlement
- Fiatsend Console — API keys and webhooks
- OpenAPI specification — machine-readable Partner API