Request for a new Direct Debit Sample Clauses
Request for a new Direct Debit mandate signed by the Debtor and given to the Creditor
Figure 1 Description of flow for issuing and validating a mandate - Creditor side
1. The Creditor acquires the mandate signed by the Debtor (dataset – DS 01).
2. The Creditor dematerialises and files the information on the mandate in its archive (dataset – DS 02).
3. After receiving the mandate from the Debtor, the Creditor sends the Alignment PSP a SEDA message containing the information on the mandate (dataset – DS-SEDA 01).
4. The Alignment PSP sends the Debtor PSP a SEDA message containing the information of the mandate (dataset – DS-SEDA 01).
5. The Debtor PSP performs the following minimum required controls on the information received: that the mandate received is not already present and active17 in its archive; that the IBAN provided by the Debtor identifies an active account that can be debited18 through SDD; that the party that signed the mandate is entitled to carry out operations on the debit account; that the mandate scheme code (AT-20 – Core, B2B, other Schemes) is compliant with the debit account classification.
6. For B2B mandates, after receiving the alignment flow, the Debtor PSP obtains confirmation of the mandate data pursuant to the provisions of the SEPA B2B Scheme Rulebook and according to methods established with its client (including transmission of a copy of the mandate immediately after it is signed).
7. If the verifications have a positive outcome, the Debtor PSP activates the mandate in its archive by using the following attributes of the SEDA message received as unique key:
i. The unique Mandate reference (AT-01);
ii. The identifier of the Creditor (AT-02), excluding the business code19;
iii. The identification code of the Scheme (AT-20 - Core, B2B, other schemes). 17 If the mandate is present but inactive, the Debtor PSP shall reactivate it upon receipt of this new request message. 18 “Chargeability” includes the debit limitations that the debtor may choose pursuant to Regulation no. 260/2012.
