Comprehensive Financial Validation API for validating IFSC codes, IBANs, and US routing numbers. The IFSC validation includes format checks and optional reference lookups, while IBAN validation ensures structural integrity and checksum accuracy without confirming account existence. The routing number endpoints incorporate checksum validation alongside a FedACH-based bank directory for accurate routing information.
{
"input": "HDFC0001234",
"normalized": "HDFC0001234",
"valid": true,
"reason": "ok",
"reference_match": true,
"reference_status": "matched",
"branch": {
"ifsc_code": "HDFC0001234",
"bank_name": "HDFC Bank",
"branch_name": "PARK STREET",
"city": "JAIPUR",
"district": "JAIPUR",
"state": "RAJASTHAN",
"source": "razorpay_ifsc"
},
"attribution": [
{
"source": "Reserve Bank of India (RBI)",
"dataset": "Bank branch and IFSC reference publications",
"license": "Public reference data (verify latest RBI terms)",
"url": "https://www.rbi.org.in/",
"notice": "IFSC checks include format validation and can be augmented with RBI reference datasets for branch-level verification."
},
{
"source": "Federal Reserve Financial Services",
"dataset": "FedACH Routing Directory",
"license": "U.S. federal reference data",
"url": "https://www.frbservices.org/resources/routing-number-directory",
"notice": "US routing-number checks use checksum validation and can be matched against FedACH routing directory records for bank-level lookup."
},
{
"source": "ISO 13616 / IBAN specification",
"dataset": "IBAN structure and checksum rules",
"license": "Specification-derived validation logic",
"notice": "IBAN endpoint validates structure and checksum only and does not confirm account existence."
}
]
}
curl --location --request GET 'https://zylalabs.com/api/13400/quick+financial+validation+api/28735/check+ifsc+code?ifsc=HDFC0001234' --header 'Authorization: Bearer YOUR_API_KEY'
{
"input": "GB82WEST12345698765432",
"normalized": "GB82WEST12345698765432",
"country_code": "GB",
"expected_length": 22,
"actual_length": 22,
"checksum_valid": true,
"valid": true,
"reason": "ok",
"attribution": [
{
"source": "Reserve Bank of India (RBI)",
"dataset": "Bank branch and IFSC reference publications",
"license": "Public reference data (verify latest RBI terms)",
"url": "https://www.rbi.org.in/",
"notice": "IFSC checks include format validation and can be augmented with RBI reference datasets for branch-level verification."
},
{
"source": "Federal Reserve Financial Services",
"dataset": "FedACH Routing Directory",
"license": "U.S. federal reference data",
"url": "https://www.frbservices.org/resources/routing-number-directory",
"notice": "US routing-number checks use checksum validation and can be matched against FedACH routing directory records for bank-level lookup."
},
{
"source": "ISO 13616 / IBAN specification",
"dataset": "IBAN structure and checksum rules",
"license": "Specification-derived validation logic",
"notice": "IBAN endpoint validates structure and checksum only and does not confirm account existence."
}
]
}
curl --location --request GET 'https://zylalabs.com/api/13400/quick+financial+validation+api/28736/verify+iban+format?iban=GB82WEST12345698765432' --header 'Authorization: Bearer YOUR_API_KEY'
{
"input": "021000021",
"normalized": "021000021",
"checksum_valid": true,
"valid": true,
"reason": "ok",
"reference_status": "matched",
"reference_match": true,
"bank": {
"routing_number": "021000021",
"customer_name": "JPMORGAN CHASE",
"city": "TAMPA",
"state": "FL",
"zip_code": "336100000",
"phone": "8134323700",
"institution_status_code": "1",
"source": "fedach",
"updated_at": "2026-07-29T17:19:03.916039Z"
},
"attribution": [
{
"source": "Reserve Bank of India (RBI)",
"dataset": "Bank branch and IFSC reference publications",
"license": "Public reference data (verify latest RBI terms)",
"url": "https://www.rbi.org.in/",
"notice": "IFSC checks include format validation and can be augmented with RBI reference datasets for branch-level verification."
},
{
"source": "Federal Reserve Financial Services",
"dataset": "FedACH Routing Directory",
"license": "U.S. federal reference data",
"url": "https://www.frbservices.org/resources/routing-number-directory",
"notice": "US routing-number checks use checksum validation and can be matched against FedACH routing directory records for bank-level lookup."
},
{
"source": "ISO 13616 / IBAN specification",
"dataset": "IBAN structure and checksum rules",
"license": "Specification-derived validation logic",
"notice": "IBAN endpoint validates structure and checksum only and does not confirm account existence."
}
]
}
curl --location --request GET 'https://zylalabs.com/api/13400/quick+financial+validation+api/28737/verify+routing+number?routing_number=021000021' --header 'Authorization: Bearer YOUR_API_KEY'
{
"input": "021000021",
"found": true,
"bank": {
"routing_number": "021000021",
"customer_name": "JPMORGAN CHASE",
"address": "3RD FLOOR",
"city": "TAMPA",
"state": "FL",
"zip_code": "336100000",
"phone": "8134323700",
"office_code": "O",
"record_type_code": "1",
"servicing_frb_number": "021001208",
"institution_status_code": "1",
"data_view_code": "1",
"source": "fedach",
"updated_at": "2026-07-29T17:19:03.916039Z"
},
"attribution": [
{
"source": "Reserve Bank of India (RBI)",
"dataset": "Bank branch and IFSC reference publications",
"license": "Public reference data (verify latest RBI terms)",
"url": "https://www.rbi.org.in/",
"notice": "IFSC checks include format validation and can be augmented with RBI reference datasets for branch-level verification."
},
{
"source": "Federal Reserve Financial Services",
"dataset": "FedACH Routing Directory",
"license": "U.S. federal reference data",
"url": "https://www.frbservices.org/resources/routing-number-directory",
"notice": "US routing-number checks use checksum validation and can be matched against FedACH routing directory records for bank-level lookup."
},
{
"source": "ISO 13616 / IBAN specification",
"dataset": "IBAN structure and checksum rules",
"license": "Specification-derived validation logic",
"notice": "IBAN endpoint validates structure and checksum only and does not confirm account existence."
}
]
}
curl --location --request GET 'https://zylalabs.com/api/13400/quick+financial+validation+api/28738/retrieve+bank+details+by+routing+number?routing_number=021000021' --header 'Authorization: Bearer YOUR_API_KEY'
After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the Quick Financial Validation API simply include your bearer token in the Authorization header.
| Header | Description |
|---|---|
Authorization
|
Required
Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.
|
No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
(Save 2 months with annual billing 🎉)
Trusted by leading companies
Comprehensive Financial Validation API for validating IFSC codes, IBANs, and US routing numbers. The IFSC validation includes format checks and optional reference lookups, while IBAN validation ensures structural integrity and checksum accuracy without confirming account existence. The routing number endpoints incorporate checksum validation alongside a FedACH-based bank directory for accurate routing information.
Each endpoint returns specific financial validation data. The IFSC endpoint provides details like bank name, branch location, and validity status. The IBAN endpoint returns format validity, expected length, and checksum status. The routing number endpoints offer bank name, address, and transaction types supported.
Key fields include "valid" and "reason" for validation status, "bank_name" and "branch_name" for IFSC, "country_code" and "checksum_valid" for IBAN, and "customer_name" and "address" for routing numbers. These fields help users assess the accuracy of financial information.
The returned data is structured in JSON format, containing nested objects for detailed information. Each response includes fields like "input," "valid," and specific details related to the financial code being validated, ensuring clarity and ease of use.
The IFSC endpoint provides bank and branch details, the IBAN endpoint checks format and checksum validity, while the routing number endpoints deliver bank information and transaction capabilities. This comprehensive data supports various financial operations.
Data is sourced from reputable institutions such as the Reserve Bank of India (RBI) for IFSC codes and the Federal Reserve for routing numbers. These sources ensure high accuracy and reliability in the validation process.
Data accuracy is maintained through regular updates from authoritative sources and validation checks, such as format and checksum verifications. This ensures that users receive reliable and up-to-date financial information.
Typical use cases include validating bank details for fund transfers, integrating banking functionalities in applications, and ensuring correct payment processing in e-commerce. This helps reduce errors and enhances user experience.
Users can utilize the returned data by checking the "valid" field to confirm the accuracy of financial codes. They can also leverage detailed information like bank names and addresses for transaction processing and customer verification.
To obtain your API key, first sign in to your account and navigate to the API you want to use. From the API's Pricing section, choose a plan and complete the subscription process. Once subscribed, return to the API page and you will see your API Access Key displayed at the top of the documentation page. You can use this key to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
The free trial lasts for 7 days and allows you to make up to 50 API requests.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes. If the API offers a free trial, you will see a "Free 7-Day Trial" option in its Pricing section. The trial lasts for 7 days and allows up to 50 API requests, enabling you to evaluate the API before subscribing to a paid plan.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
You can monitor your API usage through the response headers included with every request:
x-zyla-api-calls-monthly-used: Shows the total number of API requests you have used during the current billing period.
x-zyla-api-calls-monthly-remaining: Shows the number of API requests you have remaining for the current billing period.
Yes, you can cancel your subscription at any time. Simply go to the Pricing section of the API you're subscribed to and click the "Unsubscribe" button.
Please note that upgrades, downgrades, and cancellations take effect immediately. Once your subscription is canceled, access to the service will end immediately, regardless of any remaining API calls in your quota.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund