Variants — One Global Message, Purposefully Narrowed

ISO 20022 Beyond the Message

Terminology and example scope: A registered ISO variant is a particular restricted Message Definition, not every locally narrowed contract. The implementation stories also discuss ordinary community usage profiles; shared engineering lessons apply to both, but profile terminology does not imply ISO registration. Banks, service rules, versions and restrictions in unnamed examples are fictional. Drawings and ellipsis paths are conceptual, not verified variant XML or executable XPath.

A variant can contribute structural restriction, but the complete implementation profile may still need additional business rules. A community may instead constrain the global message through a usage guideline without registering an ISO variant. A restricted local XSD, API contract or spreadsheet does not by itself establish formal registration.

For a new registered variant, the submitting organisation supplies a Business Justification for RMG approval, after the commenting process. The Registration Authority verifies that the developed model complies with ISO specifications and truly restricts the approved global definition, then registers and publishes it. The official process does not require a second SEG approval of the developed variant definition merely because it restricts an already SEG-approved parent. ISO 20022 Variants — registration process.

A community could potentially restrict which external code values it accepts, but that usage restriction does not convert the external code set itself into a variant.

Explore the complete Payment Life Cycle