Table of contents
PSP service levels
Availability of the service
The payment service must be available 24x7, 365 days a year with respect to the service levels indicated below.
In total, the following is permitted:
- 36 hours of programmed stops, distributed over the course of the calendar year, at the discretion of the PSP, to be communicated to PagoPA S.p.A. at least 72 hours in advance.
- 9 hours for non-programmed stops during the calendar year, whose duration will be counted based on what is automatically detected by PagoPA S.p.A.
Service levels of the PSP methods
| Acronym | Description | Threshold on a monthly basis |
|---|---|---|
| TPNP | Maximum time for the emission of a response following the invocation of the method paVerifyPaymentNotice | 98% within a maximum of 2 seconds |
| TNSPO | Maximum time for the emission of a sendPaymentOutcome after conclusion of managing the pspNotifyPayment method with a positive outcome (outcome = OK) | 98% within a maximum of 2 seconds |
| TPSPO | Maximum time for the emission of a sendPaymentOutcome after conclusion of the payment procedures on the PSP touchpoint, both if the payment is made successfully (outcome = OK), as well as if the payment was not made (outcome = NOK) | 98% within a maximum of 2 seconds |
Managing the PSP timeouts
The timeout represents a predetermined period of time after which a given operation is considered concluded by the node.
The following table shows, for each primitive, the maximum times the node waits for the response from the PSP, remembering however that every PSP is required to respect the service levels indicated in the previous paragraph.
| Primitive | Timeout in seconds |
|---|---|
| pspNotifyPayment | 7 |
Availability of the operational workgroup
The PSP must guarantee with its system LdS the availability of their staff for the operational workgroup, for the purpose of communication with the operational workgroup of the pagoPA platform and the concerned counterparties.
The operational workgroup of the PSP reacts autonomously and as fast as possible in the case of critical events.
Procedural service levels
The overwriting flow is considered valid if sent by and no later than 24 hours from the fourth business day after receiving the payment order(D+4).
| Acronym | Indicator | Description | Value |
|---|---|---|---|
| NFER | Maximum number of incorrect flows per month | Indicates the maximum number of incorrect flows that a PSP can correct during a calendar month. | 30 |
| NBI | Maximum number of integrative SCTs per IBAN | Indicates the maximum number of SCT-FdR pairs for integration in case of a previously sent partial SCT during a calendar month. | 30 |
Tell us what you think
For clarifications on implementation specifications, such as SACI and SANP, you can open an issue on GitHub