- Knowledgebase
- ISO 20022 Messages
- ISO 20022 business rules
-
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
PaymentTypeInformationRule
ISO 20022 has the following rule regarding PmtTpInf:
- PmtTpInf may not be given in both 'PmtInf' and in 'PmtInf/CdtTrfTxInf' simultaneously
R1 PaymentTypeInformationRule*
If PaymentTypeInformation is present at PaymentInformation level, then CreditTransferTransactionInformation/PaymentTypeInformation is not allowed.
Below is a screenshot of vanilla pain.001.001.03 schema to potentially help to visualize the situation:
* Defined as R1 in pain.001.001.03, same rule is present in Direct Debits and other versions of Credit Transfers as well, but with a different R[number]