Static virtual accounts
A dedicated account number for one purpose.
Besides one-off checkout payments, you can issue your business an account number that a customer pays into directly. It suits a recurring or standing collection tied to one purpose, such as a specific customer or a subscription, rather than a single order.
Subscription collection
90 • • • • • • 01
- Status
- pending_activation → active
- Mode
- test or live, by key
Fictional values for illustration.
How it works
Issue, collect, block.
- 01
Choose a bank
Fetch the banks you can issue with from the API. The list can change, so do not hardcode one.
- 02
Issue the account
Send a purpose (up to 255 characters, searchable later) and the bank code. The account starts as pending activation while it is provisioned.
- 03
Collect
Once active, the account accepts inbound transfers for that purpose.
- 04
Manage
List accounts with filters for status, dates and purpose, retrieve one by id, or block an account you no longer want to receive payments.
Account status
Four states, one clear meaning each.
- pending_activation
- Issued, not yet ready to accept transfers.
- active
- Accepting inbound transfers.
- blocked
- Deliberately stopped from your side.
- expired
- No longer accepting transfers.
Blocking is one-way. There is no API endpoint to reactivate a blocked account; contact KonetPay support if you need one reinstated.
POST /api/external/virtual-accounts/
Authorization: Bearer sk_test_XXXX
{
"purpose": "Subscription collection",
"bank": "<code from the banks endpoint>"
}