Table of contents
Stand In
Stand In payment process
Stand In is a function that makes it possible to deal with a situation in which the creditor's systems are temporarily unavailable, so that the users can make payments for the pagoPA notices even in this situation, providing that the payment notice was correctly loaded into the Centralized Notice Archive (ACA).
Stand In functions for payments activated with a PSP
The Stand In function can be activated for spontaneous-payment-via-psp, in particular by retrieving the primitives paVerifyPaymentNotice and paGetPaymentV1/V2.
If the creditor does not respond to the invocation of the cited primitives within the maximum specified time, as indicated in PSP service levels, the platform automatically activates the Stand In function, then the SPC node verifies the presence of the payment notice in the Centralized Notice Archive (ACA).
If the payment notice was loaded correctly in ACA, the pagoPA platform returns to the user the amount of the notice that was previously communicated by the creditor to ADA and allows the user to make the payment.
In this case, the payment is managed in Stand In mode and at the end of the payment, the pagoPA platform sends the telematic receipt via paSendRTV1/V2, using the standard modes detailed in Fase invio ricevuta.
However, if the payment notice is not present in ACA, the user is not able to make the payment due to the fact that pagoPA does not have the necessary data.
Conditions for exclusion from the Stand In function
It is possible to define exclusions from the Stand in function via the pagoPA backoffice for entire portions of APA or specifically for each individual debt position in the ACA, by setting the payStandIn field to false.
These exclusions are motivated by the variability of the amount of the debt position until the moment of the payment.
The reasons to be attributed to all the cases of exclusion include the following mandatory list:
- Increases due to late fees and interest depending on the payment date;
- Increases due to notification fees, which vary based on the date of notification.
Tracing Stand In payments
To identify and distinguish between payments managed using the Stand In process from those managed using the “standard process”, the creditors and PSPs who want to receive this information must adjust their software to manage the new flag.
The standin flag is set in the primitives:
- verifyPaymentNotice response
- verificaBollettino response
- activatePaymentNoticeV1/V2 response
- pspNotifyPaymentV1/V2 request
- paSendRTV1/V2 request.
This flag can be set to one of the following two values:
- standin = true: this value is assigned to payments that took place using the Stand In process;
- standin = false: this value is assigned to payments that took place with the standard process.
The use of this flag makes it possible to clearly distinguish between the two payment processes.
Reporting of payments managed in Stand In mode
Payments that are successfully processed using the Stand In process are then paid to the IBAN of the creditor as previously configured. Furthermore, these payments are reported in the reporting flow with outcome code 4.
Impacts on the creditor deriving from activation of Stand In mode
Update of the debt position in the ACA
Creditors must keep the debt position updated in the ACA to guarantee that the amount is suitably updated and that the debt position is canceled. All the information for fulfilling this task is available in Archivio centralizzato avvisi.
Management of payment notices paid in Stand In mode
Creditors must be able to manage amounts that are potentially not updated with respect to the payment notices paid in Stand In mode because it may be necessary to manage payments with an amount that was not previously updated in the ACA.
Management of payment notices paid in Stand In in case of assignment to the ACA using the paCreatePosition
The Stand In mechanism, which is activated when the creditor station is temporarily unavailable, recovers the information necessary for the payment in ACA.
The integration with ACA, only and exclusively in the case of assignment via the paCreatePosition, requires the communication of the following information:
- fiscalCodePA: fiscal code of the creditor who created the debt position;
- entityUniqueIdentifierType: type of debtor (F=physical person, G=legal person);
- entityUniqueIdentifierValue: fiscal code of the debtor;
- fullName: first and last name of the debtor;
- IUV: univocal payment identifier;
- amount: amount (it is not possible to register a position with an amount equal to zero);
- description: reason;
- dueDate: due date of the debt position;
- Iban: Repayment IBAN (optional);
- postalIban: Repayment postal IBAN (optional);
- switchToExpired: flag for indicating whether or not the dueDate is binding;
- payStandIn: flag for indicating whether or not the position can be paid in Stand In mode.
If the Iban and postalIban fields were not sent, the system autonomously obtains the IBAN that will be used during the credit phase. It uses the one configured by the creditor via the pagoPa backoffice or, if this configuration is not present, the one with the most recent change is used.
The data structure confirms that there is a single total amount communicated by the creditor, which represents the sum of the amounts present in the various transfers of the original debt position. This implies that the Stand In functionality, only and exclusively in the case of assignment to the ACA via the paCreatePosition, cannot manage the division of the amounts into a multi-beneficiary debt position, as the information necessary for the execution of this payment structure is not provided.
Definition of a default IBAN for payments in Stand In mode
The creditors can define a default IBAN via the pagoPA backoffice for managing payments in Stand In mode, thereby guaranteeing the correct routing of the repayments.
If the creditor does not declare a default IBAN, the IBAN with the most recent change is used.
This information related to the default IBAN is used only if both Iban and postalIban fields have not been send via paCreatePosition.
In case of assignment to the ACA via the API for creating and updating the Debtor Position Management (GPD) service, the iban field is mandatory for every transfer.
To access the detailed guide for entering the IBAN to be used during Stand In operations, please click on the link.
Activation of Stand In mode
The logic for activating the function is based on the primitives paVerifyPaymentNotice and paGetPaymentV1/V2, of these primitives, the following faultCodes are monitored:
- PPT_STAZIONE_INT_PA_IRRAGGIUNGIBILE
- PPT_STAZIONE_INT_PA_TIMEOUT
- PPT_STAZIONE_INT_PA_SERVIZIO_NON_ATTIVO
The stations of the EC are constantly monitored in order to evaluate their availability. Stand In mode is activated if all the following conditions occur within a period of 30 minutes
during nighttime hours, between 10 pm and 6 am
- the stations have availability of less than 50%;
- the total traffic of payments managed by the station exceeds 10% of the total traffic on the NodoSPC;
during daytime hours, between 6 am and 10 pm
- the stations have availability of less than 50%;
- the total traffic of payments managed by the station exceeds 5% of the total traffic on the NodoSPC.
Deactivation of Stand In mode
The logic for deactivating the function is based on the primitive paVerifyPaymentNotice, in particular, during the period in which the station is in Stand In mode, technical calls are made to check if the station is again operational.
For the technical calls to the primitive paVerifyPaymentNotice a fake univocal payment identifier (IUV) (000000000000000000) is used in order to obtain PAA_PAGAMENTO_SCONOSCIUTO, in case of a minimum percentage of 50% positive responses, the station's Stand In condition is disabled, restoring the normal operational configuration of the creditor's station.
Pricing for the managed debt position
If the data is NOT communicated by the creditor to the ACA, Stand In mode cannot be activated. Therefore the creditor is charged a fixed amount of 5 cents for each payment for the management of the process outside of Stand In mode.
For the purposes of invoicing for Stand In mode, the creditor's data provided when registering with the pagoPA platform is used, that is, the data available as of January 1, 2025 if the institution updated the data prior to that date.
On this page
Tell us what you think
For clarifications on implementation specifications, such as SACI and SANP, you can open an issue on GitHub