RBI · Razorpay OSSPublic DataReady to ship

IFSC / Bank Lookup API Integration

Resolve any Indian bank branch from an IFSC code — used for payouts, onboarding and validation.

Provider
RBI · Razorpay OSS
Version
v1.0
Uptime
99.99%
Latency
180 ms
Access
Public
BankBranch

What IFSC / Bank Lookup API integration does

IFSC lookup resolves any Indian bank branch from its eleven-character code, returning the bank, branch, address and the payment systems that branch supports. It is a small integration with an outsized effect on payout reliability.

The failure it prevents is expensive out of proportion to its size. A payout initiated against an invalid or mistyped IFSC fails at the bank, the money is returned days later, and in the meantime a customer, vendor or claimant believes they have been paid. Validating the code at data entry converts a multi-day reconciliation problem into an inline form error. Shipping a static IFSC list instead is a slow-burning version of the same problem, because branch data genuinely changes — mergers, closures and re-codings happen regularly.

What teams build with it

Beneficiary validation

Validate the IFSC at the point the customer enters it, so an invalid code is a form error rather than a failed transfer.

Payout preparation

Confirm bank and branch before initiating vendor, refund or claim disbursements.

Onboarding data quality

Auto-fill bank and branch names from the code to reduce typing and mismatches.

Master data cleanup

Re-validate stored bank details across an existing customer or vendor base to catch codes invalidated by mergers.

Endpoints included

  • GET/ifsc/v1/{code}
    Returns branch details for an IFSC code.

Try it in the sandbox

Returns branch details for an IFSC code.
GEThttps://sandbox.aeologic.io/ifsc/v1/{code}
Requestapplication/json
{
  "ifsc": "HDFC0001234"
}
Response
Run the sample to see a live response
Returns masked / synthetic data in Sandbox

What you need before we start

  • The IFSC codes to validate
  • A form or API surface where validation runs inline
  • A caching policy, since branch data changes slowly

How we deliver it

  1. Inline validation wired into your onboarding or payout form
  2. Sandbox integration and response mapping
  3. Caching layer for frequently used codes
  4. Optional batch re-validation across an existing master

Solution bundles that use it

IFSC / Bank Lookup API integration — FAQs

What does the lookup return?

Bank, branch, address and supported payment systems for the given IFSC code.

Why not just bundle a static IFSC list?

Because branch data changes — mergers, closures and re-codings happen regularly — and a stale list becomes a slow-burning source of failed payouts.

Is it free to use?

It is a public-access rail with no scheme licensing cost; you pay for the integration and throughput.

Ship IFSC / Bank Lookup in days

Tell us your stack and we'll wire up IFSC / Bank Lookup API integration for your team.

Talk to Aeologic