Message Validation: SWIFT MT and ISO 20022

Validate SWIFT MT and ISO 20022 messages against schemas and business rules with the open source Reframe validation engine.

Overview

Reframe’s open source rules engine validates messages at multiple levels:

1. Format Validation: Message structure and syntax
2. Schema Validation: Field formats and required elements
3. Business Validation: Package-specific business rules
4. Custom Rules: User-defined validation rules via JSONLogic

API Usage

Basic Validation

curl -X POST http://localhost:3000/api/validate \
  -H "Content-Type: application/json" \
  -d '{
    "message": "{1:F01BNPAFRPPXXX...}",
    "business_validation": true
  }'

Response (Valid Message)

{
  "status": "valid",
  "message_type": "MT103",
  "format": "swift_mt",
  "validation": {
    "format": "passed",
    "schema": "passed",
    "business": "passed"
  },
  "timing_ms": 0.5
}

Response (Invalid Message)

{
  "status": "invalid",
  "message_type": "MT103",
  "format": "swift_mt",
  "validation": {
    "format": "passed",
    "schema": "failed",
    "business": "skipped"
  },
  "errors": [
    {
      "code": "FIELD_REQUIRED",
      "field": "32A",
      "message": "Tag 32A (Value Date/Currency/Amount) is required"
    },
    {
      "code": "INVALID_FORMAT",
      "field": "50K",
      "message": "Account number must start with /"
    }
  ]
}

Validation Options

Full Options Example

curl -X POST http://localhost:3000/api/validate \
  -H "Content-Type: application/json" \
  -d '{
    "message": "...",
    "business_validation": true,
    "canonical_json": true,
    "fail_fast": false
  }'

Format Detection

Reframe automatically detects the message format:

SWIFT MT Validation

Block Structure

• Block 1: Basic header format
• Block 2: Application header format
• Block 3: User header (optional)
• Block 4: Text block with tags
• Block 5: Trailer (optional)

Tag Validation

Example Errors

{
  "errors": [
    {
      "code": "BLOCK_STRUCTURE",
      "message": "Block 1 is malformed"
    },
    {
      "code": "MISSING_TAG",
      "field": "32A",
      "message": "Required tag 32A is missing"
    },
    {
      "code": "INVALID_BIC",
      "field": "52A",
      "message": "Invalid BIC format in tag 52A"
    }
  ]
}

ISO 20022 Validation

XML Schema Validation

• Well-formed XML
• Valid against XSD schema
• Correct namespace declarations
• Required elements present

Business Application Header

• Valid sender/receiver BIC
• Message definition identifier matches document
• Creation date/time format

Document Validation

Example Errors

{
  "errors": [
    {
      "code": "SCHEMA_VIOLATION",
      "path": "/Document/FIToFICstmrCdtTrf/CdtTrfTxInf/IntrBkSttlmAmt",
      "message": "Currency attribute is required"
    },
    {
      "code": "INVALID_DATE",
      "path": "/Document/FIToFICstmrCdtTrf/CdtTrfTxInf/IntrBkSttlmDt",
      "message": "Date must be in YYYY-MM-DD format"
    }
  ]
}

Business Validation

When business_validation: true, package-specific rules are applied.

CBPR+ Package Rules

Party Identification

• Debtor/Creditor name required
• Valid account formats
• BIC format validation

Amount Rules

• Positive amounts only
• Currency code validation
• Settlement date validation

Agent Chain

• Valid BIC codes
• Required agent information
• Consistent agent chain

UETR Validation

• UUID format check
• Uniqueness (optional with persistence)

Canonical JSON Output

With canonical_json: true, the parsed message structure is returned:

SWIFT MT Canonical

{
  "canonical": {
    "basic_header": {
      "app_id": "F",
      "service_id": "01",
      "lt_address": "BNPAFRPPXXX"
    },
    "application_header": {
      "message_type": "103",
      "receiver_address": "DEUTDEFFXXX"
    },
    "fields": {
      "20": {"transaction_reference": "REF123456"},
      "32A": {
        "date": "250115",
        "currency": "USD",
        "amount": "50000,00"
      }
    }
  }
}

ISO 20022 Canonical

{
  "canonical": {
    "app_header": {
      "from": "BNPAFRPPXXX",
      "to": "DEUTDEFFXXX",
      "msg_def_id": "pacs.008.001.12"
    },
    "document": {
      "grp_hdr": {
        "msg_id": "MSG123",
        "cre_dt_tm": "2025-01-15T10:30:00Z"
      },
      "cdt_trf_tx_inf": {
        "pmt_id": {
          "instr_id": "INSTR123",
          "uetr": "174d2c70-..."
        }
      }
    }
  }
}

Error Codes

Interactive Playground

Validate messages using the interactive playground:

Related Pages

• Validate API Reference - Complete API documentation
• Message Types Reference - Supported SWIFT MT and ISO 20022 types
• Error Codes Reference - Validation error codes
• Sample Generation - Generate test messages
• Interactive Playground - Try validation online
• FAQ - Common questions about Reframe