ISO 20022 Financial Messaging
Standards-compliant message processing for cross-border payments. Parse, generate, and validate pacs, pain, and camt messages via REST and GraphQL APIs — ready for SWIFT migration and SEPA.
8 Supported Message Types
Full coverage of the most critical ISO 20022 message types used in cross-border payments, direct debits, and account reporting. Every message type includes an XML parser, generator, and XSD validator.
Customer Credit Transfer
Initiate customer credit transfers from debtor to creditor institutions.
Direct Debit Initiation
Pull-based payment collection from debtor accounts with mandate references.
FI Credit Transfer
Interbank credit transfers between financial institutions with UETR tracking.
Payment Status Report
Status updates and rejection reasons for initiated payment instructions.
FI Direct Debit
Interbank direct debit settlement between financial institutions.
Payment Return
Return previously executed payments with structured return reason codes.
Bank Statement
End-of-day account statements with detailed entry and balance reporting.
Debit/Credit Notification
Intraday transaction notifications for real-time account monitoring.
Engine Capabilities
A production-grade message engine handling the full lifecycle from parsing raw XML to generating standards-compliant output with namespace detection and XSD validation.
Message Registry
Automatic namespace detection identifies message types from raw XML input. The registry maps each ISO 20022 namespace to its parser and validator, eliminating manual type selection.
- Automatic namespace-to-type mapping
- XSD schema validation with detailed error reporting
- Structured JSON output from any XML input
UETR Cross-Border Tracking
Every cross-border payment carries a Unique End-to-End Transaction Reference (UETR), enabling end-to-end payment tracking across correspondent banking chains.
- Auto-generated RFC 4122 UUIDs for UETR
- SWIFT gpi tracker compatible
- Status query by UETR reference
Business Application Header
Full BAH (AppHdr) support for wrapping ISO 20022 messages in SWIFT MX envelopes. Includes sender/receiver BIC, message name, and creation date with proper namespace handling.
- SWIFT MX envelope compatible
- BIC routing in header fields
- Duplex detection via message ID
XSD Validation Engine
Validate messages against official ISO 20022 XSD schemas before transmission. Catch structural errors, missing mandatory fields, and invalid code values at parse time.
- Official ISO XSD schema bundle
- Field-level error messages with XPath
- Strict and lenient modes
API Reference
REST and GraphQL APIs for the full ISO 20022 message lifecycle. All endpoints require Bearer token authentication.
REST Endpoints
GraphQL Operations
mutation {
iso20022Validate(
xml: "..."
type: "pacs.008"
) {
valid
errors { field message }
uetr
}
}Use Cases
From SWIFT migration projects to SEPA compliance and regulatory reporting — ISO 20022 is the common thread.
SWIFT Migration
Translate legacy MT messages to ISO 20022 MX format. Full co-existence support during the SWIFT migration period.
SEPA Messaging
Native pain.001/pain.008 for SEPA Credit Transfers and Direct Debits. Fully compliant with EPC rulebooks.
Cross-Border Tracking
Track payments hop-by-hop across correspondent banks using UETR references embedded in pacs.008 messages.
Regulatory Reporting
Generate camt.053 statements and camt.054 notifications for automated reconciliation and regulatory submission.
Ready for ISO 20022?
Parse your first message in under five minutes. Full API docs available in the developer portal.