Business Compliance Tools

Travel Rule message validator

Travel Rule message validator is a free browser tool that produces complete selected schema, field, duplicate-copy and VASP roster findings from exact message set and review scope and approved schema name and revision. Results apply only to your exact supported schema, field rules, raw messages and roster.

Free. No account or payment needed.

Messages stay in this browser. Validation does not transmit them.

Prepare exact message validation

Supply up to 100 original messages, one approved bounded inline schema, exact field checks and a VASP roster. Full scope must fit 32,000 UTF-8 JSON bytes.

Validation is free and local. The complete export price appears after validation and file preparation, before checkout.

Method and recovery limits

  • Results apply only to the exact customer-approved supported schema, field rules, raw messages and roster. A match does not establish IVMS101 conformity or jurisdictional Travel Rule requirements.
  • No message is transmitted. No sanctions screening, identity authentication, VASP registration, network membership, ownership, delivery, acceptance or legal compliance is verified.
  • The selected bounded draft-07 profile rejects remote or recursive references, definitions, unsupported keywords and formats, and complex patterns. It preserves original input and rejects duplicate JSON keys.
  • Schema validation does not coerce values, remove unknown properties, populate defaults or rewrite messages. Date and time formats require a valid calendar date and an explicit RFC 3339 offset. Leap seconds are outside this bounded profile. Numeric JSON values follow JavaScript finite-number precision. Use exact strings for identifiers and monetary units.
  • At most 100 messages, 20 field rules and 50 counterparties fit a complete 32,000-byte scope. Schema and JSON nesting are bounded to 12 levels. Complete output must fit 400,000 bytes before any paid export preparation.
  • Counterparty review states are customer assertions. An approved-roster match is an exact string comparison. A valid LEI checksum does not prove current GLEIF registration or ownership.
  • Duplicate-copy findings compare exact original message bytes. Semantically equivalent but differently spaced JSON is not classified as a duplicate. Malformed messages remain unchanged for correction and recovery.

Local recovery contains the complete original schema, supplied messages, counterparty roster and accepted findings. Download it regularly. Save the schema name and VASP pointers free in your account. Optional paid private saving retains the exact original workspace after separate approval. Restoration requires fresh scope approval and validation.

Method 2026-10-09.travel-rule-message-validation.1. The supported profile interprets inline draft-07 schemas without remote references or dynamic code generation.

Third-party interpreter and schema licenses

The fictional PDF and Word samples present findings and source attachment indexes. Download their complete fictional source JSON. These samples require tailoring and do not establish real provider acceptance.

What does the travel rule message validator produce?

Validate one selected message contract and identify schema, field, duplicate-copy and counterparty roster exceptions before any transmission.

Validate the exact supplied messages against the supported customer-approved inline schema, field rules and VASP roster. All checks run in this browser. Preserve the complete original findings and review unresolved cases before exporting.

What do you need before you start?

  • Gather the complete selected original messages, approved inline schema and VASP roster.
  • Approve the exact selected validation scope in this browser.

What information do you enter?

Enter the complete original messages, one supported inline schema, exact JSON pointers, field rules and roster. Approve this exact scope before validation. Nothing is transmitted during local preparation.

  • Exact message set and review scope
  • Approved schema name and revision
  • Complete approved inline draft-07 JSON schema
  • Complete supplied message set
  • Exact field rules
  • Your supplied VASP counterparty roster
  • Exact originator VASP ID pointer
  • Exact beneficiary VASP ID pointer
  • Approve the exact schema and scope

What you can download

Every result must identify its supplied facts, assumptions and unresolved items.

Free resultIncluded downloads

Enter your information, inspect the on-screen result and keep a browser backup.

Editing and direct copies of your entered information stay free.

  • Complete selected schema, field, duplicate-copy and VASP roster findings.
  • Formal PDF and Word report, complete original findings JSON and recovery workspace ZIP.

These supported outputs are free. No checkout is required.

Fictional message validation report (PDF). Editable report (DOCX). Requires tailoring. Samples use the finalized renderer.

How does the travel rule message validator work?

  1. 1
    Prepare the exact message contract

    Enter the complete schema, messages, field rules and roster.

  2. 2
    Approve and validate

    Confirm the selected scope and inspect every original message and finding.

  3. 3
    Prepare the finalized pack

    Build all four complete files before reviewing the checkout amount.

  4. 4
    Resume approved work

    Save selected nonsensitive answers free in your account. Optional paid saving retains the exact original workspace. Restoring requires fresh approval.

Common questions

What information does the travel rule message validator need?

Enter exact message set and review scope; approved schema name and revision; complete approved inline draft-07 JSON schema; complete supplied message set; exact field rules. Gather the complete selected original messages, approved inline schema and VASP roster.

What does the travel rule message validator produce?

Complete selected schema, field, duplicate-copy and VASP roster findings. Formal PDF and Word report, complete original findings JSON and recovery workspace ZIP. Review unresolved findings and limitations before use.

Who makes the final decision?

A responsible person reviews the result. Results apply only to your exact supported schema, field rules, raw messages and roster. A match does not establish IVMS101 conformity or jurisdictional Travel Rule requirements.

Is this tool free?

Yes. The on-screen result and listed downloads are free. No checkout is required. Keep local backups and review the stated method and limits.

Can I use the travel rule message validator for this task?

Check selected schemas, fields and counterparties. Results apply only to your exact supported schema, field rules, raw messages and roster. A match does not establish IVMS101 conformity or jurisdictional Travel Rule requirements.

What still needs review?

Results apply only to your exact supported schema, field rules, raw messages and roster. A match does not establish IVMS101 conformity or jurisdictional Travel Rule requirements.

No message is transmitted. No sanctions screening, identity authentication, VASP registration, network membership, ownership, delivery, acceptance or legal compliance is verified.

The selected bounded draft-07 profile rejects remote or recursive references, definitions, unsupported keywords and formats, and complex patterns. It preserves original input and rejects duplicate JSON keys.

Schema validation does not coerce values, remove unknown properties, populate defaults or rewrite messages. Date and time formats require a valid calendar date and an explicit RFC 3339 offset. Leap seconds are outside this bounded profile. Numeric JSON values follow JavaScript finite-number precision. Use exact strings for identifiers and monetary units.

At most 100 messages, 20 field rules and 50 counterparties fit a complete 32,000-byte scope. Schema and JSON nesting are bounded to 12 levels. Complete output must fit 400,000 bytes before export preparation.

Counterparty review states are customer assertions. An approved-roster match is an exact string comparison. A valid LEI checksum does not prove current GLEIF registration or ownership.

Duplicate-copy findings compare exact original message bytes. Semantically equivalent but differently spaced JSON is not classified as a duplicate. Malformed messages remain unchanged for correction and recovery.