Validate an IVMS 101 message payload before submitting to Notabene or a counterparty VASP

Steps

1. Construct the IVMS101 JSON object with top-level keys: Originator, Beneficiary, OriginatingVASP, BeneficiaryVASP (note PascalCase for entity objects, camelCase for field names within them)
2. 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
3. For legalPerson entities, include name.nameIdentifier[].legalPersonName and legalPersonNameIdentifierType (e.g. LEGL); include LEI (Legal Entity Identifier) where available
4. 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
5. 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
6. 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