Virtual Account API
Issue a unique virtual bank account per customer for automatic payment collection and reconciliation.
What is the Virtual Account API?
The BILAPI Virtual Account API lets you issue a unique virtual bank account number (with IFSC) for each customer, invoice or order — so every incoming NEFT/IMPS/RTGS/UPI payment is automatically mapped back to the right payer with zero manual reconciliation.
It is used by lenders collecting EMIs, marketplaces settling with sellers, and B2B platforms handling bulk collections. Because each payer gets their own account number, reconciliation becomes instant and error-free.
Create a virtual account in one call and receive the account number and IFSC as JSON. Billed per successful creation.
What the Virtual Account API returns
Every successful call returns a clean, predictable JSON envelope. The data object includes the fields below (exact fields vary by record availability).
| Field | Description |
|---|---|
virtual_account_number | The unique virtual account number issued. |
ifsc | IFSC to be used with the virtual account. |
reference_id | Your reference / customer id mapped to this account. |
status | Status of the virtual account (active/closed). |
created_at | Timestamp the account was created. |
Sample request & response
Call the endpoint with your API key in the X-Bilapi-Api-Key header. The same request shape works in the free sandbox and in production.
POST https://api.bilapi.com/v1/virtual-account-api
X-Bilapi-Api-Key: <your_api_key>
Content-Type: application/json
{
"reference_id": "CUST-1029",
"name": "Rahul Sharma"
}{
"status_code": 200,
"success": true,
"message": "Virtual account created",
"data": {
"virtual_account_number": "BILAPI0001029",
"ifsc": "HDFC0000123",
"reference_id": "CUST-1029",
"status": "ACTIVE"
}
}Key features
Real-time results
Sub-300ms median response so identity checks never slow your onboarding funnel.
Predictable JSON
The same clean response envelope as every BILAPI endpoint — parse once, reuse everywhere.
Only pay for hits
Invalid inputs and failed lookups are never charged to your wallet.
Secure by design
TLS 1.3 in transit, PII tokenisation at rest and a full audit log on every request.
One key, every API
Sandbox to production on a single key — no per-vendor contracts or integrations.
Built to scale
99.9% uptime target with bulk and webhook-friendly workflows for high volume.
Where it's used
Customer onboarding
Auto-fill and validate identity during signup to cut drop-off and manual review.
Lending & underwriting
Add a verified data point to credit decisions and reduce first-party fraud.
Fraud & risk
Flag mismatches and synthetic identities before they enter your system.
Compliance & audit
Keep a tamper-evident trail of every verification for KYC/AML reviews.
How it works
Create a free account
Sign up on the BILAPI console and get a live API key instantly.
Send a request
POST the required identity fields to the endpoint with your API key in the header.
Get structured JSON
Receive a clean, predictable JSON response in milliseconds.
Plug into your flow
Drop the result straight into onboarding, underwriting or risk decisioning.
Frequently asked questions
What is a virtual account and why use one?
A virtual account is a unique account number mapped to one customer, invoice or order. Because each payer pays into their own number, incoming payments reconcile automatically with no manual matching.
What does the API return?
It returns the issued virtual account number and IFSC, your reference id, and the account status — ready to share with the payer for collections.
Which payment modes does it support?
Payments received via NEFT, IMPS, RTGS and UPI into the virtual account are mapped back to the reference id you supplied.
Who uses the Virtual Account API?
Lenders collecting EMIs, marketplaces settling to sellers and B2B platforms handling bulk collections use it to eliminate reconciliation effort.
Can I test it before going live?
Yes, a free sandbox is included with every account.
Start verifying with BILAPI
One key, a free sandbox and a predictable JSON envelope across every endpoint.