Validate International Bank Account Numbers (IBANs) via a pay-per-call MPP endpoint.
What it does
This endpoint validates International Bank Account Numbers (IBANs) through the Locus MPP (Micropayment Protocol) gateway. It accepts a POST request with a JSON body containing an IBAN string and returns validation results. The service is powered by Abstract API's IBAN validation backend.
Payment is handled via the MPP protocol using the Tempo method (pathUSD on Tempo L2). Each call costs 6000 base units of pathUSD (6 decimals), which equates to $0.006 per request. The endpoint uses a "charge" intent, meaning each request is a one-shot payment.
The endpoint is routed exclusively to POST requests. HEAD and GET probes return 404, which is expected behavior for a POST-only route. The OpenAPI schema specifies a single required field ("iban") in the request body. Documentation references point to Abstract API's IBAN validation docs and a Locus-hosted markdown file for LLM consumption.
Capabilities
Use cases
- —Validating customer-provided IBANs before initiating wire transfers
- —Checking IBAN format and checksum in onboarding flows
- —Automated compliance checks on international payment details
- —Agent-driven bank account verification without API key management
Fit
Best for
- —AI agents needing on-demand IBAN validation without subscription
- —Applications requiring pay-per-use banking data verification
- —Developers who want crypto-settled micropayments for financial data lookups
Not for
- —Bulk batch validation of millions of IBANs (per-call pricing adds up)
- —Use cases requiring full bank details beyond IBAN validity (e.g., balance checks)
- —Environments that cannot settle payments via Tempo L2 / pathUSD
Quick start
curl -X POST https://abstract-iban-validation.mpp.paywithlocus.com/abstract-iban-validation/validate \
-H "Content-Type: application/json" \
-d '{"iban": "DE89370400440532013000"}'Example
Request
{
"iban": "DE89370400440532013000"
}Endpoint
Quality
OpenAPI schema is present with clear request structure and payment info, but no example response was captured, the endpoint returned 404 on HEAD/GET (expected for POST-only but no 402 challenge was directly observed), and crawled pages yielded no additional documentation.
Warnings
- —No 402 challenge was captured via HEAD/GET probes; endpoint is POST-only so liveness could not be confirmed without an actual POST request
- —No example response schema or sample available — response structure is unknown
- —All crawled pages returned 'not found' JSON; documentation is only available at external URLs
Citations
- —The endpoint validates IBANs and is part of Abstract API's IBAN validation servicehttps://www.abstractapi.com/api/iban-validation-api
- —API reference documentation is available at Abstract API docshttps://docs.abstractapi.com/iban-validation
- —LLM-oriented documentation is hosted at Locushttps://beta.paywithlocus.com/mpp/abstract-iban-validation.md