IFSC sources and methodology
Pinned reference
The private reference contains all 183,214 valid IFSCs in Razorpay v2.0.62, released 1 September 2026 and representing an RBI update dated 15 August 2026. Local review: 4 October 2026. Razorpay identifies upstream RBI and NPCI inputs; ILeven has not independently certified current bank details.
Normalization and publication
Each valid IFSC remains distinct. Matching names or addresses do not prove duplicates, closure or merger. Contradictory case-variant capability fields become unresolved; disputed claims and missing optional fields are omitted. Records without a usable bank, branch, state, city or address remain finder-only. Raw location strings are not converted into assumed geographic entities.
Updates
Candidate releases are compared privately for additions, source disappearances and field changes. Review is required before promotion. Disappearance does not imply retirement or replacement. Existing canonical URLs remain fixed when descriptions change; deliberate changes require a one-hop permanent redirect.
Search privacy
Same-origin POST searches use a private on-disk index. Browsers receive bounded answers, not a bulk dataset; no live Razorpay service handles ordinary lookups. Application code does not intentionally log raw queries. Short-lived answer caches and security buckets use keyed identifiers. Infrastructure can retain technical/security logs. Do not enter personal or account details.
Attribution and limits
The pinned README describes its dataset as public domain and its code as MIT licensed. This implementation uses the dataset, not copied Razorpay application code. Source attribution implies no bank, government, RBI, NPCI or Razorpay affiliation. Verify critical information independently.
Corrections
Send the IFSC, source link and date to hello@ileven.in. Review precedes any correction.
