Table of contents
Fund transfer operation
For the fund transfer operation to each Creditor, the PSP only uses the SEPA Credit Transfer instrument. The transfer operations are timed on each operating day of the Public Connectivity System Payment Node as better specified in the next paragraph. Consistent with Articles 15 and 20 of Legislative Decree No. 11/2010, the payer's PSP is required to remit the collected amounts in a cumulative mode.
Therefore, the PSP is required to make one, and only one, transfer that contains the cumulative amount of all and only the payment transactions sent in the Reporting Flow indicated in the Flowidentifier attribute of the Remittance Information field of the SCT scheme.. The reconciliation and squaring off methods are described in the Reconciliation of remittance flow.
The envisaged SEPA Credit Transfer templates should be used for the execution of the transaction (see SEPA Credit Transfer rulebook published by EPC ).
Table 3 shows how to assign values to the attributes of an SCT template:
Table 3 - Attribution of values to SCT template
| ID | Name | Value | Optional |
|---|---|---|---|
| AT-02 | Payer | <PSP Name> pagoPA service | |
| AT-04 | Amount | <Amount> | |
| AT-05 | Remittance Information | /PUR/LGPE-REMITTANCE/TXT/<prog>/URI/<FlowIdentifier> | |
| AT-10 | Payer ID Code | <Payer Fiscal Code> | |
| AT-20 | Iban of Beneficiary | <IBAN of Beneficiary> | |
| AT-24 | Beneficiary ID Code | <Beneficiary Fiscal Code> | |
| AT-41 | Payer Reference | <EndToEndID> |
Legend:
- <prog>: is a one-digit progressive number between 0 and 9, with
- 0 -> ordinary SCT;
- 1-9 -> supplementary SCTs in the day as a result of technical anomalies;
- <Amount>: total SCT amount, i.e. the sum of the individual transaction amounts entered in the associated Reporting Flow, identifiable by <FlowIdentifier>;
- <IBAN of Beneficiary>: The PSP draws this data from the executed payment requests;
- <Beneficiary Fiscal Code>: The PSP draws this data from the executed payment requests;
- <FlowIdentifier>: specifies the data element related to the FlowIdentifier information present in the Reporting Flow described in the following Reporting Flow;
- <EndToEndID>: reference assigned by the PSP to the fund transfer operation.
Please note:
- a single SCT must be prepared for each RF, only in case of technical anomalies can supplementary SCTs be executed;
- specific SCTs may not be executed for each individual payment transaction;
- in order to perform automatic reconciliation of the payment the information of attribute AT-05 was composed according to the structure proposed by the European Association of Corporate Treasurers (EACT) in the document EACT FORMATTING RULES OF SEPA “UNSTRUCTURED” 140 CHRS FIELD FOR REMITTANCE INFORMATION and aimed at the automated processing of information between business partners. In particular, the strings "/PUR/", "/TXT/" and "/URI/" are constant tags whose meaning is defined by the EACT standard
- PUR purpose of payment, coded
- TXT free text, to be used in combination with other structured elements
- URI identification of a Remittance Advice which is sent separately
Operating day and sending of the SEPA Credit Transfer
Consistent with the provisions of Article 20 of Legislative Decree No. 11/2010, the payer's PSP shall ensure that the amount of the transaction is credited to the Creditor's account by the end of the operating day following the day indicated in the relevant telematic receipt.
In order to ensure the uniform application of the maximum execution time of transactions and also taking into account the different operating models adopted by the PSPs, regardless of the end of the operating day established by each PSP, the end of the operating day for the receipt of payment transactions to be made through the Payments Node is generally established for each PSP at 1:00 p.m. (the so-called "Payments Node operating day"), the time indicated refers to the Italian time in effect at the time of the payment transaction and the Italian calendar applies.
Specifically, all transactions arising from a Payment Request where D day is indicated in conjunction with a time up to and including 1:00 p.m. belong to the Public Connectivity System Payment Node operating day (D), while all transactions arising from a Payment Request where D day is indicated but in conjunction with a time from 1:01 p.m. until 1:00 p.m. of the next business day belong to the next Public Connectivity System Payment Node operating day (D+1).
The date and time specified in the telematic receipt (paymentDateTime element of the receipt), is decisive for the purpose of fulfilling the end user's obligation to the Creditor, regardless of the actual time or operating day at/on which the payment is credited to the Creditor.
From the expiration of the deadline for the execution of the credit to the Creditor’s account of the amount of the payment transaction, legal interest on arrears equal to the ECB rate increased by eight percentage points shall accrue.
In the event that the PSP, for reasons attributable to it, does not credit the amount of the transaction to the Creditor’s account by the end of the operating day of the Public Connectivity System Payment Node following that of the payment (the date of the crediting day is explicit in the transferDate field of the receipt), without prejudice to the debiting of default interest in the amount referred to above, the PSP will also be liable for any damage caused to the Creditor and/or the end user as a result of the delay in crediting the amount of the transaction, including damages related to the application of sanctions against the Creditor established by specific reference legislation. For example, for Creditors performing the collection service, the penalties set forth in Article 47 of Legislative Decree No. 112 of April 13, 1999, should be noted.
Rejection of the SEPA Credit Transfer
If the SEPA Credit Transfer is returned with a REJECT message to the PSP that sent it, the PSP shall immediately notify the pagoPA system management operational service through the channels made available, indicating the information in Table 4.
Table 4 - Data to be sent by the PSP in case of REJECT of the SCT
| Datum | Content |
|---|---|
| PSP Identifier | |
| Name of the PSP | |
| Creditor’s fiscal code | |
| Name of Creditor | |
| IBAN for crediting of SCT | attribute AT-20 IBAN of the account of the Beneficiary |
| SCT amount | attribute AT-04 Amount |
| SCT description | attribute AT-05 Remittance Information |
| TRN of SCT | attribute AT-43 Originator Bank’s reference number |
| Reason for REJECT message | attribute AT-R3 reason code for non-acceptance |
| Notes | to be managed by the PSP |
Based on the indications received from the pagoPA system management operational service, the Creditor and the PSP shall take action to remove the causes of the rejection and the subsequent completion of the fund transfer operation.
Once this operation is completed, the Creditor shall immediately notify the pagoPA system management operational service using the channels made available, indicating the same information as above.
Tell us what you think
For clarifications on implementation specifications, such as SACI and SANP, you can open an issue on GitHub