Bank data changes
Institutions merge, branches change and routing identifiers are updated.
Routing data before payment execution
Give bank and payment operations teams access to bank, branch and routing information before payments are sent. Use API queries or monthly export files to support routing readiness across supported markets.
Bank and payment operations teams need a clear view of the routing information a payment flow depends on before it enters the payment network.
Institutions merge, branches change and routing identifiers are updated.
Routing formats and required fields differ across countries and payment systems.
Payment flows need the routing details their workflow requires.
Bank Reference Data
Access available reference information for supported markets to identify financial institutions and support payment routing across different countries.
Review available routing information when a payment flow needs it.
Individual lookupsIntegrate reference information into internal payment systems and directories.
Data for workflowsWork with institution, branch, location and market details where they are available.
Field scope variesCoverage and returned fields vary by market. Ask us to confirm fit for your workflow.
Example record
Public bank details used for this interactive example. This preview does not query IPID or represent its coverage.
Talk to our team about your markets, routing requirements and integration needs.
Payments depend on both the intended recipient and the routing information being in place.
Do we have the routing information this payment needs?
Identify available bank, branch and routing information for supported markets before payment execution.
Can we verify the intended recipient?
Check whether the account belongs to the intended payee where validation coverage is available.
Explore Payee VerificationUse Bank Reference Data across bank and payment operations workflows, from directory maintenance to payment initiation.
Retrieve bank and branch information when capturing or reviewing payee details.
Check routing information before a transaction enters the payment network.
Keep internal bank directories and payment-routing tables organised across markets.
Give teams a consistent source of available bank information for routing workflows.
Understand the scope, access methods and relationship to Payee Verification before you discuss fit.
Bank reference data is information used to identify financial institutions, branches and the routing information needed to direct payments. Available fields depend on the market and the source data.
Bank Reference Data supports available international and domestic routing information across selected supported markets. Coverage and returned fields vary by market and data availability.
Bank Reference Data provides information used to route a payment, such as bank, branch and market details. Payee Verification checks whether an account belongs to the intended recipient. The capabilities address different sources of payment risk and can be used together.
Bank Reference Data can be accessed through individual API queries or a monthly export file, depending on how you want to integrate the information into your payment workflow.
Depending on the market and identifier, a lookup can return information such as the financial institution, branch, institution type, country, city, postcode and address details where available.
No. Bank Reference Data is provided as reference information sourced from public-domain sources for supported markets only. Coverage and returned fields may vary, and the information should not be treated as a guarantee of accuracy, completeness, payment success or routing outcome.
Give bank and payment operations teams access to available bank and routing information as they prepare payment flows.
Explore bank data