Version information
Please note that usage of PmtTpInf depends on the version of EPC used. In version 2017 v1.0 usage of PmtTpInf is mandatory either under 'PmtInf' or under 'CdtTrfTxInf' (previously was optional on both levels) and EPC no longer recommends it to be used under 'PmtInf', therefore both levels are ok to be used (albeit not simultaneously as stated by ISO 20022 business rule).
EPC SEPA 2017 v1.0
Credit Transfer
EPC describes the following rules for Payment Type Information (PmtTpInf):
-
Payment Type Information must be present either under 'PmtInf' or under 'CdtTrfTxInf'
- It is recommended to use Service Level Code (SvcLvl/Cd)
- When used, the value must be "SEPA"
Earlier versions
Credit Transfer
EPC describes the following rules for Payment Type Information (PmtTpInf) element:
- It is recommended to use the element in Payment Information (PmtInf) level.
- If Instruction Priority (PmtTpInf/InstrPrty) is given the element must be used in Payment Information (PmtInf) level.
- It is recommended to use Service Level Code (SvcLvl/Cd)
- When used, the value must be "SEPA"
The rules may vary between banks. E.g. some banks accept the usage of the PmtTpInf in transaction level even when InstrPrty is used. Bank spesifics are taken into account in bank specific validation pipes.
Direct Debit
EPC describes the following rules for Payment Type Information (PmtTpInf) element:
- PmtTpInf is mandatory and can be given only in Payment Information level.
- PmtTpInf/SvcLvl/Cd is mandatory. "SEPA" only accepted value
- PmtTpInf/LclInstr/Cd is mandatory. "CORE", "COR1", "B2B" only accepted values.