• Credit

    US flag

  • Credit

    US flag

Fund Accounts

In this section we will understand how fund flow works for Pre Paid Instrument (PPI) accounts.

  • The fintech transfers funds from its current account to the Fintech’s current account of the sponsor IFI (eg RBL, IDFC)
  • Zeta Ops verifies the fund transfer and increases the limit of the Fintech Funding A/c
  • Account holder adds money to his PPI account
  • Fintech Triggers an A2A transfer API to debit the VBO Funding account and credit the account holder’s account
Depending upon the sponsor bank for the PPI program, the fund flow may have variations.

APIs for RAH funding

Fusion provides the following set of APIs to perform different operations of Real Account Holder (RAH) funding.

  • Fund Account Holder Account

  • Retrieve the Account balance

  • Retrieve the Account transaction

  • Reverse Account Transaction

Fund Account Holder Account

Fusion supports IMPS and NEFT fund transfer modes. Each mode is defined by a unique identifier, transferCode, which must be passed in the request body of the /transfers endpoint. Contact Zeta to know the supported transfer codes.

Support for UPI fund transfer is coming soon.

To fund the account, use the /transfers endpoint and provide the values for the following keys in the request body, as shown below:

  • transferCode: Required. Code to specify the mode of fund transfer like IMPS and NEFT.

  • debitAccountID: Required. ID of the fintech’s account from where the funds will be transferred. A fintech account is provisioned during the onboarding.

  • creditAccountID: Required. ID of the Account Holder’s account to which the funds will be transferred.

Input parameters

  • ifiID: Required. Unique identifier of the IFI.

  • Request id: Required.This identifier is used to identify a unique request

  • amount: Required. User needs to specify the amount that needs to be transferred. (In Paisa).

  • currency: Required. It shows the currency in which the money is transferred. (Length 16 characters).

  • transferCode: Required. Code to specify the mode of fund transfer like IMPS and NEFT.

  • debitAccountID: Required. Unique identifier of the fintech’s account from where the funds will be transferred. A fintech account is provisioned during the on-boarding.

  • creditAccountID: Required. Unique identifier of the Account Holder’s account to which the funds will be transferred.

  • transferTime: Optional. Time required to transfer funds.

  • remarks: Optional. Remark of the fund transfer.

Response parameters

  • Request id: This identifier is used to identify a unique request.

  • Transfer id: Unique identifier for the transaction. This will be used in case of reversals.

  • status: Status of the transfer. Value of this field can be Success/Failure

Retrieve the Account balance

You can retrieve the balance of an account by passing accountID as a path parameter in the balance endpoint, as shown below:

Input parameters

  • ifiID: Required. Unique identifier of the IFI.

  • accountID: Required. Unique identifier of the Account whose balance is to be retrieved.

Retrieve the Account transaction

In Fusion, a Transaction refers to any fund transfer from one account to another. To view transactions, pass accountID as a path parameter in the /transactions endpoint, as shown below. To get a paginated view, use pageSize and pageNumber query parameters.

Input parameters

  • ifiID: Required. Unique identifier of the IFI.

  • accountID: Required. Unique identifier of the Account whose balance is to be retrieved.

Reverse Account Transactions

In case of any disputes, pass transactionID as a path parameter to reverse fund transfer. For partial transaction reversals, set doPartialReversal to True.

Input parameters

  • ifiID: Required. Unique identifier of the IFI.

  • transactionID: Required. Unique identifier of the transaction for which the reversal is being triggered.

  • requestID: Required. Unique identifier of the A2A Reversal.

  • currency: Required. Currency for which reversal is required. For example, INR, USD, and more.

  • amount: Required. Amount that needs to be reversed.

  • doPartialReversal: Optional. Pass this as true for partial reversal or false for full reversal of transaction.

  • transferCode: Required. Code to specify the mode of fund transfer like IMPS and NEFT.

  • remarks: Optional. Remark of the fund reversal.

Withdrawal of funds from RAH account

Let us consider a scenario of fund transfer from one Real Account Holder (RAH) to another Legal Account Holder (LAH). In a card transaction, an individual swipes using the payment card at the merchant. The money travels from an individual’s account to the bank’s account.

Input parameters

  • ifiID: Required. Unique identifier of the IFI.

  • requestID: Required. This is generated by the requester. Should be globally unique. Zeta will reject a duplicate token generation request ID.

  • amount: Required. Amount that needs to be transferred. Possible value supported for currency are INR, USD, and more.

  • transferCode: Required. Code to specify the mode of fund transfer like IMPS and NEFT.

  • debitAccountID: Required. Unique identifier of the Real Account Holder’s account from where the funds will be transferred. A fintech * account is provisioned during the on-boarding.

  • creditAccountID: Required. Unique identifier of the Legal Account Holder’s account to which the funds will be transferred.

  • transferTime: Optional. Time required to transfer funds. remarks: Optional. Remark of the fund transfer.