ci4j-adorsys.3.5.25.source-code.pain.008.001.02.xsd Maven / Gradle / Ivy
Go to download
Show more of this group Show more artifacts with this name
Show all versions of hbci4j-adorsys Show documentation
Show all versions of hbci4j-adorsys Show documentation
HBCI4j - Home Banking Computer Interface for Java - Clone from https://github.com/hbci4j/hbci4java
Mandatory if changes occur in âMandate Identificationâ, otherwise not to be used.
Mandatory if changes occur in 'Creditor Scheme Identification', otherwise not to be used.
Mandatory if changes occur in debtor account, otherwise not to be used.
If changes occur in debtor agent and SMNDA is NOT used in OrgnlDbtrAcct
If a Creditor Reference contains a check digit, the receiving bank is not required to validate this.
If the receiving bank validates the check digit and if this validation fails, the bank may continue its processing and send the transaction to the next party in the chain.
It is recommended that all transactions within the same âPayment Informationâ block have the same âCreditor Scheme Identificationâ.
This data element must be present at either âPayment Informationâ or âDirect Debit
Transactionâ level.
It is recommended that this element be specified at âPayment Informationâ level.
This data element may be present either at âPayment Informationâ or at âDirect Debit Transaction Informationâ level.
Mandatory if provided by the debtor in the mandate.
Mandatory if 'Amendment Indicator' is 'TRUE'
The reason code from the Rulebook is indicated using one of the following message subelements.
Either âBIC or BEIâ or one
occurrence of âOtherâ is allowed.
Either âDate and Place of Birthâ or one occurrence of âOtherâ is allowed
Private Identification is used to identify either an organisation or a private
person.
âNameâ is limited to 70 characters in length.
âNameâ is limited to 70 characters in length.
If present the newâ Nameâ must be specified under âCreditorâ. âNameâ is limited to 70 characters in length.
âNameâ is limited to 70 characters in length.
If present and contains âtrueâ, batch booking is requested. If present and contains âfalseâ, booking per transaction is requested. If element is not present, pre-agreed customer-to-bank conditions apply.
This data element may be present either at âPayment Informationâ or at âDirect Debit Transaction Informationâ level.
It is recommended that this element be specified at âPayment Informationâ level.
It is recommended that all transactions within the same âPayment Informationâ block have the same âCreditor Scheme Identificationâ.
This data element must be present at either âPayment Informationâ or âDirect Debit
Transactionâ level.
Only âB2Bâ and 'CORE' is allowed. The mixing of different Local Instrument values is not allowed in the same message.
Depending on the agreement between the Creditor and the Creditor Bank, âCategory Purposeâ may be forwarded to the Debtor Bank.
Only one occurrence of âOtherâ is allowed, and no other sub-elements are allowed.
Identification must be used with an identifier described in General Message Element Specifications, Chapter 1.5.2 of the Implementation Guide.
Scheme Nameâ under âOtherâ must specify âSEPAâ under âProprietary
Only codes from the ISO 20022 ExternalPurposeCode list are allowed.
When present, the receiving bank is not obliged to validate the reference information.