The simplification decree ‘switch off PagoPA and payment instruments’

electronic – Articles 24 and 24-bis of Decree-Law No 76/2020 (Article 65 of Legislative Decree No 217/2017)’

quotes the obligation for authorised payment service providers

the use of the PagoPA platform for payments to public authorities of

have an upgraded platform able to meet the requirements

supplementary to the National Central Node of Payments and Detailed

in SANPs regularly updated and published by PagoPA.

The myPay project is aimed at public authorities participating in the system of

electronic Pay Payments, which want to take on the role of

technology broker. The project implements a platform

territory of electronic payments ensuring homogeneity of

use of the system by citizens and businesses on the ground

it allows all member institutions to operate under a single system of

intermediation with the national node “PagoPa”.

This platform enables payment management and regularisation.

reconciliation of debt positions to meet the requirements

imposed by SANP indicated by PagoPa, and make available functionalities

dedicated to citizens and operators of bodies for verification and management

information on paid and unpaid debt positions

by bodies (even if not collected)

The objectives of the project are to make available a platform dedicated to the

payment world able to meet the management needs of

payments by institutions in need of

— explain to the public any debt claims against them.

be able to consult them and, where appropriate, pay through integration with

National Payment Node

— manage debt entries paid through the National Node of

PagoPA payments and consequently to be regularised and reconciled with the

internal systems of the institution itself.

The aim of the project is to offer services compatible with the guidelines.

AGID in terms of compliance with SLAs, accessibility (UNI-EN

301549-2018), platform enhancement in terms of usability and

user experience for citizens, operators and bodies.

The project is based on the Payment Node Implementation Specifications:

SPC Version 3.6

The system is highly cloud-oriented and concept-centred

horizontal and vertical scalability in order to be able to adapt

dynamic and automatic at the expected increasing loads due to high pressure

the use of electronic payment instruments integrated with PagoPa.

The solution consists of the following components:

— The citizen-oriented MyPayCittadino App application and to

depending on whether you have authenticated or not, you may have at your disposal

dedicated functionalities. The application involves both a public area with:

some functionalities that do not need authentication in order to be able to be

paid out and a private area where citizens have previously authenticated

dedicated and data-centric functionalities will be available

your own.

— The trader oriented MyPayOperator App application and the

Intermediary local bodies of both the Intermediary Body. Application

provides that, depending on their application profile, each operator

can benefit from different position management features

debts to be paid and paid within stages

preparing for payment and finalising it.

* * application functionality * *

The application functionality macro-categories are:

— Functionality of the authenticated citizen

— Unauthenticated citizen functionality

— Backoffice functionality for the operator of the intermediary entity in

scope of payments

— Backoffice functionality for the payment administrator

of the intermediary body

— Backoffice functionalities for the administrator of the intermediary institution

+ + functionality Unauthenticated citizen user + +

— search for, print and pay payment notices of which it has elements

identification uniforms required by the system and if paid, download the

payment receipt

— make spontaneous payment of various types of due amount

by the various entities participating in the platform

+ + authenticated citizen user functionality + +

— search for, print and pay payment notices of which it has elements

identification uniforms required by the system

— make spontaneous payment of various types of due amount

by the various entities participating in the platform

— search for, view and pay for your due

— search for, view and download the receipt of the payment due

appropriations

* * backoffice functionality for the system administrator user of the

intermediary institution * *

— Configure the entities participating in the scheme

— Configure for each entity that is a member of the system the types of due from

display to citizens

— Configure for each entity that is a member of the system the operators for the

management of the institution’s debts

— Configure for each entity that is a member of the system the association of

operators due

* * backoffice functionality for the payment administrator user

intermediary body * *

— Configure a reduced set of attributes of the institution to which it is associated

previously entered in the system

— Configure a reduced set of attributes of the institution’s payables

previously entered in the system

— Configure the operators for the management of the institution’s debts

— Associating the institution’s operators with the institution’s obligations

— Upload due for debt positions held in the name of citizens and

undertakings for the institution

— Request massive extraction of ‘due’/‘payment notices’ and

payment receipts

— View and download local import and export flows of

data carried out by other users or by automatic systems of the institution

* * backoffice functionality for the operator of the intermediary entity in

scope of payments * *

— Upload and manage in terms of insertion, modification, cancellation of the

due for debt entries in the name of citizens; and

companies

— Request massive extraction of ‘due’/‘payment notices’ and

payment receipts for the institution

​