The model: a tenancy of accounts
As a Platform, your Rolla business becomes a tenant that owns a book of customer accounts:- Accounts — each customer is a full Rolla account you create and verify through the Account Onboarding API: application → documents → KYC → submit → approved.
- One key, scoped per request — your tenant API key acts on any account in your tenancy. Add the
X-Account-Idheader and the entire request — wallets, payouts, beneficiaries, funding instructions — runs as that customer. Omit it and you act as yourself. See Operate customer accounts. - Everything else is the same API — once a request is scoped to a customer, you use exactly the endpoints the Business docs describe: withdraw, swap, transactions. Nothing to relearn.
What your customers get
Verified accounts
API-driven KYC/KYB: hosted verification links, document uploads, or reliance on your own KYC.
Real deposit accounts
NGN accounts issued instantly; USD accounts after provider review. Funding instructions per currency.
Payouts on their behalf
Every payout rail — local, SWIFT, mobile money, stablecoins — from each customer’s own wallet.
One reconciliation feed
Every transaction across all your accounts in one listing, each row naming its account. JSON or CSV.
Staying in sync
Webhooks cover the platform lifecycle end to end:account.submitted, account.approved, account.changes_requested, account.verification.completed, deposit-account events, and every transaction.* event for your customers’ money — delivered to your endpoints, since you’re the tenant. Fee events tell you what each account incurred.
Start here
Platform Quickstart
Onboard a test customer, issue them an account, fund it, and pay out on their behalf — end to end in sandbox.
Onboard your customers
The full onboarding journey for business and individual customers, including KYC options.