pain.001.001.05

Q: How do I validate a pain.001 message?

Run askiso validate message.xml . The schema is found from the document's own namespace, so you do not name it. Validation needs that schema installed. To check the business rules without one, run askiso lint instead.

What pain.001.001.05 is

pain.001.001.05 is an ISO 20022 message definition. Its business area is Payments Initiation (pain), and pain.001 is the definition it versions.

AskISO does not copy the specification. The Registration Authority publishes the message definition report and the schema, free of charge. The links below go straight there.

This is one of 14 published versions of pain.001, and it is not the newest. The current version is pain.001.003.01. That does not make this page obsolete: a counterparty running an older integration may still send you exactly this version, and you will need to read it.

Versions of pain.001

The standard publishes 14 versions of this definition. A newer version does not automatically replace an older one. The scheme or market infrastructure you send to decides which version you should be using.

Where to get the schema

pain.001.001.05 is published in 1 message set. Download from the Registration Authority, then import:

askiso catalog fetch pain.001

Message set	Version	Download
Payments Initiation	v05	iso20022.org

What AskISO does with pain.001.001.05

askiso info pain.001.001.05  # metadata and schema paths
askiso validate message.xml  # full XSD validation, needs the schema
askiso lint message.xml      # business rules, needs no schema
askiso generate pain.001     # from a template, needs no schema

This message has a hand-written template with rail-aware defaults, so a sample can be generated with no catalogue installed.

SWIFT MT equivalence

One MT message converts into pain.001:

MT101 — Request for Transfer. A corporate instructs its bank to make one or more payments. MT101 retires with the rest of the MT payments suite; pain.001 replaces it.

askiso translate payment.mt101

pain.001 also converts back to MT. Both directions carry a fidelity report naming every field that was mapped, derived, truncated or lost, because conversion between the two is lossy in both directions.

Questions

What business area does pain.001.001.05 belong to?

Payments Initiation (pain).

How do I validate a pain.001 message?

Run askiso validate message.xml. The schema is found from the document's own namespace, so you do not name it. Validation needs that schema installed. To check the business rules without one, run askiso lint instead.

Does AskISO include the pain.001.001.05 schema?

No. AskISO ships no ISO 20022 specification content at all. You download the message set from the Registration Authority, then import it with askiso catalog add. The binary carries only an index: what exists, and where to find it.

Which version of pain.001 should I send?

The scheme or market infrastructure you send to decides that, not the standard. There are 14 published versions. Run askiso diff <from> <to> to see every structural difference between two of them, marked as breaking or compatible.

Check a pain.001 message — paste one and see every finding, with the rule and the path behind it
Structured addresses — the CBPR+ rule that governs every address in a pain.001, and where its timing now stands
Converting between MT and ISO 20022 — what survives the trip in each direction, and what does not
All Payments Initiation messages — the rest of the Payments Initiation area, and every other ISO 20022 message
Documentation — installing AskISO, and every command it offers

AskISO generates this page from its built-in index of the standard. The source of truth for ISO 20022 is iso20022.org.