Table of contents
Generation of Univocal Payment Identifier
As defined in paragraph 7.1 of the Guidelines, the generation of an IUV code that is univocal over time is the responsibility of the Creditor, which is free to structure its composition according to its own needs, taking care that such coding complies with the existing international standards and takes into account the number of "generation points" of the code itself (IUV Code Generation Points).
IUV Code Generation Points
The pagoPA system allows a Creditor to use one or more intermediaries and/or technology partners: this circumstance means that the IUV can be generated independently at multiple entities and possibly not under the direct control of the Creditor.
This situation may also be present at Creditors with a complex, well-structured organization consisting of several autonomous organizational units, which need to generate the IUV code independently.
Therefore, an "IUV code generation point" is defined as any entity, whether or not part of the Creditor's organization, which is assigned by the Creditor to associate an IUV code with a single payment in the pending payment archive referred to in paragraph 7 of the Guidelines.
PagoPA S.p.A. will assign one or more segregation codes (progressively ascending: from 00 to 45) to each of the intermediaries/technology partners, i.e. autonomous entities of the Creditor as requested by these.
If a Creditor generates its own IUV code through autonomous entities and uses an intermediary or technology partner at the same time, the autonomous entities should be surveyed as intermediary/partners of the same institution.
The segregation code
All this being said, rules must be defined so that the payment coding is effectively univocal within the Creditor over time: this is achieved by associating a particular code that serves to segregate the institution's payment management domains with each IUV code generation point.
This code is referred to as the ‘segregation code’.
PagoPA S.p.A. assigns the segregation code to each IUV code generation point depending on the entity playing the role of intermediary or technology partner, according to the following classification:
- Centralized service providers: technological intermediaries, which deliver services in a centralized mode at the national level;
- IUV Code Generation Points: any intermediary or technological partner that does not fall under the previous classification, as well as autonomous units of the institution.
An outline of how the Segregation Code is attributed is shown in Figure 1.
Centralized service providers
These are those entities, surveyed at the general level, that provide centralized services for a community of Creditors with reference to specific procedures: such as, for example, SUAP (One Stop Shop for Productive Activities), on-line issuance of the Electronic Identity Card, issuance of registry certificates through ANPR (National Registry of the Resident Population), etc.
In some cases, such as that related to the on-line issuance of the CIE (Electronic Identity Card) or registry certificates, which allow simultaneous payment for the service, the use of the centralized procedure will be mandatory for all Italian municipalities.
The qualification as a centralized service provider must be requested from PagoPA SpA, which will update the list shown in Table 1.
Table 1 - Segregation codes for centralized services
| segregation code | Service provider | Service |
|---|---|---|
| 99 | Ministry of the Interior | CIE (Electronic Identity Card) on-line issuance |
| 98 | Ministry of the Interior | Emission of certificates from ANPR (National Registry of the Resident Population) |
| 97 | Unioncamere | SUAP (One Stop Shop for Productive Activities) |
| 96 | Automobile Club d’Italia | Road Tax |
| 85 | PagoPA S.p.A. | TARI (tax on waste)/TEFA subsidiarity |
| 81 | PagoPA S.p.A. | N/A |
| 47 | PagoPA S.p.A. | Single Fee |
Composition of the Notice Code
For all types of payment there must always be a payment notice (analog or digital) with which a Notice Number is associated, containing the IUV code within it.
Template A
The structure of the Notice Number, which conforms to pre-existing and established de facto practices and standards at PSPs, is specified by the following template, where the indicated components take on the following meaning:
$$<aux digit (1n)><IUV code (17n)>$$
| Aux Digit | Numeric value that defines the structure of the IUV code according to the number of points of its generation. The values 0-1-2 must no longer be used. |
|---|---|
| IUV code | Represents the unique payment identifier as defined in paragraph 7.1 of the Guidelines. A single pending payment can be associated with one and only one IUV code, regardless of the possible different tools made available by the PSP. For the structure of the IUV code, refer to Composition of the IUV code |
Composition of the IUV code
Template B
The composition of the IUV code is represented by the template as a concatenation of its components, which take the following meaning:
$$<Segregation code (2n)><base IUV (13n)><IUV check digit (2n)>$$
| Segregation code | Numerical value that represents the Segregation Code. |
|---|---|
| Base IUV | Numerical value that each Creditor is free to structure according to its needs, within the limits indicated by these implementation specifications. |
| IUV check digit | It represents the IUV control code, calculated using the algorithm specified in the following paragraphs. |
The provision of the IUV check digit (<IUV check digit (2n)>) does not imply for the PSP the obligation to verify but rather the power to verify, allowing the PSP itself to check the Notice Number, with an obvious streamlining effect on the payment process as it preempts the receipt of negative responses sent by the Creditor.
Generation of the Notice Number and IUV code.
Value 3 of the <Aux Digit>component
This is a template provided to manage institutions that have one or more than one intermediary/technology partner, i.e., institutions for which the "IUV code generation point" may not be univocal.
The template shows the composition to use for the Notice Number:
$$3<segregation code (2n)><base IUV (13n)><IUV check digit (2n)>$$
IUV.3 template
The composition of the IUV code is defined by the following template:
$$<segregation code (2n)><base IUV (13n)><IUV check digit (2n)>$$
where the component <IUV check digit> is calculated as the remainder of the division by 93 of the number obtained by concatenating the components , <aux digit>, <codice segregazione> and <IUV base>.
It is understood that it is the responsibility of the Creditor and/or its Intermediaries/technology partners to properly activate the portion of the APA archive affected by the payment.
Tell us what you think
For clarifications on implementation specifications, such as SACI and SANP, you can open an issue on GitHub