
SEPA XML Generator (pain.001 & pain.008) & IBAN Validator
Generate SEPA pain.001 and pain.008 XML with IBAN checks from CSV, Excel or JSON
Answered our latest tool-list check 23 hours ago with 6 tools. It will be marked verified after 3 successful checks in 7 days.
- Pricing
- Paid
- Platforms
- API, Web
- Runs
- Remotely
- Version
- 1.2.0
- Listing updated
- 5 days ago
Similar MCP servers
About SEPA XML Generator (pain.001 & pain.008) & IBAN Validator
SEPA XML Generator (pain.001 & pain.008) & IBAN Validator is a paid MCP server for finance and payments. It runs as a hosted remote server, so there is nothing to install locally.
Bulk European payments need XML files that banks accept in full or reject whole, and this server produces them deterministically instead of asking a language model to. It converts CSV, Excel or JSON into SEPA Credit Transfer (pain.001.001.09) and Direct Debit (pain.008.001.08) XML with structured postal addresses, and can also write the classic pain.001.001.03 and pain.008.001.02 versions.
Checks include MOD-97 IBAN verification, an exact integer-cent control sum and automatic sanitising of German and French diacritics. It runs as an Apify Actor (finops_studio/sepa-xml-generator) reached through Apify's hosted MCP endpoint, a REST call for n8n or Make workflows, or a browser preview. The README prices it pay-per-use at $0.02 per transaction with no monthly subscription.
It is one of a family of FinOps Studio engines covering EU e-invoice XML, US NACHA ACH, BAI2 statement parsing, DATEV, Australian ABA, pain.002 rejection decoding, UK BACS and others, each a separate Actor.
Install
Run in a terminal
claude mcp add --transport http sepa-xml-pain001-iban-mcp https://finops-rapidapi-edge.ria-rader.workers.dev/public-mcpAdd to Settings → Connectors → Add custom connector
https://finops-rapidapi-edge.ria-rader.workers.dev/public-mcpAdd to ~/.cursor/mcp.json
{
"mcpServers": {
"sepa-xml-pain001-iban-mcp": {
"url": "https://finops-rapidapi-edge.ria-rader.workers.dev/public-mcp"
}
}
}Add to .vscode/mcp.json
{
"servers": {
"sepa-xml-pain001-iban-mcp": {
"type": "http",
"url": "https://finops-rapidapi-edge.ria-rader.workers.dev/public-mcp"
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"sepa-xml-pain001-iban-mcp": {
"serverUrl": "https://finops-rapidapi-edge.ria-rader.workers.dev/public-mcp"
}
}
}Add to Grok Bot desktop app → Connect apps → Add a custom connector
https://finops-rapidapi-edge.ria-rader.workers.dev/public-mcpEnter a Name (for example "SEPA XML Generator (pain.001 & pain.008) & IBAN Validator"), choose Type: Remote HTTPS, paste this as the Server URL and choose Add plugin.
Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"sepa-xml-pain001-iban-mcp": {
"type": "http",
"url": "https://finops-rapidapi-edge.ria-rader.workers.dev/public-mcp"
}
}
}Using several servers? Build one config file with the MCP config generator.
Tools this server provides (6)
Read directly from the server.
- validate_global_bank_identifiers
- Deterministically validate IBAN (ISO 13616 MOD-97), SWIFT BIC, US ABA routing (MOD-10), UK Sort Code + Account Number, Australian BSB, Canadian CPA-005 routing, and EU VAT IDs.
- preview_sepa_xml_2_rows
- Free 2-row taste-test preview of 2026 EPC structured-address ISO 20022 SEPA Credit Transfer (pain.001.001.09) & Direct Debit (pain.008.001.08) XML generation.
- preview_us_nacha_ach_2_rows
- Free 2-row taste-test preview of 94-character Block-10 padded US NACHA ACH (.ach) files with ABA MOD-10 verification.
- preview_eu_einvoice_xml_2_lines
- Free 2-line taste-test preview of EN 16931 Peppol BIS 3.0 UBL, German XRechnung 3.0, or Factur-X CII XML invoice generation.
- preview_datev_extf_csv_2_rows
- Free 2-row taste-test preview of German DATEV Buchungsstapel EXTF v700 CSV generation (SKR03 / SKR04).
- preview_bai2_statement_2_tx
- Free 2-transaction taste-test preview of Corporate BAI2 bank statement parsing (records 01..99) into signed JSON & CSV.
What it does
- SEPA credit transfers
- Writes pain.001.001.09 files, plus the older pain.001.001.03.
- SEPA direct debits
- Writes pain.008.001.08 files, plus pain.008.001.02.
- IBAN validation
- Checks IBANs with the MOD-97 checksum.
- Exact control sums
- Totals amounts in integer cents so the control sum matches.
- Diacritic cleanup
- Sanitises German and French accented characters automatically.
- Flexible input
- Accepts CSV, Excel or JSON, including semicolon CSV.
Good for
- Turn a spreadsheet of supplier payouts into a bank-ready SEPA file
- Create direct-debit batches from ERP rows
- Validate IBANs before submitting a payment run
- Automate payment file generation in n8n or Make
Pricing
Paid
Pay-per-use on Apify: $0.02 per transaction; no monthly subscription
Prices change. Check geornaden.github.io before you buy.
SEPA XML Generator (pain.001 & pain.008) & IBAN Validator FAQ
Which schema versions does it output?
The 2026 structured-address pain.001.001.09 and pain.008.001.08, plus classic pain.001.001.03 and pain.008.001.02.
How is it priced?
The README lists $0.02 per transaction, pay-per-use, with no monthly subscription.
Does it use an LLM?
No. It describes itself as a deterministic engine with exact integer-cent maths.
How can I call it?
Through Apify's hosted MCP endpoint, the Apify REST API, n8n or Make workflows, or a browser preview.
Is SEPA XML Generator (pain.001 & pain.008) & IBAN Validator free?
No. SEPA XML Generator (pain.001 & pain.008) & IBAN Validator is a paid product.
How do I add SEPA XML Generator (pain.001 & pain.008) & IBAN Validator to Claude Code?
Run this command in your terminal: claude mcp add --transport http sepa-xml-pain001-iban-mcp https://finops-rapidapi-edge.ria-rader.workers.dev/public-mcp
What are the best alternatives to SEPA XML Generator (pain.001 & pain.008) & IBAN Validator?
The closest alternatives to SEPA XML Generator (pain.001 & pain.008) & IBAN Validator are FinOps Studio — Banking, Payroll & E-Invoicing, SepaCheck Validator, FinOps Studio Zero-Auth Bank Validator & 2-Row Taste-Test MCP, ISO 20022 pain.002 Bank Rejection & Status XML Decoder and Fast Data Actors (via Apify MCP).
Where this comes from
- Description: written from the project's README and the project's website.
- Status and tools: checked automatically by AIPoweredBot on 18 November 2026.
- Install steps: from the official MCP Registry entry.