Status

Endpoint Overview

POST /api/v1/bank-verification/reverse-penny-drop/status

Description

This API endpoint allows you to check the status of a reverse penny drop verification process. Reverse penny drop is a method to verify bank account details by sending a small amount (typically one rupee) to the account and verifying the transaction details. This endpoint retrieves the current status and details of a previously initiated reverse penny drop verification using a unique client ID.

Key Benefits

Verify bank account ownership without requiring additional documentation

Confirm account holder name matches with the provided information

Reduce fraud by ensuring bank accounts belong to the intended recipients

Streamline customer onboarding with reliable bank account verification

Use Cases

Financial Services

Payroll & HR

Marketplace Platforms

Verify customer bank accounts during loan application processing

Validate payee accounts before setting up recurring payments

Confirm bank details during customer onboarding for investment platforms

Technical Implementation

Authentication

All API requests require authentication using a JWT Bearer token. Authentication follows these steps:

Obtain API Credentials: Register with Surepass to receive your API key.

Generate JWT Token: Use your API key to generate a JWT token.

Include in Requests: Add the token to the Authorization header as Bearer TOKEN.

Different authentication tokens are used for sandbox and production environments:

Sandbox: https://sandbox.surepass.io

Production: https://kyc-api.surepass.io

Request Parameters

Request Headers

Header	Required	Description
Authorization	Yes	Bearer token for authentication. Format: `Bearer YOUR_JWT_TOKEN`
Content-Type	Yes	Must be set to `application/json`

Request Body

Parameter	Type	Required	Description
client_id	String	Yes	The unique client ID obtained from the `initialize` endpoint for the reverse penny drop verification

Example Request

{
    "client_id": "reverse_penny_drop_jJhjvtijBXpKduHvxSUk"
}

Process Response

Response Parameters

Parameter	Type	Description
data	Object	Contains the verification results
data.client_id	String	The unique client ID for this verification
data.details	Object	Complete details of the bank account verification
data.details.account_number	String	The bank account number to which the payment was made
data.details.ifsc	String	The IFSC code of the bank associated with the account
data.details.upi_id	String	UPI ID used for the payment transaction (if applicable)
data.details.amount	String	The amount transferred in the transaction (typically "1" for penny drop)
data.details.payment_mode	String	Mode of payment used (e.g., UPI, NEFT)
data.details.holder_name	String	Name of the account holder as returned by the bank
data.details.type	String	Type of transaction (credit or debit)
data.details.remitter_name	String	Name of the person who initiated the payment
data.details.status	String	Status of the verification (success or failed)
status_code	Integer	HTTP status code of the response
success	Boolean	Indicates if the API request was successful
message	String	Human-readable message describing the result
message_code	String	Code representing the message for programmatic handling

Example Successful Response

{
    "data": {
        "client_id": "reverse_penny_drop_prtkdSoSybrlmvZkzfCi",
        "details": {
            "account_number": "77780101256547",
            "ifsc": "UBIN0123546",
            "upi_id": "test@ybl",
            "amount": "1",
            "payment_mode": "UPI",
            "holder_name": "TEST GUPTA",
            "type": "credit",
            "remitter_name": "TEST GUPTA",
            "status": "success"
        }
    },
    "status_code": 200,
    "success": true,
    "message": "Success",
    "message_code": "success"
}

Possible Error Responses

Invalid Client ID

Authentication Error

Verification Pending

{
    "status_code": 400,
    "success": false,
    "message": "Invalid client_id provided",
    "message_code": "invalid_client_id"
}

This error occurs when the provided client_id is invalid or does not exist in the system.

Integration Best Practices

Security Recommendations

Store JWT tokens securely and never expose them in client-side code

Implement proper error handling to avoid exposing sensitive information

Rotate JWT tokens periodically and don't reuse them across different environments

Use HTTPS for all API communications to ensure data encryption in transit

User Experience Guidelines

Implement appropriate loading states while waiting for verification results

Clearly communicate verification status to end-users with appropriate messaging

Provide clear instructions if verification fails and action is needed

Consider implementing a retry mechanism for failed verifications

Code Samples

cURL

Python

Node.js

Related APIs

Initialize Reverse Penny Drop: Initiates a new reverse penny drop verification process

Bank Account Verification: Verifies bank account details using various methods

UPI ID Verification: Validates UPI IDs and retrieves associated account information

Compliance and Legal Considerations

When implementing bank account verification, ensure you have appropriate consent from users to verify their bank accounts. The penny drop verification process involves making a small transaction to the user's account, which may appear on their bank statement. Clearly communicate this to users during the verification process. Additionally, ensure compliance with data protection regulations when storing and processing bank account information.

curl --location --request POST 'https://kyc-api.surepass.app/api/v1/bank-verification/reverse-penny-drop/status' \ --header 'Content-Type: application/json' \ --data-raw '{ "client_id": "reverse_penny_drop_jJhjvtijBXpKduHvxSUk" }'

{ "data": { "client_id": "reverse_penny_drop_prtkdSoSybrlmvZkzfCi", "details": { "account_number": "77780101256547", "ifsc": "UBIN0123546", "upi_id": "test@ybl", "amount": "1", "payment_mode": "UPI", "holder_name": "TEST GUPTA", "type": "credit", "remitter_name": "TEST GUPTA", "status": "success" } }, "status_code": 200, "success": true, "message": "Success", "message_code": "success" }

Status

Status#

Description#

Use Cases#

Technical Implementation#

Request Headers#

Request Body#

Example Request#

Response Parameters#

Example Successful Response#

Possible Error Responses#

Integration Best Practices#

Code Samples#

Request

Responses

Status

Description

Use Cases

Technical Implementation

Request Headers

Request Body

Example Request

Response Parameters

Example Successful Response

Possible Error Responses

Integration Best Practices

Code Samples