/

to search

Introducing Setu Changelog Check it out ↗

#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
CODEMESSAGE
BAV1000BAV invalid state
BAV00Transaction approved
BAV03Invalid scheme type
BAV08CBS offline
BAV12Invalid transaction
BAV17Exceeds account limit
BAV19Duplicate reference number
BAV20Invalid response code
BAV34Suspected fraud
BAV52Invalid account
BAV76Card-issuer timed out
BAV78Transfer limit exceeded
BAV84Block operation failed.since a/c is closed/frozen
BAV91Transaction timeout
BAV92Invalid ifsc or no routing for institution/network
BAV94Duplicate transaction
BAVNFSystem malfunction
BAVCUHost (CBS) offline
BAVXFInvalid response code
BAVFLDFailed txn by beneficiary bank
BAVIUIssuer node offline
BAVM0Verification successful but original credit transaction failed
BAVM1Either ifsc or bank account is invalid
BAVM2Amount limit exceeded
BAVM3Account blocked/frozen
BAVM4Nre account
BAVM5Account closed
BAVM6Limit exceeded for member bank
BAVM7Transaction not permitted to account
BAVM8Txn limit exeeded
BAVMICustomer tx. limit exceeded
BAVMJInvalid beneficiary IFSC or NBIN
BAVMNForeign inward remittance not allowed
BAVMPBenificary bank not enable for P2A
BAVMQTransaction not allowed as invalid payment reference
BAVMSTransaction is declined as invalid account number
BAVREFFunds refunded by remitter bank
BAVMTTransaction not allowed as general error
BAVMWForeign inward remittance for P2P only
BAV51Transaction unsuccessful due to an issue at the beneficiary bank's end.
BAVNCNo connectivity with NPCI
BAVNRNot registered
BAVRETFunds returned by beneficiary bank
BAVRM1Remittor CBS timeout while a/c enquiry
BAV1009Invalid amount
BAVXUCut-off is in process (beneficiary)
BAV1001Invalid tranaction type
BAV1004Blank trace number
BAV1008Invalid bene IFSC
BAV1010Invalid amount
BAV1012Invalid response from imps switch
BAV1013Duplicate trace id
BAV1014Invalid queryback trace number
BAV1015No such transaction request enquery
BAV1016Invalid sender mobile number
BAV1017Invalid remitter name
BAV2000Upsteam error
BAV2001Internal error

Was this page helpful?