Free online SWIFT message validator

Validate SWIFT MT & MX messages online

Check payment instructions, statuses, returns, notifications and account reports before deeper network or scheme validation.

  • Eight detailed SWIFT MT profiles
  • Eight detailed pain, pacs and camt profiles
  • BIC, IBAN and postal-address checks

3 free message actions every day - no account or card required

Supported SWIFT MT validation profiles

Detailed checks cover MT101, MT103, MT202 and MT202 COV, MT900, MT910, MT940, MT942 and MT950. Checks include the FIN envelope, required tags, references, dates, currencies, amounts, BIC format, IBAN checksum and applicable party data.

Supported ISO 20022 validation profiles

Detailed XML checks cover pain.001, pacs.002, pacs.004, pacs.008, pacs.009, camt.052, camt.053 and camt.054. FinMessage checks the namespace, business root, required elements, amounts, currencies, BICs, IBANs and postal addresses where applicable.

Message-specific structure checks

Business flowProfilesKey structures
Initiation and transferMT101, MT103, MT202/COV, pain.001, pacs.008, pacs.009Parties, accounts, agents, IDs and amounts
Status and returnpacs.002, pacs.004Original references, status or return data
ReportingMT900/910/940/942/950, camt.052/053/054Accounts, balances, entries and indicators

How to validate a message

  1. Paste the complete MT or MX message, or upload a text-based file.
  2. Select Validate message.
  3. Fix blocking errors and review warnings against the destination profile.
  4. Use the authoritative schema and network validation process before submission.
Structural review, not certification. No-error results do not prove acceptance by SWIFT, CBPR+, a clearing system or a receiving bank.

Common parsing and validation problems

  • Only a partial MT was pasted: include the FIN blocks and the {2:I103...} or {2:O103...} application header. Try the MT103 format checker.
  • XML is not well formed: close tags and escape special characters; then retry.
  • MX namespace is different from the expected version: use the pacs.008.001.08 structure checker for that specific version.
  • Required field is missing: inspect the error's field or XML element and compare with the MT103 field reference.

The validator runs built-in structural checks, not complete XSD or CBPR+ compliance validation. Some parse failures can come from unsupported envelopes or message fragments.

Privacy

Successful message actions are saved to history. Review or delete saved entries in the workspace. Use authorized data and prefer redacted samples.