account_reference you define.
Replace
sandbox.lyseis-pay.com with live.lyseis-pay.com when moving to production.Headers
Request Body
string
required
A unique identifier you assign to this virtual account (e.g. a customer ID or wallet ID). Must be unique across your merchant account. Used to look up the account later.
string
required
The full legal name of the customer this account is provisioned for. This name is associated with the bank account.
string
required
The customer’s email address. Used for notifications and account lookup.
string
required
ISO 4217 three-letter currency code for the account. Example:
NGN.string
required
The customer’s Bank Verification Number (BVN) — an 11-digit identifier issued by the Central Bank of Nigeria. Required for regulatory compliance when provisioning NGN accounts.
object
Optional arbitrary key-value pairs to attach to this virtual account record. Returned on subsequent lookups and webhook notifications.
Example Request
Response
string
Indicates whether the account was successfully provisioned. A value of
"success" means the virtual account is active and ready to receive funds.string
The virtual bank account number assigned to this customer. Share this with the customer for inbound transfers.
string
The name of the partner bank or institution that issued the virtual account, e.g.
"Wema Bank".string
The CBN-assigned sort code or bank code for the issuing bank.
string
The unique reference you provided at creation. Use this to retrieve or identify the account later.
string
Paylink’s internal reference for the account reservation. Use this when contacting support about a specific virtual account.
string
The activation status of the virtual account, e.g.
"active".string
The customer name associated with the account, echoed from the request.
string
The customer email associated with the account, echoed from the request.
Example Response
Virtual account numbers are persistent — the same account number is reused for all subsequent transfers from the customer. Funds received are automatically posted to your merchant wallet and trigger a webhook if one is configured.