Skip to main content
Ideal for: Giving a customer their own bank account number to pay into, again and again — wallet top-ups, recurring collections, marketplace sellers, or any case where you need to know who sent money without asking.

Virtual account or bank transfer?

Both have the customer send money to a SeerBit-controlled bank account. The difference is how long the account lives and who it belongs to. Use a plain transfer when the customer is paying once at checkout. Use a virtual account when the same customer will pay repeatedly and you want every inbound payment attributed to them automatically.

How it works

You create an account against a customer, supplying their name, email and a reference of your own. SeerBit returns a real bank account number at a partner bank. Give that number to the customer; anything they transfer into it is credited to you and attributed to the reference you set. Because the account persists, you do not need to generate anything at payment time — the customer can pay whenever they like, and you match the inbound payment by the account number or your reference.

Authentication

Virtual Account calls are authenticated with a bearer token, generated from your public and secret keys.

Authentication

How to generate the token, and which credential every other SeerBit API expects.

Create Virtual Account

POST

Request Sample

The code snippet below shows an example request for creating a virtual account

Response Sample

The code snippet below shows an example response for creating a virtual account

Parameter description

Response fields

Get Virtual Account

GET

Request Sample

The code snippet below shows an example request to get virtual account

Response Sample

The code snippet below shows an example response to get all created links

Delete a Virtual Account

DELETE

Request Sample

The code snippet below shows an example request for deleting virtual account

Response Sample

The code snippet below shows an example response for deleting a virtual account

Get Payment

GET

Request Sample

The code snippet below shows an example request to get payments

Response Sample

The code snippet below shows an example response for getting a payment

Notes

  • The account number is permanent until you delete it. Give it to the customer once and let them save it — regenerating on every payment defeats the purpose.
  • Your reference is how you attribute payments. Make it unique per customer and store it against their record, or you will not be able to tell inbound payments apart.
  • Deleting an account frees the number. A deleted account stops accepting payments; do not delete one a customer may still pay into.
  • Payments arrive without warning. A customer can transfer at any time, so rely on webhooks rather than polling — see the virtual account transaction event.
  • Accounts created with test keys only work in test mode. See Test and live modes.