Overview

This API lets the platform collect funds from a payer through NEFT/RTGS/IMPS on its v3 stack.

Flow

Below is the flow for using this API.

• The platform creates a virtual account using this API and the endpoint by passing the consumer_urn shared by Decentro before going live.
• The platform can choose a specific virtual account number as desired basis the usecase by the passing the suffix of the virtual account number under the 'custom_va_number' field in the request body.
• The platform receives the status of virtual account creation in the response from Decentro, including the virtual account number if Decentro is generating it.
• The platform can share the virtual account number and IFSC code with the payer on its website, app or offline for the payer to transfer funds to the virtual account.
• The payer transfers funds to the virtual account using their Netbanking portal and any supported modes (NEFT/RTGS/IMPS).
• Decentro triggers the account balance callback to the platform's endpoints configured by Decentro at onboarding time.
• Decentro triggers the Terminal Transaction Status Callback/Webhook to the platform's endpoints configured by Decentro at onboarding time if Decentro receives a success or failure transaction at its end.

Note: Decentro has a standard nomenclature for creating a virtual account. The first 6 digits are static, and the subsequent 10 digits can be customized by the platform.

Understanding Decentro's Virtual Accounts

Decentro simplifies banking by generating multiple virtual accounts linked to various bank providers. While the custom virtual account number remains consistent across these accounts, the static prefix—comprising the first six digits—varies based on the bank code.

Example of virtual account families

Here’s how the virtual accounts are structured:

1. Provider 1: 47382500000001
   (Static Prefix: 473825)
2. Provider 2: 34598700000001
   (Static Prefix: 345987)

In this setup, the custom virtual account number is always 00000001, indicating that all accounts with this number belong to the same family.

Note: You can also identify these accounts using the customer_va_identifier assigned during their creation.

Clients can utilize any of these virtual accounts for transactions. Currently, the API response provides a single virtual account since Yes Bank is the only provider available for creating these accounts. However, we are actively working to integrate more bank providers in the near future.

Operations on virtual accounts

Clients can easily manage operations on their virtual accounts by selecting from either a single virtual account, a family of virtual accounts, or all virtual accounts associated with a consumer.

To effectively identify the relevant virtual accounts for any operation, clients can use one of the following identifiers::

Note: Virtual accounts identified by the custom VA number will be the same as those identified by the customer VA identifier.

API Endpoints

Below are the API endpoints to be used by the platform basis the environments.

Response Keys

Below are the response keys propagated by Decentro in the response_key parameter, which cover all the scenarios a platform can encounter.