Penny drop and reverse penny drop bank/VPA validation
openapi: 3.0.0
info:
title: Razorpay Bills X Account Validation API
version: 1.0.0
description: Razorpay payment gateway APIs for accepting payments, managing orders, processing refunds, payouts, and subscriptions. All amounts are in the smallest currency sub-unit (e.g. paise for INR). Supports 180+ payment methods including UPI, cards, netbanking, wallets, and EMI.
termsOfService: https://razorpay.com/terms/
contact:
name: Razorpay Support
url: https://razorpay.com/support/
email: support@razorpay.com
license:
name: Proprietary
url: https://razorpay.com/terms/
x-logo:
url: https://razorpay.com/favicon.png
x-auth-environments:
test:
keyPrefix: rzp_test_
description: Test mode — keys prefixed rzp_test_. Same API endpoint (https://api.razorpay.com/v1). No real money movement. Use test card numbers from https://razorpay.com/docs/payments/payments/test-card-details/.
live:
keyPrefix: rzp_live_
description: Live mode — keys prefixed rzp_live_. Real money movement. Requires KYC and business activation on the Razorpay Dashboard.
servers:
- url: https://api.razorpay.com/v1
description: Production
security:
- basicAuth: []
- oauth2:
- read_only
tags:
- name: X Account Validation
description: Penny drop and reverse penny drop bank/VPA validation
paths:
/fund_accounts/validations:
post:
operationId: validateFundAccount
summary: Validate a bank account or VPA
description: 'Three validation methods: (1) penny drop for bank accounts — sends Re.1 to verify; (2) penny drop for VPA — sends Re.1 to UPI address; (3) reverse penny drop — sends UPI intent URL to customer who initiates payment. Live-mode only, RazorpayX Lite account required. Composite validation (creates Contact + Fund Account inline) supported via validation_type field.'
tags:
- X Account Validation
requestBody:
required: true
content:
application/json:
schema:
type: object
required:
- account_type
- fund_account
properties:
account_type:
type: string
enum:
- bank_account
- vpa
fund_account:
type: object
description: For composite validation, include contact object instead of contact_id
amount:
type: integer
description: Penny drop amount in paise (typically 100)
currency:
type: string
default: INR
notes:
type: object
receipt:
type: string
validation_type:
type: string
enum:
- pennydrop
- penniless
- optimized
description: penniless = reverse penny drop (UPI intent); optimized = system chooses best method
responses:
'200':
description: Validation created
content:
application/json:
schema:
$ref: '#/components/schemas/FundAccountValidation'
'400':
$ref: '#/components/responses/400'
'401':
$ref: '#/components/responses/401'
'429':
$ref: '#/components/responses/429'
'500':
$ref: '#/components/responses/500'
get:
operationId: listFundAccountValidations
summary: List fund account validations
tags:
- X Account Validation
parameters:
- name: from
in: query
schema:
type: integer
description: Unix timestamp. Only validations created from this timestamp onwards are returned.
- name: to
in: query
schema:
type: integer
description: Unix timestamp. Only validations created before this timestamp are returned.
- name: count
in: query
schema:
type: integer
default: 10
description: 'Number of validation records to return. Default: 10. Maximum: 100.'
- name: skip
in: query
schema:
type: integer
default: 0
description: 'Number of validation records to skip. Use for pagination. Default: 0.'
responses:
'200':
description: List of validations
content:
application/json:
schema:
type: object
properties:
entity:
type: string
enum:
- collection
count:
type: integer
items:
type: array
items:
$ref: '#/components/schemas/FundAccountValidation'
'400':
$ref: '#/components/responses/400'
'401':
$ref: '#/components/responses/401'
'429':
$ref: '#/components/responses/429'
'500':
$ref: '#/components/responses/500'
description: List all fund account validation records, optionally filtered by date range.
/fund_accounts/validations/{validation_id}:
parameters:
- name: validation_id
in: path
required: true
schema:
type: string
description: Unique identifier of the fund account validation (e.g. `fav_00000000000001`).
get:
operationId: fetchFundAccountValidation
summary: Fetch a fund account validation
tags:
- X Account Validation
responses:
'200':
description: Validation details
content:
application/json:
schema:
$ref: '#/components/schemas/FundAccountValidation'
'400':
$ref: '#/components/responses/400'
'401':
$ref: '#/components/responses/401'
'429':
$ref: '#/components/responses/429'
'500':
$ref: '#/components/responses/500'
'404':
$ref: '#/components/responses/404'
description: Fetch details of a specific fund account validation by its ID.
components:
responses:
'404':
description: Resource not found.
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'400':
description: Bad request. Invalid parameters or missing required fields.
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'401':
description: Authentication failed. Invalid or missing API key credentials.
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'500':
description: Internal server error.
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'429':
description: Rate limit exceeded. Implement exponential backoff with jitter before retrying.
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
schemas:
Error:
type: object
properties:
error:
type: object
properties:
code:
type: string
description: 'Error code. Examples: BAD_REQUEST_ERROR, GATEWAY_ERROR, SERVER_ERROR.'
description:
type: string
source:
type: string
description: Where the error originated (e.g. business, gateway).
step:
type: string
reason:
type: string
description: 'Machine-readable reason. Examples: insufficient_funds, invalid_expiry_date, declined_by_bank.'
metadata:
type: object
field:
type: string
FundAccountValidation:
type: object
description: Bank/VPA account validation result. Live-mode only, RazorpayX Lite only.
properties:
id:
type: string
description: Validation ID (fav_*)
entity:
type: string
enum:
- fund_account.validation
status:
type: string
enum:
- created
- completed
- failed
amount:
type: integer
description: Penny drop amount in paise
currency:
type: string
utr:
type: string
reference_id:
type: string
notes:
type: object
validated_account_type:
type: string
fund_account:
type: object
properties:
id:
type: string
account_type:
type: string
bank_account:
type: object
vpa:
type: object
validation_results:
type: object
properties:
account_status:
type: string
registered_name:
type: string
name_match_score:
type: integer
details:
type: object
status_details:
type: object
upi_intent:
type: object
description: Present only for reverse penny drop (UPI intent flow)
properties:
intent_url:
type: string
phonepe_url:
type: string
gpay_url:
type: string
paytm_url:
type: string
bhim_url:
type: string
encoded_qr_code:
type: string
created_at:
type: integer
securitySchemes:
basicAuth:
type: http
scheme: basic
description: HTTP Basic authentication using your Razorpay API key pair. Use key_id as the username and key_secret as the password. Encode as Base64(key_id:key_secret). Keys are environment-scoped (Test vs Live). Obtain keys at https://dashboard.razorpay.com/app/keys. Keys are case-sensitive.
oauth2:
type: oauth2
description: OAuth 2.0 via the Razorpay MCP server (mcp.razorpay.com). Supports Authorization Code with PKCE (S256) for user-delegated access and Client Credentials for server-to-server access. Tokens expire in 3600 seconds. Dynamic Client Registration available at the registration endpoint. For integration setup see https://razorpay.com/docs/build/llm-docs/mcp-server/oauth.md.
flows:
authorizationCode:
authorizationUrl: https://mcp.razorpay.com/authorize
tokenUrl: https://mcp.razorpay.com/token
refreshUrl: https://mcp.razorpay.com/token
scopes:
read_only: Read-only access to Razorpay account data (payments, orders, refunds, payouts, subscriptions, invoices)
clientCredentials:
tokenUrl: https://mcp.razorpay.com/token
scopes:
read_only: Read-only access to Razorpay account data (payments, orders, refunds, payouts, subscriptions, invoices)
externalDocs:
description: Razorpay API Documentation
url: https://razorpay.com/docs/api/
x-tagGroups:
- name: Core Payments
tags:
- Orders
- Payments
- Refunds
- Payment Downtimes
- name: Payment Collection
tags:
- Payment Links
- QR Codes
- name: Billing & Subscriptions
tags:
- Items
- Invoices
- Plans
- Subscriptions
- name: Customer Management
tags:
- Customers
- Documents
- name: Finance & Reconciliation
tags:
- Settlements
- Instant Settlements
- Disputes
- name: Route & Marketplace
tags:
- Linked Accounts
- Transfers
- name: Smart Collect
tags:
- Virtual Accounts
- name: Partners & Onboarding
tags:
- Partner Accounts
- Partner Products
- Partner Stakeholders
- Partner Documents
- Partner Webhooks
- name: Bills
tags:
- Bills
- name: RazorpayX
tags:
- X Contacts
- X Fund Accounts
- X Account Validation
- X Banking Balances
- X Payouts
- X Payout Links
- X Transactions
x-rateLimit:
description: Razorpay does not publish specific rate limits. If you receive HTTP 429, implement exponential backoff with jitter and retry. Add randomisation to avoid thundering-herd effects.
throttleStatus: 429
strategy: exponential backoff with jitter
x-pagination:
description: All list endpoints return at most 100 records per call (1000 for settlement recon). Use count and skip together to paginate. Date range filters (from/to) use Unix timestamps in seconds.
example: GET /payments?from=1700000000&to=1700086400&count=100&skip=100
x-amountEncoding:
description: 'All monetary amounts are in the smallest currency sub-unit. For INR: 1 rupee = 100 paise, so ₹500 = 50000. Minimum for INR is 100 paise (₹1). Three-decimal currencies (KWD, BHD, OMR): drop last decimal digit. Zero-decimal currencies (JPY): pass value as-is.'