What happened
The authorisation the school granted EduPay at the registry service stopped being valid. It expires on its own after a stretch without use, and it also ends if somebody revokes it from the service side.
This is not a failure of EduPay or of your school. It is how these authorisations work — and it is why the system warns you instead of letting you find out when you try to send.
How you find out
By email. Whoever administers the account receives a notice about the expired authorisation, with a button to reconnect. It goes out once per drop, not every day.
On screen. Four places change at the same time:
| Where | What appears |
|---|---|
Integrations › Debt protest |
Authorization expired badge and the explanation |
Contracts › Delinquency 90+ |
A banner at the top, with a reconnect button |
| A title's screen | The same banner, with the action buttons blocked |
Settings › Penalty and protest |
The tab badge reads Authorization expired |
What stops and what continues
Stops: sending a title to the registry, requesting a cancellation, and resending a returned title. The buttons are blocked — and stay blocked even for someone trying to force the path.
Continues: everything that is reading. The delinquency panel keeps listing who crossed the deadline, with the reasons for those who cannot be protested. You can use the reconnection window to fix records.
Also continues, and this matters most: titles already sent keep producing effect at the registry. An expired authorisation cancels nothing, suspends nothing and returns nothing. What is lost is the tracking — EduPay stops learning what happens to them.
How to fix it
1. Open Integrations › Debt protest — or click the button in the email,
which takes you straight there.
2. Click Reconnect to Protesto24h.
3. Sign in with the institution's account and authorise again.
How to know it worked
The badge goes back to Connected, the banners disappear from the other screens and the sending buttons work again. The status of titles already at the registry starts updating on its own once more.
Why this happens with nobody touching anything
The authorisation renews itself while the school uses the integration. EduPay handles that in the background, without asking you for anything.
It only truly expires after a long stretch idle — the case of a school that connected the service and went weeks without sending anything. Since protest is precisely an occasional-use feature, this is the likeliest scenario of all.
If something goes wrong
I reconnected and the banner is still there. Reload the screen. If it persists, check the Environment selector: a testing authorisation is not valid in production.
I got no email and found out from the screen. The notice goes to whoever administers the EduPay account. If that is not you, they received it.
I received the notice twice. Then there were two drops. The notice goes out once per drop — if the connection came back and dropped again, another one goes out.
I cannot reconnect: the button is dimmed. The service is not available in this EduPay environment. Talk to support.
Reviewed on · view as plain text