Financial Messaging and
Payment Standards Catalog

As financial messaging and payment standards continue to grow in volume and complexity, our comprehensive library of pre-built mappings and processes simplifies your work – helping you stay ahead of changes and ensure seamless compliance.

Support for Swift MT and MX messages such as:

SWIFT MT examples

• MT103 – Customer Credit Transfer (most common for cross-border payments)
• MT202 – Bank-to-Bank Transfer (settlement between FIs)
• MT202 COV – Cover Payment for MT103, carrying sender/receiver bank details
• MT101 – Request for Transfer (used by corporates to instruct banks)
• MT940 / MT942 – Account Statement / Interim Transaction Report
• MT799 / MT760 – Free-format Message / Bank Guarantee or Letter of Credit

SWIFT MX (Message Exchange) - ISO 20022 XML-based format examples

• pacs.008 – FI to FI Customer Credit Transfer (replacement for MT103)
• pacs.009 – FI to FI Financial Institution Transfer (replacement for MT202)
• pacs.002 – Payment Status Report (acknowledgment or rejection)
• camt.053 – Bank Account Statement (replacement for MT940)
• camt.052 / camt.054 – Intraday Statement / Credit or Debit Notification
• pain.001 – Customer Credit Transfer Initiation (corporate to bank)
• pain.002 – Payment Status Report (customer-focused)
• camt.029 – Resolution of Investigation (like a query/response on a payment)

Please note: This is just a sampling of messages we support. Contact us for more information. Back to overview

SEEBURGER supports MT and MX (ISO 20022) messages for:

• US (CHIPS), US (Fed)
• CA (LYNX)
• EU (EURO1), for example:
• EU (Target2)

Mapping and Transformation

• ISO 20022 validation and transformation
• CBPR+ mapping library (MT<>MX)
• Target 2 mapping library (MT<>MX)
• Fedwire FAIM mapping library (FAIM<>MX)
• CHIPS (CHIPS<>MX)

Please note: This is just a sampling of messages we support. Contact us for more information. Back to overview

Examples for Euro1, EU messages

• camt.003.001.07 – To request information on one or more accounts at transaction admin
• camt.004.001.08 – Provide information on the details of one or more accounts held at transaction admin
• camt.005.001.08 – To request information about payment instructions held at transaction admin
• camt.006.001.08 – To provide information on transactions and booked entries held at transaction admin
• pacs.002.001.10 – Reports the status of the payment initiation
• pacs.004.001.09 – The Payment Return message is sent by an agent to the previous agent in the payment chain to undo a payment previously settled

Examples for TARGET2, EU messages

• camt.003.001.07 – To request information on the details of one or more accounts held at the transaction administrator, including information on the balances
• camt.004.001.08 – To provide information on the details of one or more accounts held at the transaction administrator, including information on the balances
• camt.005.001.08 – To request information about payment instructions held at the transaction administrator
• pacs.002.001.10 – Reports the status of the payment initiation
• MT1012 – Sender notification
• MT103 – Allows the exchange of single customer credit transfers

Examples for Swift MT, Global messages

• MT101 – Is a request for transfer, enabling the electronic transfer of funds from one account to another
• MT102 – Conveys multiple payment instructions between financial institutions

Examples for Swift MX, Global messages

• camt.026 – This message is used to initiate an investigation of a payment instruction that cannot be executed or reconciled
• camt.027 – This message is used to initiate an investigation for missing funds at the creditor or at an agent along the processing chain
• pacs.003 – Interbank format with which a direct debit is transmitted from the sender (creditor) bank to the recipient (debitor) bank
• pain.001 – Customer Credit Transfer Initiation for cross border and domestic payments

Please note: This is just a sampling of messages we support. Contact us for more information. Back to overview