Construct the IVMS101 JSON object with top-level keys: Originator, Beneficiary, OriginatingVASP, BeneficiaryVASP (note PascalCase for entity objects, camelCase for field names within them)
For naturalPerson entities, ensure primaryIdentifier (family name) and secondaryIdentifier (given name, may be empty string) are present; include geographicAddress or nationalIdentification as required by the counterparty's jurisdiction
For legalPerson entities, include name.nameIdentifier[].legalPersonName and legalPersonNameIdentifierType (e.g. LEGL); include LEI (Legal Entity Identifier) where available
Submit the payload to the Notabene validation endpoint: POST https://api.notabene.id/tf/validate with the IVMS101 object as the body; inspect validationErrors array in the response
Resolve validation errors by cross-referencing the IVMS 101.2023 specification; common issues include missing countryOfResidence for naturalPerson, invalid ISO 3166-1 alpha-2 country codes, and non-Latin character sets
After passing local validation, test end-to-end with a Notabene RoboVASP (beneficiary VASP simulator) to confirm the full flow including PII encryption and status transitions
Known gotchas
IVMS 101 requires UTF-8 encoding and Latin alphabet (A-Z, a-z, 0-9) for most fields; non-Latin scripts (Chinese, Arabic, Cyrillic) must be transliterated — passing native script characters causes validation errors at some VASP implementations even if your validator accepts them
The 2023 revision of IVMS 101 added proliferation financing fields; older VASP implementations may not recognize new fields and silently drop them — verify counterparty VASP support for IVMS 101.2023 before relying on new fields
The Notabene RoboVASP environment is for testing only; transactions sent to RoboVASPs do not constitute actual Travel Rule compliance — ensure production integrations target real VASP DIDs
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp