Status dashboard
Environment SITSummary of test runs for ISO 20022 over the last 7 days
Message distribution by domain ISO 20022
pacs · pain · camt · seev · sese
Suite execution status
Latest regression cycle
Latest runs
Click any row to see the details
| ID | Scenario | Message | Status | Time |
|---|
Most frequent validation errors
Error codes for ISO 20022
Message dictionary for MX
ISO 20022 · SR 2025Browse and manage the message schema, components and fields — with mandatory and repetition rules
Select a message
The tree structure, fields and rules are shown here
Build message MX
pacs.008.001.10Fill in the fields to have the document XML is built live according to the schema
Data form
GrpHdrCdtTrfTxInfDocument preview XML
along with coverage AppHdr and Document
Fill in the fields…
Live validation result
Schema rules and supplementary business rules
Message validation
Schema + Business rulesa document XML to check the structure, mandatory fields, BIC/IBAN formats and supplementary rules
Input XML
Validation report
Awaiting input…
Active rule coverage
The set of rules enforced in this environment
| Code | Title | Domain | Severity | Status |
|---|
Test scenarios
0 items selectedRegression suites without any coding — pick them and run
| Code | Scenario title | Message flow | Type | Status | Duration |
|---|
Counterparty simulator
DisabledDefine the downstream system behavior: response rules, delay and error rate
Run settings
is applied to the generated responses
Message flow
Request and response in chronological order
Live traffic monitoring
A selection of in-flight messages with the full details of each message
| Time | Direction | Message | ID | Amount | Sender | Receiver | Status | Delay |
|---|
Run reports
Auditable output for the test team and connectivity sign-off
Run history
Click a row to see the full details
| ID | Suite | Environment | Passed | Failed | Duration | Time |
|---|---|---|---|---|---|---|
| No run recorded yet. Start a run from the Scenarios section. | ||||||
Settings
Environment configuration, party identity and platform behavior
Party identity
Default values for generated messages
Platform behavior
Display and run options
Real server connection
By default everything runs on the local simulator. If the server MX Studio is running, enter its base URL and your account so that validation, message sending and scenario runs are performed by the real server.
The password is only used to obtain a token and is never stored in the browser. The token is refreshed automatically when it expires.
About this environment
Coverage and limitations