One JSON API over the reference data a cross-border payment actually needs: beneficiary and routing validation, correspondent settlement instructions, sanctions screening, country payment rules, FX, and a landed-cost estimate. Built for fintechs, PSPs, EMIs and licensed FX brokers.
One call checks the beneficiary IBAN checksum against its country, cross-checks it against the beneficiary BIC, resolves which correspondents can settle the currency, screens every submitted name and institution against sanctions watchlists, and returns an arrival estimate. It runs before you send, not after a customer complains.
POST /api/v5/validate KEY: your-api-key { "beneficiary_bic": "DEUTDEFF", "beneficiary_iban": "DE89370400440532013000", "beneficiary_owner": "Muster Handels GmbH", "currency": "EUR", "amount": 15000.00 }
{
"beneficiary_bic": {
"status": "ok",
"details": "Deutsche Bank AG, Frankfurt am Main"
},
"beneficiary_iban": {
"status": "ok",
"details": "Checksum valid, country matches BIC"
},
"available_correspondents": [
{ "corresBIC": "DEUTDEFFXXX", "currency": "EUR" }
],
"sanctions_screening": {
"beneficiary_owner": { "status": "clear" }
},
"settlement_eta": { "business_days_p50": 1 }
}
A bad checksum, an IBAN whose country does not match the BIC, a currency the beneficiary bank has filed no settlement instructions for, or a name that hits a watchlist all come back as a field-level status with a recommendation attached. Response shapes and every field are in the API reference.
Plain JSON over HTTPS, authenticated with a single API key header. No membership, no message formats to implement, no file transfer to schedule.
| Punkt końcowy | What it answers |
|---|---|
| Pre-send checks | |
| POST /api/v5/validate | Is this payment going to arrive? IBAN checksum and country match, BIC resolution, routing availability, sanctions screening and an arrival estimate in one response. |
| POST /api/v5/cost | What does the beneficiary actually receive? The sending bank fee priced for the rail the route uses, plus what comes off the money in transit and the beneficiary bank incoming tariff. |
| POST /api/v5/eta | When does it land? A p50/p90/p95 arrival window computed from completed payments on the same corridor, with return and delay risk flags. |
| Correspondent and reference data | |
| POST /api/v5/getssi | Which correspondent settles this currency for this institution, with the account, the asset category, intermediary details and national clearing identifiers. |
| POST /api/v5/getssireverse | The reverse lookup: which institutions hold a settlement account with a given correspondent. |
| GET /api/v5/banks | Bank and BIC directory search, ranked by how many currencies each office has filed settlement instructions for, so the office that actually settles comes first. |
| GET /api/v5/country/{code}/profile | Country payment rules: IBAN structure and whether it is mandatory, local bank-code system, domestic RTGS and retail clearing, SEPA participation, FATF status, currency controls and documentation requirements. |
| Compliance | |
| POST /api/v5/sanctions/screen | Screen a person, company or institution. Every screen is fired at two independent index nodes concurrently and any positive prevails, because the nodes rebuild their indices hours apart and either one alone can miss a fresh listing. |
| POST /api/v5/sanctions/screen/bulk | Screen a list of names in one call. Larger jobs go to the asynchronous batch endpoints and are metered by name count. |
| GET /api/v5/sanctions/lists | The watchlists in force right now, so your risk policy can include or exclude named lists per call instead of accepting one fixed set. |
| POST /api/v4/sanctions/monitor | Keep screening an onboarded customer after onboarding. You are told when their status changes rather than when you next remember to re-run the check. |
| GET /api/v5/sanctions/cases | The hit-case queue: assign, adjudicate and dispose of matches with an append-only audit trail your regulator can read. |
| GET /api/v5/sanctions/report/{id} | A retrievable compliance report for a completed screen, as JSON or as a PDF certificate. |
| Treasury and delivery | |
| GET /api/v4/fx/rates | Reference rate for a pair on a given date, with history and the list of covered pairs alongside it. |
| POST /api/v4/webhooks | Signed event delivery to your endpoint, with a delivery log, synthetic test events and secret rotation on a 24 hour dual-secret overlap. |
The same tools are exposed to AI agents over our MCP server, so a treasury or operations assistant can call them directly without you writing a wrapper.
Correspondent settlement instructions are read per institution and per currency at call time. Where an institution has filed nothing for a currency, you get that answer rather than a plausible-looking default.
Cost estimates price each leg against the rail the route actually uses, because a bank publishes several schedules and quoting the wrong one is how a 0.80 EUR transfer gets quoted at 150.00. Where we hold no published price for that rail we say so instead of filling in a number.
A beneficiary bank often charges a company differently from a private individual on the same incoming payment. Both segments are inputs, so the amount you show your customer is the amount that lands.
Two independent screening nodes are read on every call and the more severe verdict wins. Matches carry an adjudication verdict and a false-positive assessment, not just a similarity score, so your analysts see why a hit was raised.
A business email is enough. No membership and no correspondent relationship is required to read the data.
Run validations, bank lookups, settlement instructions and screens on the web before you write any code, so you can see the shape of the answers first.
Take a key and call the same endpoints from your back office, your onboarding flow or your mobile app. Or point an agent at the MCP server.
Validate beneficiary details at the point of capture and quote a landed amount your customer can rely on, so fewer payments are repaired after the fact.
Screen counterparties on an ongoing basis and adjudicate hits in an auditable queue, with country rules and correspondent data behind the same key.
Check the receiving side before the conversion: routing availability for the currency, the incoming tariff at the beneficiary bank, and a realistic arrival window.
Get correspondent, country and compliance reference data from day one, while your own banking relationships are still being built.
Read the full reference, or start a trial and call the validation endpoint against a payment you are about to send.
Volume-based pricing from $100/month