One input · nothing uploaded
Paste it. AskISO works out what it is.
A message, an identifier, an IBAN or a question — a single box, and the tool determines what to do with it. Every finding names the rule it originated from and its path in the document, so you can verify it rather than accept it on trust.
The engine loads automatically as soon as you begin using the page.
Ask
Answers appear here. Every finding names the rule it came from and the path in the document, so it can be checked rather than taken on trust.
About the workspace
What you can paste
The workspace accepts several categories of input and identifies which one you provided before doing anything else. It then says what it decided, so a wrong reading shows up at once rather than being buried in the result.
- An ISO 20022 message. Any XML document declaring an ISO 20022 namespace. It is linted, evaluated against the November 2026 requirements, and validated against your schema whenever you have one installed.
- A SWIFT MT message. MT101, MT103, MT104, MT107, MT202, MT204 and MT940 convert into their ISO 20022 equivalents, accompanied by a fidelity report.
- A message identifier. Enter
pacs.008for every version of that definition, orpacs.008.001.13for one specific version. - An IBAN, a BIC or a UETR. Each is checked against the standard that defines it, and any failure explains itself.
How to read a finding
Every finding carries the same four parts, because all four are needed before anybody can act on it.
The rule identifier, such as CBPR-ADDR-002, is the reference you quote in
a ticket or an email. The path gives the precise location within the
document, written as an XPath, so nobody hunts through the message by hand. The
message explains the problem in ordinary language, without jargon. The
remediation specifies what to change.
Where a correct value can be worked out, the finding gives it. A failed IBAN checksum, for example, reports the check digits that particular account number actually requires. Where no correct value can be established, the finding says so rather than guessing.
Your message is not uploaded
The workspace runs the same engine as the command line, compiled to WebAssembly and run entirely inside this browser tab. Your message is processed by code already downloaded to your own device.
You can confirm this independently. Open your browser's network panel, paste a message, and observe that no request transmits it anywhere.
Schema validation and your catalogue
Linting and the scheme rule profiles require nothing at all from you. Schema validation is different, because it needs the schema text itself, and AskISO redistributes no specification content.
Download the message sets you need from iso20022.org, free of charge, then choose the folder in the Sources panel above. Your browser reads those files locally, so they are never transmitted anywhere either.
Without a catalogue the workspace still lints and still applies the November 2026 requirements. It simply reports that schema validation did not run, rather than implying your message satisfied one.
Taking the result with you
The Studio panel exports whatever you have just executed. Findings are available as JSON, as a SARIF 2.1.0 log for GitHub code scanning, and as an evidence pack written for a human reader.
The evidence pack records the engine version, the rule profile applied, and whether schema validation actually ran. That final detail matters whenever the result is clean, because a clean result without a schema is a much narrower claim than it looks.