API SuiteBanking & Financial
Verify Bank Account
Penny-drop style bank account verification with account number, IFSC, name, and phone. Server-side POST with Bearer auth.
API reference
Try itLoading playground…
Loading…
AuthorizationBearer <token>
JWT Bearer token authentication. Obtain a token from the KwikID dashboard.
In: header
accountstring
Bank account number to verify
namestring
Account holder name
phonestring
Registered phone number
ifscstring
IFSC code of the bank branch
Response Body
curl -X POST "https://__mock__/verification/v1/banking/verifyaccount/pennydrop" \ -H "Content-Type: application/json" \ -d '{ "account": "string", "name": "string", "phone": "string", "ifsc": "string" }'{
"status": "string",
"message": "string",
"account_details": {}
}{
"detail": {},
"message": "string"
}{
"detail": {},
"message": "string"
}Overview
Call POST /verification/v1/banking/verifyaccount/pennydrop from your backend with Authorization: Bearer <token> and JSON account, name, phone, and ifsc (all required in OpenAPI). On 200 OK, read status, message, and account_details for the verification outcome.
Key features
- Name + account match: Sends holder name alongside account and IFSC.
- Funds-rail safety: Run before enabling payouts or mandates.
Implementation
Step 1: Call from your backend
POST /verification/v1/banking/verifyaccount/pennydrop HTTP/1.1
Host: <verification-api-base-url>
Authorization: Bearer <token>
Content-Type: application/json
{
"account": "1234567890",
"name": "ACCOUNT HOLDER NAME",
"phone": "9876543210",
"ifsc": "HDFC0000001"
}Error handling
| HTTP status | When |
|---|---|
| 400 | Validation error. |
| 401 | Invalid token. |
Security notes
- Never send this payload from an untrusted browser; keep Bearer on server.
Benefits
- Confirms account is reachable and matches holder name before money movement.