Bank Account Verification — Digio

Created by Rajatha B M, Modified on Fri, 27 Mar at 2:33 PM by Rajatha B M

What does this API do?

The Bank Account Verification API (powered by Digio Tech Solution Pvt Ltd) allows lenders to validate a customer's bank account details without initiating a financial transaction. It supports multiple verification modes — Penny Drop, Penny Less, and Auto — and returns real-time results including the account holder's name and an optional fuzzy name-match score. This enables faster onboarding, reduced transaction failures, and stronger compliance with regulatory standards.

Who can use it?

Any lender or financial institution that has been onboarded to the ULI Platform and has subscribed to the Digio service in the Platform Developer Portal.

Prerequisites

Complete all common platform prerequisites as described in Getting Started with ULI Platform APIs.

In addition, the following is specific to this API:

  • Digio Service Credentials: You must obtain a Client ID and Client Secret from Digio. These are separate from your ULI Platform credentials and must be stored securely by the lender. Separate credentials are required for Sandbox and Production environments.
  • Digio Service Subscription: Subscribe to the Digio Bank Account Verification service in the Platform Developer Portal (separately for Sandbox and Production). Refer to Section 10 of the SOP for Lender Onboarding for subscription steps.

What are the API endpoints?

EnvironmentURL
Sandboxhttps://extgw.nonprod.rbihub.io/digio/verify/bank-account/1.0/en
Productionhttps://extgw.api.rbihub.io/digio/verify/bank-account/1.0/en

HTTP method: POST

URL path follows the convention: /{serviceName}/{ver}/{lang}

URL ParameterDescriptionValue
serviceNameUnique name of the servicedigio/verify/bank-account
verCurrent version of the API1.0
langLanguage for the responseen

What headers are required?

HeaderDescriptionRemarks
AuthorizationJWT token generated by the authentication serverRefer to the Authentication and Authorization API specification
client-idBase64-encoded Client ID issued by the platformRequired
providerService provider codeUse 138 for Digio
x-sp-authorizationBasic authentication — Base64-encoded value of the Digio-issued username and passwordRequired
api-key24-character alphanumeric key issued by the platformOptional; reserved for future use
x-env-routeRequired to route requests to the sandbox environmentSet to /sb for Sandbox only; omit for Production

What does the request body look like?

The API accepts JSON. The top-level structure contains three objects:

FieldTypeDescriptionRequired
metaObjectMetadata including API version, timestamp, and transaction codeYes
dataObjectCore account verification detailsYes
hmacStringSHA-256 HMAC signature of the Base64-encoded data field for integrity validationYes

meta object fields:

FieldTypeDescriptionRequired
verStringAPI version. Example: 1.0Yes
tsStringRequest timestamp in ISO-8601 format (yyyy-MM-ddTHH:mm:ssZ). Example: 2025-05-22T14:30:00ZYes
txncodeStringUnique transaction code for tracing the request. Example: 324242Yes

data object fields:

FieldTypeDescriptionRequired
beneficiary_account_noStringBank account number to be verified (8–18 characters)Yes
beneficiary_ifscStringIFSC code of the bank branchYes
beneficiary_nameStringAccount holder name for optional fuzzy matchingOptional
validation_modeEnumVerification method: PENNY_DROP, PENNY_LESS, or AUTO. Defaults to PENNY_DROPOptional
amountBigDecimalAmount used for penny drop. Default is ₹1Optional
narrationStringOptional transaction narration textOptional
unique_request_idStringUnique identifier for traceability (1–70 characters)Optional

What do the response fields mean?

Top-level response fields:

FieldTypeDescription
resultObjectContains status and error information
dataObjectAccount verification results
signatureStringDigital signature of the response payload for integrity verification
metaObjectTransaction metadata (version, timestamp, transaction code)
hmacStringSHA-256 HMAC of the data field; generated by the platform
publickeyStringPublic key used to verify the signature
sig-algoStringSigning algorithm used, e.g. SHA256withECDSA

result object fields:

FieldTypeDescription
errcodeStringE000 on success; a relevant error code on failure
statusStringsuccess or fail
infoStringEmpty string on success; error description on failure

data object fields:

FieldTypeDescription
idStringUnique identifier for the verification request
verifiedBooleantrue if the account was verified successfully; false otherwise
verified_atStringTimestamp of verification in yyyy-MM-dd HH:mm:ss format
beneficiary_name_with_bankStringAccount holder name as returned by the bank
fuzzy_match_resultBooleanResult of fuzzy name match, if a name was provided in the request
fuzzy_match_scoreIntegerName-match score from 0 to 100
validation_modeEnumVerification mode used; default is PENNY_DROP
error_msgStringError message from the bank, if any
error_codeStringError code received during verification

Sample response:

{
  "result": {
    "errcode": "E000",
    "status": "success",
    "info": ""
  },
  "data": {
    "verified_at": "2025-05-19 12:19:32",
    "fuzzy_match_result": true,
    "verified": true,
    "beneficiary_name_with_bank": "JOHN DOE",
    "id": "HGBDEH7282",
    "fuzzy_match_score": 100
  },
  "meta": {
    "txncode": "324242",
    "ver": "1.0",
    "ts": "2025-05-19T12:19:32+0530"
  }
}

What are the error codes?

For the full list of platform-wide error codes, refer to the Latest Platform Error Code document. The following are Digio-specific error codes:

Error CodeDescription
EDI001Please provide a valid beneficiary account number
EDI003Please provide a valid beneficiary account IFSC code
EDI005Invalid x-sp-authorization
EDI006Must be one of PENNY_DROP, PENNY_LESS, AUTO
EDI007Invalid amount

Who do I contact for support?

If you encounter an issue, email support@rbihub.in with the following details:

  • Subject: Bank Account Verification API Error
  • Service Name: Bank Account Verification
  • Environment: Sandbox or Production
  • Service Provider: Digio
  • Request headers and payload
  • Error code and error message received
  • Prerequisites status: IP Whitelisting, URL Whitelisting, Service Subscription, Token Generation
  • Screenshot or log of the error (as attachment)

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article