Skip to main content
This guide explains the standard flow for enabling virtual accounts for an existing customer.
Please note that the product access request is subject to a fee and will appear on your invoice at the end of the month.

​
1. Create a customer

Before you can enable virtual accounts, the user must exist as a customer in the system. Start here:

​
2. Confirm the customer is active

You should verify the customer’s status before requesting access. Only customers with status active are eligible for feature access requests. If the customer is not active, the access request will be rejected.

​
3. Request virtual account access

Once the customer is active, you request access to virtual accounts.
Implementation details live in the Customers API reference.

​
4. Track the result

Your product should show the access request status to the user. Typical outcomes:
  • requested — under review / processing
  • granted — virtual accounts are enabled
  • rejected — declined (see rejection reasons)
Reference:

​
FAQ

​
What happens if I request access for a customer who is not active?

The request is rejected. The customer must be verified and active before product access can be granted.

​
Can I request access more than once?

If the same request is already pending or exists, the API may return a conflict response (duplicate request).

​
How do I know why access was rejected?

Check the rejection reason codes and map them to user-facing messages: