ISO 20022 Financial Message Engine API
High-performance edge parser converting pacs.008, camt.053, and pain.001 XML to clean JSON
The ISO 20022 Financial Message Engine API transforms complex banking XML messages into strongly-typed, developer-friendly JSON in milliseconds. Built specifically for fintechs, treasury platforms, payment rails, crypto off-ramps, and core banking modernization.
As SWIFT, Fedwire, CHIPS, and TARGET2 sunset legacy MT formats in favor of ISO 20022 MX standards, financial engineering teams face massive XML parsing overhead. This API runs entirely at the Cloudflare edge: linear O(N) stream tokenization autodetects message types (pacs.008, camt.053, pain.001), validates UETRs, IBANs, and BICs, and delivers structured JSON in sub-15ms latency.
Pure compute with zero external subrequests: your sensitive transaction and account payloads are processed instantaneously in memory without storage or third-party leakage, ensuring strict data security and zero cold-start latency.
Features
- Full support for pacs.008 (Financial Institutional Customer Credit Transfers & UETR)
- Full support for camt.053 (Bank-to-Customer Account Statements & Balances)
- Full support for pain.001 (Customer Credit Transfer Payment Initiation)
- Automatic namespace and root element auto-detection
- Structured party, agent, IBAN, BIC, and remittance reference normalization
- Sub-15ms edge execution across 300+ global locations
- Pure compute: zero external network calls, deterministic and ReDoS-safe
Endpoints
| Method | Path | Description | Example |
|---|---|---|---|
POST | /api/v1/parse | Auto-detect and parse any ISO 20022 XML message into structured JSON | /api/v1/parse |
POST | /api/v1/pacs008 | Strictly parse and validate pacs.008 customer credit transfer messages | /api/v1/pacs008 |
POST | /api/v1/camt053 | Strictly parse and validate camt.053 bank statement messages | /api/v1/camt053 |
POST | /api/v1/pain001 | Strictly parse and validate pain.001 customer credit transfer initiations | /api/v1/pain001 |
POST | /api/v1/validate | Validate ISO 20022 XML syntax, schema conformance, and business rules | /api/v1/validate |
GET | /health | Service health and supported message definitions | /health |
FAQ
Which ISO 20022 message types are supported?
The parser natively extracts complete structured data for pacs.008 (Customer Credit Transfer), camt.053 (Bank Statement), and pain.001 (Payment Initiation). Any other valid ISO 20022 XML document is safely parsed into a normalized generic JSON object.
How are XML namespaces handled?
The engine automatically detects ISO 20022 schema version identifiers in urn namespaces (e.g. urn:iso:std:iso:20022:tech:xsd:pacs.008.001.08) and resolves custom XML element prefixes transparently.
Does the parser retain or store any financial or banking data?
No. Processing is completely stateless pure compute. Payloads are parsed in-memory at the Cloudflare edge worker and streamed back immediately. Zero data is persisted to disk, databases, or logs.
What is the maximum payload size supported?
The API supports XML payloads up to 512KB per request, which comfortably fits large multi-transaction pacs.008 batches and extensive multi-entry camt.053 statements.