Use case · VerifyDesk
Validate an IBAN via API before a payment goes out
Catch mistyped IBANs before money moves: length, national account format and mod-97 checksum per the SWIFT IBAN Registry (89 countries), plus an optional BIC check. Runs offline.
The job
Most payment failures caused by bank details are typing errors: a digit swapped, one dropped, a space pasted in the wrong place. The IBAN format carries its own protection against that: a two-digit checksum computed with ISO 7064 mod-97, a fixed length per country, and a national account format (BBAN) that the SWIFT IBAN Registry defines for each country.
Checking both before a payment file is built catches the error while the person who supplied the IBAN is still reachable, rather than days later as a returned transfer.
Why an agent needs a tool for it
An agent reading IBANs out of emails, PDFs and supplier forms will occasionally misread one. validate_iban is a cheap guard to run on every IBAN it extracts, and when it fails it says why in a sentence the agent can pass back to the supplier.
The check runs on our server without calling a bank or a third party, so the IBAN is not shared further than the call itself.
The calls
3 tool calls.
{
"name": "validate_iban",
"arguments": {
"iban": "DE89 3704 0044 0532 0130 00"
}
}{
"valid": true,
"iban": "DE89370400440532013000",
"country": "DE",
"bank_code": "37040044"
}Spaces are accepted on the way in and removed on the way out, so the normalized form is ready for a payment file. The bank code comes from the positions the registry defines for that country.
{
"name": "validate_iban",
"arguments": {
"iban": "DE89 3704 0044 0532 0130 01"
}
}{
"valid": false,
"iban": "DE89370400440532013001",
"country": "DE",
"reason_code": "checksum_failed",
"reason": "Checksum failed (mod-97): digits are mistyped or corrupted."
}One digit changed at the end. The checksum catches it; reason_code is stable for code, reason is written for whoever has to fix it.
{
"name": "validate_iban",
"arguments": {
"iban": "GB82 WEST 1234 5698 7654 32",
"bic": "NWBKGB2L"
}
}{
"valid": true,
"iban": "GB82WEST12345698765432",
"country": "GB",
"bank_code": "WEST",
"branch_code": "123456",
"bic": {
"bic": "NWBKGB2L",
"valid": true,
"institution": "NWBK",
"country": "GB",
"location": "2L"
}
}With the optional BIC: its format and country are checked, and a BIC country that differs from the IBAN country comes back as a warning rather than an error.
Limits worth knowing
- This checks structure, not existence. A well-formed IBAN for a closed account, or for somebody else's account, passes. Likewise, a well-formed BIC is not proof that SWIFT issued it.
- It does not confirm that the IBAN belongs to the named payee. That needs a payee verification service at the bank level, which this is not.
Pricing
0.6 credits for the calls on this page.
| Tool | Credits per call |
|---|---|
| validate_iban | 0.2 |
Credits are prepaid and shared across every server. Starter is $10 for 1,000 credits, packs never expire, and 100 credits are free without a card. Full pricing.
Install
Connect VerifyDesk to your agent.
A remote MCP server over Streamable HTTP. Get a free key, swap it in, and the calls above work as written, with answers reflecting the data on the day you call.
https://verifydesk.agenttoolworks.com/mcp
claude mcp add --transport http verifydesk \ https://verifydesk.agenttoolworks.com/mcp \ --header "Authorization: Bearer atw_live_your_key"
Setup for Claude Desktop, Cursor and Windsurf is in the docs.
Read next
- VerifyDesk: every tool, the data sources and measured reliability.
- Verifying a company from an AI agent, the long-form guide.
- Verify an EU VAT number via API, from an agent
- Screen a company or person against sanctions lists from an agent
- Look up a French company by SIREN or name, via API
- Supplier onboarding checks an agent can run on its own
- All use cases
Public data only, from the sources named on the product page. Not affiliated with any registry, list publisher, job board provider or store platform named here.