#Sync API
The following guide describes a sync API implementation for bank account verification. This lets you initiate a verification request and expect an immediate response on the status of the verification. Essentially, you will need the following API—
- Verify bank account—This lets you initiate a verification request, and get verification status in response.
Here are the URLs you would need for this integration—
- Sandbox—
https://dg-sandbox.setu.co
- Production—
https://dg.setu.co
- Headers—Contact Setu for providing the credentials required to successfully call Setu APIs. This contains:
x-client-id
x-client-secret
x-product-instance-id
While this is a simpler implementation, the experience for your end customer may be better handled with our async APIs, that let you asynchronously fetch the status associated with a bank verification request.
You can update the pending
status on your UI , whenever the new status is available, rather than letting your customer wait for a response on the UI.
#Verify bank account
Call this API to verify bank account 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.
While testing on Sandbox, you may use the following sample values—
- Use ABCD0123456 (IFSC) and 1234567890 (account number) to get a successful verification response.
- Use DCBA6543210 (IFSC) and 0987654321 (account number) to get a failed verification response.
Your request contains a valid bank account
and Setu has processed your request successfully.
Request
POST /api/verify/ban{"ifsc": "CNRB0008517","accountNumber": "8517129000033"}
Response
{"code": "BAV00", // BAV Code"verification": "success","message": "Account exists and is active.","data": {"name": "name of the account holder","transactionReference": "120716373986","verifiedAt": "2017-08-28T09:36:18+00:00"},"id": "d9342684-1300-4fa8-8344-cc861a20a477","traceId": "..."}
BAV Codes
CODE | MESSAGE |
---|---|
BAV1000 | BAV invalid state |
BAV00 | Transaction approved |
BAV03 | Invalid scheme type |
BAV08 | CBS offline |
BAV12 | Invalid transaction |
BAV17 | Exceeds account limit |
BAV19 | Duplicate reference number |
BAV20 | Invalid response code |
BAV34 | Suspected fraud |
BAV52 | Invalid account |
BAV76 | Card-issuer timed out |
BAV78 | Transfer limit exceeded |
BAV84 | Block operation failed.since a/c is closed/frozen |
BAV91 | Transaction timeout |
BAV92 | Invalid ifsc or no routing for institution/network |
BAV94 | Duplicate transaction |
BAVNF | System malfunction |
BAVCU | Host (CBS) offline |
BAVXF | Invalid response code |
BAVFLD | Failed txn by beneficiary bank |
BAVIU | Issuer node offline |
BAVM0 | Verification successful but original credit transaction failed |
BAVM1 | Either ifsc or bank account is invalid |
BAVM2 | Amount limit exceeded |
BAVM3 | Account blocked/frozen |
BAVM4 | Nre account |
BAVM5 | Account closed |
BAVM6 | Limit exceeded for member bank |
BAVM7 | Transaction not permitted to account |
BAVM8 | Txn limit exeeded |
BAVMI | Customer tx. limit exceeded |
BAVMJ | Invalid beneficiary IFSC or NBIN |
BAVMN | Foreign inward remittance not allowed |
BAVMP | Benificary bank not enable for P2A |
BAVMQ | Transaction not allowed as invalid payment reference |
BAVMS | Transaction is declined as invalid account number |
BAVREF | Funds refunded by remitter bank |
BAVMT | Transaction not allowed as general error |
BAVMW | Foreign inward remittance for P2P only |
BAV51 | Transaction unsuccessful due to an issue at the beneficiary bank's end. |
BAVNC | No connectivity with NPCI |
BAVNR | Not registered |
BAVRET | Funds returned by beneficiary bank |
BAVRM1 | Remittor CBS timeout while a/c enquiry |
BAV1009 | Invalid amount |
BAVXU | Cut-off is in process (beneficiary) |
BAV1001 | Invalid tranaction type |
BAV1004 | Blank trace number |
BAV1008 | Invalid bene IFSC |
BAV1010 | Invalid amount |
BAV1012 | Invalid response from imps switch |
BAV1013 | Duplicate trace id |
BAV1014 | Invalid queryback trace number |
BAV1015 | No such transaction request enquery |
BAV1016 | Invalid sender mobile number |
BAV1017 | Invalid remitter name |
BAV2000 | Upsteam error |
BAV2001 | Internal error |
Was this page helpful?