#fintech

US bank ABA routing-number (routing transit number) validation as an API, computed locally and deterministically. The validate endpoint checks a nine-digit routing number with the official ABA checksum — 3·(d1+d4+d7) + 7·(d2+d5+d8) + (d3+d6+d9) must be a multiple of ten — ignoring hyphens and spaces, and reads the first two digits as the Federal Reserve routing symbol to name the district (01–12 are the twelve Federal Reserve Banks from Boston to San Francisco, 21–32 are thrift institutions); JPMorgan Chase’s 021000021 validates and resolves to the Federal Reserve Bank of New York, and a number with a wrong check digit is rejected. The checkdigit endpoint computes the ninth check digit from the first eight so the whole number passes. It also returns the institution identifier (digits 5–8) and the check digit. Everything is computed locally and deterministically, so it is instant and private. Ideal for fintech, banking, ACH, payroll, payment and accounting app developers, bank-account-form validation and onboarding tools, and US payment software. This is the checksum and routing-symbol structure only — it does not confirm a live bank. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 2 endpoints. For SWIFT/BIC codes use a BIC API and for IBANs an IBAN API.

api.oanor.com/routingnumber-api

SWIFT/BIC business-identifier-code validation and parsing as an API, computed locally and deterministically. The validate endpoint checks that a code follows the ISO 9362 BIC structure — four letters for the institution, a two-letter ISO country code, a two-character location code and an optional three-character branch code, eight or eleven characters in total — ignoring spaces and upper-casing the input, and confirms the country code is a recognised one; DEUTDEFF (Deutsche Bank, Frankfurt) is a valid eight-character head-office BIC and DEUTDEFF500 a valid eleven-character branch BIC. The parse endpoint breaks a BIC into its institution, country, location and branch components, reports whether it is a head office or a branch (branch XXX or none means the head office), and reads the status from the location code’s second character — 0 for a test/non-SWIFT code, 1 for a passive participant and 2 for reverse billing. A BIC carries no checksum, so this is structural validation. Everything is computed locally and deterministically, so it is instant and private. Ideal for fintech, banking, payment, KYC, treasury and accounting app developers, SWIFT-code and bank-identifier tools, and onboarding flows. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 2 endpoints. This validates and parses a BIC; for IBAN account-number validation use an IBAN API.

api.oanor.com/bic-api

ISO 18245 Merchant Category Codes (MCC) as an API — the 981 four-digit codes that Visa, Mastercard and other card networks use to classify a merchant's line of business. Look up any code (e.g. 5812 → Eating places and Restaurants, 5411 → Grocery Stores/Supermarkets, 3000 → United Airlines), search by description (e.g. "hotel", "airline", "pharmacy"), filter by IRS-reportable status, or list them all. Each record carries the network/edited description, USDA and IRS descriptions and whether the category is IRS 1099-reportable. Ideal for payments, fintech, expense management, fraud analysis and transaction enrichment.

api.oanor.com/mcc-api

A fast, fully-local payment-card toolkit: validate card numbers with the Luhn (mod-10) checksum, detect the brand by IIN/prefix (Visa, Mastercard including the 2-series, American Express, Discover, Diners, JCB, UnionPay, Maestro), format and mask numbers with brand-correct grouping, list supported brands with their valid lengths and CVV length, and generate synthetic Luhn-valid TEST card numbers for QA. Pure server-side compute, no third-party upstream, and inputs are never logged. It is algorithmic only (no real issuer/bank BIN-database lookup). Ideal for checkout forms, payment flows, fraud pre-checks and test fixtures.

api.oanor.com/creditcard-api

Validate IBANs with the ISO 7064 mod-97 checksum and per-country length and structure checks, and resolve the BIC and bank details for supported countries. A local parse endpoint works for every IBAN country offline; the validate endpoint adds bank-code verification and BIC. Ideal for payments, billing, onboarding and KYC.

api.oanor.com/iban-api