Validate IBANs, generate IBANs, validate bank accounts, validate BICs and check API usage.
The IBAN-Test MCP server provides structured tools for AI clients and agents:
validate_iban – Validates one IBAN, including SEPA bank participation.validate_iban_batch – Validates multiple IBANs; each IBAN counts as one API request.generate_test_iban – Generates an IBAN from country, bank code and account number.ibantest_bank_account_validate – Checks a German bank code and account number.ibantest_bic_validate – Validates a BIC.get_usage_info – Shows API usage without consuming a validation request.
This lets an AI workflow validate payment data without implementing bank data logic itself.
SEPA Direct Debit: Core and B2B
IBAN validation also returns the bank’s participation in SEPA Direct Debit schemes, checked against the EPC participant registers.
sddCore – SEPA Direct Debit Core; sddB2b – SEPA Direct Debit B2B.
Both schemes are checked independently. confirmed means there is an unambiguous, current register match. unknown means participation could not be confirmed; it does not mean the bank does not support the scheme.
This checks bank participation. It does not confirm account existence or direct debit eligibility, a mandate, or the success of a collection.
SEPA fields and response examples
