Skip to main content
Every customer on your platform is a full Rolla account, created and verified through the Account Onboarding API. This guide walks the journey at a high level; the reference pages carry every field. An application moves through five statuses:
You’ll hear about every move via webhooks: account.submitted, account.approved, account.changes_requested, account.rejected.

​
Business customers

1

Create the account

Create Account with type: "business", the business name, and a unique email (email is required). The response carries the new account’s id under data.account, plus a draft application.
2

Fill in business details

Update Business Details with business_info, business_address, contact_info, and optionally banking_info. Sections merge, so you can save progress across calls.
3

Upload documents

Upload Document for each requirement — incorporation certificate, articles, proof of address, director and shareholder registers, bank statement.
4

Verify related persons

Add each beneficial owner and director, then get each verified — see KYC options below.
5

Submit

Poll Get Requirements until readyToSubmit: true, then Submit.

​
Individual customers

Same shape, shorter path: create with type: "individual", fill in personal details, upload proof of address, complete identity verification, and submit once requirements are clear.

​
KYC options

You choose how identity verification happens, per account and per related person:
KYC reliance is gated per partner — ask Rolla to enable it for your tenancy.
The account.verification.completed webhook fires as each person passes, with ready_to_submit telling you whether the application is now complete.

​
After approval

Approval provisions the account’s wallets (and fires account.approved). From there:
  1. Issue deposit accounts — NGN instantly, USD after provider review; share details from Funding Instructions.
  2. Operate the account — every wallet, payout, and transaction endpoint, scoped with X-Account-Id. See Operate customer accounts.
If review comes back changes_requested instead, the webhook and Get Account carry the reason — fix and resubmit.

​
Testing the journey

In sandbox, Approve Account lets you self-approve a submitted application and run the whole flow — onboarding to payout — without waiting on compliance review. It is sandbox-only, so call it against the staging host; in production it returns 404. The Platform Quickstart does exactly that.