caad.006.001.04

Q: How do I validate a caad.006 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 caad.006.001.04 is

caad.006.001.04 is an ISO 20022 message definition. Its business area is CAAD (caad), and caad.006 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 the newest published version of caad.006, out of 3 in total. Older versions remain valid, and plenty of institutions still send them, so receiving one is normal rather than a problem.

Versions of caad.006

The standard publishes 3 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

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

askiso catalog fetch caad.006

Message set	Version	Download
Acquirer to Issuer Card Messages (ATICA)	v04	iso20022.org

What AskISO does with caad.006.001.04

askiso info caad.006.001.04                    # 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 caad.006.001.04 --from-schema  # walks the schema

Questions

What business area does caad.006.001.04 belong to?

CAAD (caad).

How do I validate a caad.006 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 caad.006.001.04 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 caad.006 should I send?

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

Check a caad.006 message — paste one and see every finding, with the rule and the path behind it
All CAAD messages — the rest of the CAAD 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.