The following guide describes an async implementation of our bank account verification APIs. This lets you initiate a verification request and let it complete asynchronously—without having to wait for an immediate response. Essentially, you will need the following 2 APIs—
Verify bank account—This lets you initiate a verification request.
Get verification request details—This lets you check the status associated with the verification request.
Here are the URLs you would need for this integration—
Headers—Contact Setu for providing the credentials required to successfully call Setu APIs. This contains:
Call this API to initiate bank account verification of your customer. A quick explanation of the request params—
ifsc is the IFSC (Indian Financial System Code) of the bank branch, where the bank account is held.
accountNumber is the bank account number that has to be verified.
narration is the reason for carrying out bank account verification
While testing on Sandbox, you may use sample values to mimic real-life scenarios. Use the below values to get specific responses from the Get verification request details API.
Set the accountNumber value as 1234567890 always. Use the ifsc values as mentioned below, to mimic respective scenarios—
ABCD0123456—successful verification response.
ABCD0123457—invalid transaction response. This may happen if the provided account does not support IMPS transactions.
ABCD0123458—transaction limit may have been reached. This may happen if, at the time of the penny drop, the transaction breaches the the daily IMPS limit for the account. While this is rare, it is still a possibility.
ABCD0123459—downstream service error.
ABCD0123467—invalid account details.
Your request contains a valid bank account number and the verification request has been successfully initiated.
"narration":"test transaction for verification"
You get an id associated with the verification request, which you can use to check verification status asynchronously.