Atlas DocumentationChangelog
New features, improvements and fixes to the Atlas API and dashboard.
October 2026
Virtual accounts move to VaaS
Virtual accounts now have a new set of VaaS endpoints under /api/v1/vaas. They take the same requests and return the same responses as before. Only the path changes, except for reactivating an expired account, which moves to POST /api/v1/vaas/update-virtual-account and takes the account reference in the request body.
VaaS also adds endpoints to activate and deactivate a virtual account without deleting it.
The /api/v1/virtual-account endpoints are deprecated. They keep working for existing integrations, but they are no longer maintained.
What you need to do
Replace /api/v1/virtual-account with /api/v1/vaas in your requests, and send reference in the body when you reactivate an account. Your existing virtual accounts carry over, so you don't need to recreate them. See the virtual accounts migration guide and the create virtual account endpoint.
August 2026
Create a virtual account for an existing customer
You can now create a virtual account for an existing customer who doesn't have a wallet yet.
Virtual account provider is optional
provider_name is now optional when you create a virtual account. In test mode, the only provider you can name is duplo; in live mode, globus or wema.
Virtual accounts
You can now create dedicated NGN virtual accounts and collect bank transfers into them.
- Single-use accounts accept one payment and expire at the time you set, up to 24 hours ahead.
- Multi-use accounts stay open and accept repeated payments.
- List your virtual accounts, find one by its reference or your source reference, and list the transactions paid into it.
Start with the virtual accounts guide or the create virtual account endpoint.