A timeout should not force the citizen to start again blindly
A resident completes a form, makes payment and loses the connection before receiving confirmation. The gold standard is a safe recovery path that determines which steps succeeded and prevents unnecessary duplicate actions.
Identify the transaction state
Submission, payment and case creation may complete independently. Recover the authoritative status rather than assuming all stages failed.
Preserve work where appropriate
Draft saving and resumable processes can reduce repeated effort while respecting security requirements.
Prevent duplicate submissions
Suitable transaction identifiers and retry controls help distinguish repeated attempts from new applications.
Explain next steps
Users need a clear way to check status and obtain assistance when the result is uncertain.
Reconcile cross-system records
Payment and application systems must agree about the authorised final state.
Protect exceptions
Unusual cases, deadlines and accessibility needs may require assisted or specialist review.
Break-test: the user retries after payment succeeded
Can the system recognise the original transaction and avoid a second charge?
Connected knowledge
See Service Journey Incident Recovery, Duplicate Transaction Prevention and GovTech.
