Check country format, length and check digits before storing customer payment details.
SEPA IBAN validation API
Validate IBANs and check SEPA bank participation
Check an IBAN and the bank’s participation in SEPA Credit Transfer, Instant Credit Transfer, Direct Debit Core and B2B. Get a separate result for each scheme in one JSON response, using bank data and EPC participant registers.
Start with 10 free API requests every 24 hours.
Is the IBAN valid — and does the bank support your SEPA scheme?
These are separate checks. An IBAN can pass its format and checksum checks while the bank’s participation in a particular payment scheme remains unconfirmed. Check both when collecting payment details or preparing a payment run.
Use available bank-directory data to resolve the bank and BIC. Directory checks are available for 40 countries.
Read the individual result for your credit transfer, instant payment or direct debit workflow.
Four SEPA schemes, four independent results
Credit Transfer
details.sepa.sct
Reports the bank’s participation in the standard SEPA credit transfer scheme.
Instant Credit Transfer
details.sepa.sctInst
Reports participation in the instant credit transfer scheme. It is not a live RT1/TIPS reachability check or a guarantee of instant execution.
Direct Debit Core
details.sepa.sddCore
Reports participation in the SEPA Direct Debit Core scheme.
Direct Debit B2B
details.sepa.sddB2b
Reports participation in the Business-to-Business scheme. Do not infer this result from the Core result.
Participant data comes from the European Payments Council’s separate scheme registers. A confirmed result requires an unambiguous bank mapping and a current participant match in fresh register data.
SEPA API request and JSON response
Use the IBAN validation endpoint with your API key. The SEPA results are included when bank details are returned; no separate scheme-check request is needed.
curl --get "https://www.iban-test.eu/api/v2/iban/validate" \
--header "Authorization: Bearer YOUR_API_TOKEN" \
--data-urlencode "iban=DE89370400440532013000"Example response excerpt showing only the SEPA fields. Actual results depend on the IBAN and available register data.
{
"details": {
"sepa": {
"sct": {
"status": "confirmed",
"reason": "matched"
},
"sctInst": {
"status": "confirmed",
"reason": "matched"
},
"sddCore": {
"status": "confirmed",
"reason": "matched"
},
"sddB2b": {
"status": "confirmed",
"reason": "matched"
}
}
}
}Read the complete SEPA field and reason reference.
For a step-by-step example, follow the guide to checking SEPA bank participation. It includes a Python response interpreter, an illustrative JSON file and instructions for reading each scheme’s status and reason.
Handle confirmed and unknown results correctly
Handle invalid IBAN input first. SEPA participation is additional information and does not change the IBAN validation result.
confirmed with reason matched confirms bank participation in that scheme. Each scheme must be evaluated separately.
unknown means participation could not be confirmed. Check the reason and use a review or fallback step instead of automatically marking the bank unsupported.
For example, missing_bic means the bank BIC was unavailable, no_match means no matching participant was found, and stale_data means the register data is outdated.
This is a validation and bank-participation API. It does not initiate payments, verify account ownership or existence, confirm a direct debit mandate, or guarantee settlement. Account eligibility and live payment routing must be handled by your payment provider.
Add SEPA checks to your payment workflow
Use these results in customer onboarding, direct debit setup and payment preparation. Start with a free API key, inspect a response and handle the required scheme in your application.
For general format, checksum and bank-directory validation, see the IBAN validation API.