DevPortalPagoPA

Table of contents

Service catalog

The Service catalog is the repository that contains the list of generalized services activated by the creditors for the payment process activated spontaneously at the PSP.
The Service catalog is updated and published daily.
The Service catalog information is coded in an XML file according to the trace https://github.com/pagopa/pagopa-api/blob/SANP3.3.0/xsd/CatalogoServizi_2_0_0.xsd and must be sent by each creditor to PagoPA S.p.A. using the functions provided on the service portal.
An image
The information can be requested by the individual PSPs from the pagoPA platform using the primitive nodoChiediCatalogoServizi.
Each service included in the Service catalog is associated with a set of specific data that the creditor needs to provide the PSP with the notice number, this data set is associated with an XSD schema that defines its content and makes it possible to control the information. The name of the XSD is indicated in the xsdRiferimento element of the Service catalog.
An example is shown below of the xml of the Service catalog returned in the xmlCatalogoServizi tag in base64 format via the primitive nodoChiediCatalogoServizi.
1<listaCatalogoServizi>
2	<catalogoServizi>
3		<idServizio>00009</idServizio>
4		<descrizioneServizio>School cafeteria payment</descrizioneServizio>
5		<elencoSoggettiEroganti>
6			<soggettoErogante>
7				<idSoggettoServizio>00035</idSoggettoServizio>
8				<idDominio>77777777777</idDominio>
9				<denominazioneEnteCreditore>Day care school cafeteria payment</denominazioneEnteCreditore>
10				<dataInizioValidita>2022-04-30</dataInizioValidita>
11				<dataFineValidita>2024-04-30</dataFineValidita>
12				<commissione>N</commissione>
13			</soggettoErogante>
14			<soggettoErogante>
15				<idSoggettoServizio>00036</idSoggettoServizio>
16				<idDominio>77777777777</idDominio>
17				<denominazioneEnteCreditore>Kindergarten school cafeteria payment</denominazioneEnteCreditore>
18				<dataInizioValidita>2022-06-30</dataInizioValidita>
19				<dataFineValidita>2024-06-30</dataFineValidita>
20				<commissione>S</commissione>
21			</soggettoErogante>
22			<soggettoErogante>
23				<idSoggettoServizio>00037</idSoggettoServizio>
24				<idDominio>77777777778</idDominio>
25				<denominazioneEnteCreditore>Kindergarten school cafeteria payment</denominazioneEnteCreditore>
26				<dataInizioValidita>2022-09-30</dataInizioValidita>
27				<dataFineValidita>2024-09-30</dataFineValidita>
28				<commissione>S</commissione>
29			</soggettoErogante>
30		</elencoSoggettiEroganti>
31		<categoria>School cafeteria</categoria>
32		<xsdRiferimento>mensa_scolastica_1_1_0.xsd</xsdRiferimento>
33	</catalogoServizi>
34</listaCatalogoServizi>
35
  • idServizio: service identifier;
  • descrizioneServizio: global description of the service;
  • elencoSoggettiEroganti: list of the creditors associated with the service;
  • categoria: service category;
  • xsdRiferimento: XSD schema that defines the content of the specific data for the service and permits control of the information.
The object soggettoErogante is defined as follows
  • idSoggettoServizio: identifier of the association between the service and the creditor;
  • idDominio: identifier of the creditor;
  • denominazioneEnteCreditore: description attributed to the service by the creditor;
  • dataInizioValidita: start date of validity of the service for the specific creditor;
  • dataFineValidita: end date of validity of the service for the specific creditor;
  • commissione: flag that defines whether or not to associate a share of the commission with the service by the creditor.

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