Is PagoPA down? User reports show problems with PagoPA

Is PagoPA down right now?

A payment stuck on in progress for a public notice sends payers here for a plain PagoPA status. PagoPA down reports climb when the IO checkout, the pagoPA site checkout or a body module stops answering.

On a normal day the notice opens with its sum and body name. The checkout takes a card or a wallet, and the receipt lands in the app right after. Faults usually hit one part: the checkout, the receipt, the notice state or the IO login. The rest of the flow keeps working while that part stalls.

Is PagoPA down for me or everyone?

Try the same notice on the pagoPA checkout site in a browser. A notice that pays there points at the IO app or its session. The same stall on the site answers is PagoPA down for me with a shared break.

Payments stuck in progress

A pagoPA payment stuck in progress needs patience first: the official advice is to wait about half an hour before you retry. A retry too soon can double the charge, since the first payment can clear right after the retry. An avviso that shows as already paid while the payer never paid needs the creditor body, not the checkout.

Keep the notice code and the IUV code from the notice. Those two codes let support and the body trace the payment state. A payment charged but missing a receipt also needs those codes in the support message.

Receipts, amounts and provider choice

A receipt missing after a charge usually lags behind the bank debit by a short while, and an automatic reversal can follow a failed match. A wrong amount on the notice comes from the body that issued it, so the checkout cannot fix the sum. The provider choice at checkout also matters: each provider carries its own fee and its own card rules. Check the receipt area in the IO app before you retry. A receipt shown there proves the payment closed. A notice still open after a charge needs support with the notice code in hand.

SPID login and missing messages

SPID login to the IO app can fail on wrong credentials, a provider outage or an outdated in-app browser. Messages from a body can also go missing when the service sits inactive or the push switch sits off. A PagoPA outage shows when checkouts fail across many bodies at once, since the shared platform sits behind them all. Test the SPID login on the provider site first. A login that works there points at the app, and a fresh install usually clears it. For missing messages, check the services area for the service state.

Wallet documents and body services

Wallet documents in the IO app come from the issuing body, so a document missing there means the body never issued it or revoked it. Removing and re-adding the service can refresh the wallet list. Body services in the services area show which bodies send messages and notices to the app.

Common PagoPA Problems and Fixes

A stuck pagoPA payment or a missing receipt usually settles with one of these moves.

Wait half an hour before you retry

A payment stuck in progress can clear on its own within half an hour.

Keep the notice code and IUV ready

Copy the notice code and the IUV code from the notice before you pay. Support and the body trace every payment from those two codes.

Check the receipt area before you retry

Open the receipt area in the IO app and look for the payment. A receipt shown there proves the payment closed, even if the notice screen lags.

Test SPID on the provider site

Sign in on the SPID provider site with the same credentials.

Switch the provider at checkout

Pick a different provider at the checkout step when one refuses the card. Each provider carries its own fee and card rules.

Having a problem with PagoPA?

Comments are public and help others understand the issue.

Subscribe

Login

Notify of

new follow-up comments new replies to my comments

Label

{} [+]

Name*

Email*

Label

{} [+]

Name*

Email*

0 Comments

Oldest

Newest Most Voted