Skip to content

Virtual Accounts Solution Cheatsheet

Clean parent→child ledger hierarchy giving customers real account numbers for direct deposits, segregating funds, and automating flows via APIs—without opening hundreds of physical accounts.

Choose Your Perspective

👨‍💻

For Developers

Simple Account Creation

Create virtual accounts via API - customers get real account numbers for direct deposits

Comprehensive API Coverage

Create/list/update virtual accounts; credit/debit sub-accounts; list transactions; settlement and withdrawal flows

Developer-Friendly

OpenAPI specs, UAT & production environments, comprehensive documentation

Integration Support

Postman collections, code samples, and dedicated API support

Common Transaction Flows

Transaction Steps

1
Corporate creates Virtual Account via API
2
Customer receives dedicated account number
3
Customer deposits directly to their account number
4
Funds appear in their Sub Account automatically

Practical Guardrails

🏛️

BMA-Regulated Clients Only

Onboarding requires due diligence and developer portal registration

🔀

Enforced Routing

No direct Sub ↔ Settlement transfers; always route through Parent for auditability

Same-Name Withdrawals

Customer withdrawals must go to same-name external accounts for AML compliance

🔄

Reversal Support

Unauthorized or mis-routed inbound funds can be reversed or rejected