Skip to main content
Most integrations only need part of the lifecycle. Find your goal below: the highlighted stages are the ones you implement, the dimmed ones you can ignore.

Give users a USD account

Anyone outside Nigeria and Canada can hold US dollars and receive money into a virtual bank account.
UserWalletKYCRailFundMove money
Create a USDB wallet, run Global KYC (id-and-liveness), gate on GET /kyc/usd-readiness, then POST /onboarding/start-usa. The account is issued asynchronously, so poll GET /vba/usd until it reports active. Read: KYC — USD · USD virtual bank account

Nigerian wallets and bank withdrawals

Hold CNGN, receive into an NGN virtual account, and withdraw to any Nigerian bank.
UserWalletKYCRailFundMove money
Nigeria is the shortest KYC path: a BVN auto-populates the profile, and POST /kyc/activate takes no sumsubLevelName. Withdrawals verify the destination account first, then register it, then offramp. Read: KYC — Nigeria · NGN deposits & withdrawals

Mexican peso on and off ramp

Let Mexican users fund by SPEI transfer and pay out to a CLABE.
UserWalletKYCRailFundMove money
Mexico activates through Etherfuse rather than an onboarding/start-* endpoint: POST /latam/mx/kyc/activate, have the user sign Etherfuse’s agreements via GET /latam/mx/kyc/launch/agreements, then poll until approved — the CLABE is provisioned automatically. Every movement afterwards is a quote followed by an order. Read: KYC — Mexico · MXN on/offramp

Pay out to EU bank accounts

Send euros from an EURe wallet to any IBAN over SEPA.
UserWalletKYCRailFundMove money
The EUR rail activates with a Monerium handshake (POST /onboarding/start-monerium) after the standard KYC wizard. Payouts are a three-call handshake because the transfer is signed on-device. Read: KYC — Europe · EU SEPA payouts

Top up with crypto instead of a bank

Take USDC (and other supported assets) on-chain rather than through fiat rails.
UserWalletKYCRailFundMove money
A crypto top-up needs no local rail: read GET /deposit/supported-assets for the chains and tokens on offer, then POST /deposit/wallet for a deposit address. Read: Supported regions

Onboard users without your own app

You have no mobile app. Your users onboard inside the BMONI app from an invite, and you read their accounts over the API.
UserWalletKYCRailFundMove money
This is the smallest integration there is: one invite call that carries the KYC you already hold, a webhook that tells you the user linked, and a read of their virtual account. Stages 2, 4, 5, and 6 happen inside the BMONI app. Read: Integration flow (no mobile app)

Not sure yet? Read the lifecycle

All six stages, what each one needs before it works, and what it leaves you with.