Cashfree Payments - Auto Collect (Virtual Bank Accounts)

Send a POST request to /pg/vba with a nested body containing virtual_account_details (id and name), optional kyc_details, remitter_lock_details, amount_lock_details, and bank_codes. Use header x-api-version: 2024-07-10, which differs from the standard PG version.

No, VBAs accept bank transfers only (IMPS, NEFT, RTGS) because NPCI does not permit UPI transfers to virtual bank accounts. For UPI collection, use standard Cashfree PG UPI flows, payment links, or static UPI VPAs instead.

VBA credits arrive as a standard PAYMENT_SUCCESS_WEBHOOK with payment_group set to vba_transfer, not a dedicated event. The UTR, remitter account details, and vaccount_id are inside data.payment.payment_method.vba_transfer, verified with the standard HMAC-SHA256 signature.

A remitter lock restricts a VBA to accept payments only from whitelisted bank accounts specified as account_number and ifsc pairs in remitter_lock_details. Transfers from any other account are rejected, preventing mis-credits in high-value B2B flows.

There is no close endpoint; deactivate by sending PUT /pg/vba/{virtual_account_id} to set the status to INACTIVE. First check recent credits via POST /pg/vba/payments filtered by virtual_account_id and wait about 48 hours after the last expected payment.

Common causes are remitter lock mismatches, amounts outside the configured min_amount or max_amount range, or the VBA being INACTIVE. Check POST /pg/vba/payments filtered by virtual_account_id to see rejected entries with failure reasons.