DevPortalPagoPA




Table of contents

Generation of the Univocal Payment Identifier

According to what is defined in paragraph 7.1 of the guidelines:
“ ..., each creditor attributes an identifier code called a “Univocal Payment Identifier” (IUV) to each collection transaction, which cannot be associated in time with any other collection issued by the same creditor.....”.
The IUV code therefore takes on a fundamental importance
“« ... for the purpose of permitting the payment reconciliation activities by the creditors and the repayment activities by the payment service providers... "
thereby representing one of the essential elements on which the pagoPA system is based.
Paragraph 7.1 of the guidelines also gives the creditors the possibility to
“ .... fully or partially delegate the generation of the Univocal Payment Identifier to a third party, making sure that univocality is maintained over time”.
As a result, the generation of the IUV code that remains univocal over time is the responsibility of the creditor that, during the creation phase, must keep in mind that this coding must comply with the existing international standards and the guidelines specified in the SACI (Implementing specifications of the payment identifier codes).

Need help?

Open a ticket using the dedicated function within your Reserved Area

Tell us what you think

For clarifications on implementation specifications, such as SACI and SANP, you can open an issue on GitHub