Interbank payments
- Test correspondent routes and cover payments
- Verify intermediary charge handling
- Simulate return (R) messages and reversals
- Toggle account formats and currencies per locale when rehearsing correspondent banking flows
ISO 20022
Standardize cross-border testing
with ISO 20022 messages
Generate pacs.008 and pacs.002-style messages so payment hubs, correspondent banks, and analytics teams can exercise the same data set during migrations to ISO 20022.
Compliance disclaimer
Message formats vary by market infrastructures and bank-specific rules. Treat these samples as testing aids—not production-ready instructions or regulatory guarantees.
Where ISO 20022 samples help
Safely rehearse pacs.* flows for international payments, domestic instant rails, and compliance monitoring without exposing sensitive production messages. Locale-aware defaults deliver yen or USD-based payloads so domestic and US teams can reuse the same scenarios.
Payment hub integration
- Reproduce RTGS/ACH common formats
- Check BIC mapping and proxy identifiers
- Validate real-time status updates and notifications
Compliance monitoring
- Exercise sanctions and AML attribute checks
- Confirm charge bearer logic across regions
- Practice UETR-based tracking for SWIFT gpi
Representative fields
The pacs.008-based samples include the following fields to cover end-to-end payment flows.
| Field | Description | Reference |
|---|---|---|
| message_id | Message identifier (unique per payment) | ISO 20022 Business Application Header |
| uetr | Unique end-to-end transaction reference (UUID) | SWIFT gpi |
| instruction_priority | Priority code (NORM / HIGH) | ISO 20022 InstructionForNextAgent |
| instructed_amount | Amount and currency (ISO 4217) | ISO 20022 AmountType |
| debtor_agent_bic | Debtor agent BIC | ISO 9362 |
| charge_bearer | Charge bearer (DEBT, CRED, SHAR, SLEV) | ISO 20022 ChargesInformation |
When migrating from MT to ISO 20022, validate any conversion tool output (additional headers, proprietary fields) by extending the schema accordingly.
Testing playbook
1
Select message types
Decide which pacs, camt, or pain messages you need and list the mandatory attributes.
2
Validate profiles
Run samples through ISO 20022 validators or market infrastructure profiles (e.g., CBPR+).
3
Execute scenarios
Simulate success, rejects, returns, and cancellation flows to verify routing and notifications.
4
Archive & audit
Store message history, charge information, and FX rates as audit evidence for regulators.
Frequently asked questions
Do you provide response messages such as pacs.002?
Yes—success, reject, and pending statuses are generated and can be customized with reason codes.
How large are the files?
Each message is roughly 5 KB. For batch testing we can bundle multiple messages into a ZIP archive.
Can we test encryption or signing?
Payloads are plain for testing, but you can inject dummy certificate metadata. Apply TLS and key management in your integration environment.
Accelerate ISO 20022 payment testing
Generate realistic pacs messages in minutes to validate formatting, routing, and compliance checks across your payment landscape.