PPI Transaction Flow

1. First, you need to onboard your agents (users) using the Onboard Agent API. This is a one-time process for each agent on our platform.
2. Then, follow these guidelines to design the PPI transaction flow in your app:
   1. Check if the customer has already been onboarded on EKO’s platform using the Get Sender Information API.
      1. For a new customer, use the Onboard Sender , Verify Customer OTP,Validate Aadhar and Validate Pan APIs to onboard them on the platform.
         1. Note: OTPs will not be dispatched on UAT for testing.
      2. For an existing customer, use the Get Sender Information and Verify OTP APIs to get the customer monthly limit .
   2. Then, Get List of Recipients which are already registered for that customer.
   3. If the desired recipient is not registered, Add Recipient and Add Recipient Bank API for that customer.
   4. Then, use the PayPoint Transaction API to initiate PPI transaction to a registered recipient for that customer.
3. Also, note the following:
   1. Check the status of any transaction later using the Transaction Inquiry API.
   2. If the transaction goes into Refund Pending state, checkout the Initiate Refund API.

Every transaction response will contain a tx_status code with the following possible values:

In case if any other value is returned in tx_status parameter then the transaction should be treated as initiated and transaction inquiry should be done until final status is received.

❗️

Transaction Timeout

A transaction can timeout due to multiple reasons, such as, bad internet connection or slow response from the partner bank. In such cases, transaction should not be treated as declined or failed. Ideally, it should be inquired using the Transaction Inquiry API by the passing your own reference number, i.e., client_ref_id.