Bank AccountPenny Drop

Bank Account Verification — Penny Drop

Verify a bank account with a penny drop transaction. Confirm the account holder's name and ensure the account is active before processing payments.

curl -X GET "https://production.deepvue.tech/v1/verification/bankaccount?account_number=example_string&ifsc=example_string&name=John Doe" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_TOKEN (JWT)" \
  -H "x-api-key: YOUR_API_KEY"
{
  "code": 200,
  "timestamp": 1738042952419,
  "transaction_id": "fe104a7a-f3a9-4365-9390-e3af0e4193e5",
  "data": {
    "message": "Bank Account details verified successfully.",
    "account_exists": true,
    "name_at_bank": "Master NIHARika  .",
    "utr": "502811454342",
    "amount_deposited": 1,
    "name_information": {
      "name_at_bank_cleaned": "Master Niharkika"
    }
  }
}
GET
/v1/verification/bankaccount
GET
Bearer Token (JWT)
Bearer Tokenstring
Required

ACCESS_TOKEN generated from the authorize endpoint. Should be included in the header as Bearer .

ACCESS_TOKEN generated from the authorize endpoint. Should be included in the header as Bearer .
API Key (header: x-api-key)
x-api-keystring
Required

The CLIENT_SECRET provided to you. This header parameter is required for authentication purposes.

The CLIENT_SECRET provided to you. This header parameter is required for authentication purposes.
Request Preview
Response

Response will appear here after sending the request

Authentication

header
Authorizationstring
Required

Bearer token (JWT). ACCESS_TOKEN generated from the authorize endpoint. Should be included in the header as Bearer .

header
x-api-keystring
Required

API Key for authentication. The CLIENT_SECRET provided to you. This header parameter is required for authentication purposes.

Query Parameters

Responses

codeinteger
timestampinteger
transaction_idstring
dataobject

Overview

The Penny Drop API enables bank account verification through a penny drop check mechanism. The service validates a customer's bank account and IFSC code combination by depositing 1 INR into the specified account, then retrieving the associated account information in return.

This verification method authenticates customer bank account details for KYC (Know Your Customer) compliance and account onboarding workflows.

Billing only occurs when the API returns a 200 status code response.

Response scenarios

Successful verification returns account existence confirmation, name-at-bank details, UTR reference number, and deposited amount. The response may also indicate various non-verification states including invalid credentials, blocked accounts, invalid IFSC codes, or NRE (Non-Resident External) account detection.

The API relies on bank connectivity and NPCI (National Payments Corporation of India) availability. Service disruptions may occur if beneficiary banks are offline, source banks decline requests, or NPCI services are unavailable.