DevPortalPagoPA

Table of contents

IO app

![](../../.gitbook/assets/appIO_SANP (3).png)
  • The user that starts the payment using the IO app
    An image
    must scan the QR code located on the payment notice;
  • The paVerifyPaymentNotice is used to request the creditor to verify the payment option identified by the notice number;
  • The request to activate the payment reaches the creditor by means of paGetPayment;
  • once the effective payment transactions are concluded by the user, the note sends the details to the PSP via the pspNotifyPayment, in the case of a KO response by the PSP, the process is interrupted and the payment must be canceled;
  • if the PSP sends a sendPaymentOutcome after responding with KO to the pspNotifyPayment, the node would respond with KO to signal the discordant outcome;
  • if accepting the pspNotifyPayment the PSP is required to provide the outcome of the payment within 2sec with the sendPaymentOutcome, if the PSP sends an outcome = KO, the node would respond with a KO to signal the discordant outcome;
  • By means of the primitive paSendRT, the receipt is sent to the n creditors involved with the payment only if the payment was made, the receipt is an object generated by the pagoPA platform;
  • When the creditor receives the receipt, they must close the debt position and consider it fully paid.
To manage the errors, refer to Gestione degli errori.
To be able to use the metadata in a correct and standardized manner, a Dizionario dei metadata has been prepared that contains a section dedicated to information about the payment channel present in additionalPaymentInformations of pspNotifyPayment.

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