[ 01 ] -
Account & Wallet
provision and maintain accounts for your end users in any of 16 supported assets.
Loading
Loading
Account provisioning, on-ramp, off-ramp, transfers, payouts, collections, FX, compliance, and digital products exposed through one REST API, settled on stablecoins, delivered across 55 countries today.
$ curl -X POST https://api.zeam.co/v1/payouts \
-H "Authorization: Bearer $ZEAM_KEY" \
-H "Idempotency-Key: po_9f3b1e" \
-d '{
"connector": "ZA-OFF-001",
"amount": "500.00",
"currency": "ZAR",
"funding": {"asset": "USDZ", "chain": "stellar"},
"beneficiary": {"id": "ben_01HY…"}
}'{
"id": "po_01HY9W…",
"status": "delivered",
"settled_at": "2026-04-18T10:14:07Z",
"tx": "txn_A7F…e3" // verifiable on stellar
}provision and maintain accounts for your end users in any of 16 supported assets.
Collect local-currency pay-ins via bank, mobile money, and allocation references; receive stablecoin in return.
fund with stablecoin, deliver fiat to bank accounts, mobile wallets, cash networks, vouchers, and QR.
Move value between accounts and across assets, on-ledger.
single and bulk, with idempotency keys and webhook-driven status.
receive funds with auto-reconciliation to a named account.
between any supported pair, at verifiable rates.
hosted KYB/KYC, screening, monitoring, EDD or bring your own license. airtime and other VAS, exposed as catalog items.
On-ramp and off-ramp connectors compose. A user pays KES via M-Pesa (on-ramp). The platform converts to USDZ on-chain. A second connector off-ramps USDZ to ZAR and lands it in a South African bank account. The user experiences one payment. Underneath, two connectors, two countries, two providers, one stablecoin bridge. This is why coverage compounds. Adding one new on-ramp connector immediately opens routes into every existing off-ramp destination.
Stellar, Ethereum, and Solana at launch. Connect supports ZEAM-native stablecoins (USDZ, ZARZ), client-issued stablecoins, and curated third-party stablecoins. Every movement is recorded on-chain. Reconciliation is verified against the ledger, not a vendor attestation. New chains are added on the same compliance, liquidity, and reliability bar no chain-specific behaviour leaks into the API.
Every payment reaches delivered or refunded. There is no third state. - Automated retries on transient failures - Automated reroute where alternative connectors exist - Automated refund where delivery cannot complete - STP target above 99.99% — measured against the underlying ledger You do not run an ops team to babysit our rails.
Connect can be operated under three compliance models, assigned per corridor: - Model A — partner relies on ZEAM's compliance stack. Hosted KYB/KYC, screening, monitoring, regulatory reporting included. Best for unregulated or new-market partners. - Model B — partner brings its own license. ZEAM provides infrastructure; the partner owns its end-user compliance. Best for licensed EMIs and banks. - Model C — hybrid, corridor by corridor. Use ZEAM compliance in new markets, your own where you're licensed.
One integration replaces 3–6 months of integration per market. New countries arrive as connector configurations, not platform rewrites.