Quickstart
Integrate with ChatterPay B2B through the public Sandbox, API Reference and official backend SDK. You do not need access to ChatterPay source repositories or internal runtime environments.
Start in the Sandbox
Use the Sandbox to explore a guided integration flow in your browser. It creates demonstration resources through the same SDK-backed integration boundary and displays the resulting operation timeline.
Integrate your backend
Use the API Reference as the public HTTP contract. Your backend authenticates with the credentials issued for its environment, uses the official SDK or equivalent conforming HTTP client, and supplies a unique request ID for every financial mutation. Reusing that ID makes a safe retry instead of creating a duplicate operation.
Typical flow
- Create or identify a user in your tenant.
- Create a logical wallet and provision the enabled chain account.
- Request and present a quote.
- Accept the quote with that unique request ID.
- Follow the asynchronous operation and verify signed webhooks or cursor events.
What you can do, and where each one is documented
| Capability | The call that does it | Documented in |
|---|---|---|
| Resolve a person to a wallet, and read their balance per network | resolveRecipient, balances | Identity, users and wallets · Recipient resolution |
| Send on an EVM network, on Bitcoin or on Cardano | quote, transfer | EVM · Bitcoin · Cardano |
| Send an amount no single network covers, split across networks | quote, transfer — the quote comes back with legs | A send split across networks |
| Swap one asset for another | lifiQuote, transfer | Swaps and bridges |
| See what an operation cost and who paid it | operation, platformAccounts | Costs and platform accounts |
| Follow what happened, and be told about it | operation, events, signed webhooks | Operations, quotes and states · Webhooks and channels |
Every one of them is reachable from a conversation too, through the channel adapters: the interface is not a limit on the capability.
Network availability
Networks, assets and execution modes are enabled independently per environment. The Roadmap is the authoritative public view of pilot, in-development and planned capabilities; no sandbox or testnet result is a mainnet or production commitment.
Fees and settlement
Quotes use integer base units and separate service, provider and network costs. Cross-chain routes are exposed only when their exact configuration is enabled; a route whose total debit cannot be safely determined is not presented as executable.