Virtual Accounts
A Virtual Account (VA) is a dedicated collection account used for receiving inbound funds. Onboarding a customer onto a VA follows one shape for both customer types: check the supported currencies, upload the required documents, register the customer, and RHUB Admin/Operations then approves the request and links it to a collection bank account.
Virtual Account APIs use the same access token as the rest of the platform. Obtain it from the Authentication API and send it on every VA call:
Authorization: Bearer <access_token>
Base URLs for each environment are listed under API environments.
This API onboards a customer onto a Virtual Account (VA) — a dedicated collection account used for receiving inbound funds. There are two customer types — Individual and Business — and both follow the same shape: check the currency list → upload the required KYC/compliance documents → register the customer → an admin approves the VA request and links it to a real collection bank account.
Individual Customer
A natural person. Registration collects personal identity (name, DOB, gender, nationality), a single government ID, and a home address. 3 mandatory KYC documents.
Business Customer
A registered company. Registration collects business/legal identity, a registration document, and a list of Ultimate Beneficial Owners (UBOs) in ownerDetailList . 8 of 9 corporate documents are mandatory.
How VA onboarding works
RHUB Admin/Operations links the customer to the applicable collection bank account.
Where to start
| Step | Page |
|---|---|
| Understand the sequence | VA integration flow |
| Check supported currencies | VA currencies |
| Find the document checklist | VA document requirements |
| Register a customer | Individual · Business |
| Track the request | VA request status |
| Understand approval | VA approval process |