- Knowledgebase
- XMLdation Service Guides
- Validator User Guide
-
Glossary
-
XML / ISO 20022 Standard
-
ISO 20022 Messages
-
XML Schema
- Miscellaneous
- Attribute
- Closing Tag
- Comment
- Content
- Cvc-complex-type
- Cvc-elt
- Cvc-id
- Cvc-identity-constraint
- Cvc-minexclusive-valid
- Cvc-mininclusive-valid
- Cvc-type
- Cvc-totaldigits-valid
- Cvc-attribute
- Cvc-datatype-valid
- Maximum Length
- Cvc-enumeration-valid
- Cvc-fractiondigits-valid
- Cvc-length-valid
- Cvc-maxexclusive-valid
- Cvc-maxinclusive-valid
- Cvc-maxlength-valid
- Cvc-minlength-valid
- Cvc-pattern-valid
- Element Value
- Encoding
- Length
- Mandatory element
- Missing
- Missing Tag
- Missing Child Element
- MIXD
- Root
- Unsupported Characters
- UTF-8
- Value
- Wrong Declaration
-
EPC SEPA
-
CGI-MP
-
US ACH (Nacha)
-
SWIFT MT
-
Finvoice
-
Bank-Specific
-
XMLdation Service Guides
-
Studio Guide
-
Simulator
Validation process
The goal of XMLdation validation service is to let you know whether a specific XML file is valid against selected validation pipe.
The results and possible errors are given as informatively as possible.
In practice XML file is uploaded to XMLdation service, validation pipe is selected and results are shown. A
Below is the exact content inserted into EPC Credit Transfer pipe and content returned by our service:
- Inserted XML file
- Returned report (in large .png screenshot of the report. Downloadable as .html and .pdf from service)
Before showing the report, the validation service shows a short summary of the validation result.
As visible from the report, the service returns multiple errors and notices into relevant places of the XML file. Most of the errors also include a "read more" wikilink.
Usage of API is also supported for the validation process, removing the need for using UI and enabling automated validation process.