Service continuity and exit
Two distinct questions: what happens if the service is interrupted, and what happens if you leave it. Both are dealt with before the service goes live, not at the time of the incident.
- Documented continuity and recovery arrangements, with their tests.
- Recovery objectives and service commitments, where contractually agreed.
- Critical external dependencies and the consequences of their unavailability.
- Data return arrangements: format, time limit, scope.
- Treatment of balances in the event of programme exit or closure.
This block is visible in internal review only. No working text appears on published pages.
Continuity
The continuity and recovery arrangements, their objectives and their tests are described in the documentation file. No availability rate or recovery objective is published on this site before it has been established and contractually agreed.
Dependencies
A service relies on third parties: hosting, technical providers, account-holding institutions. Critical dependencies and the consequences of their unavailability are identified in the file, together with the measures planned.
Exit and data return
Leaving a programme means knowing what you get back, in what format and within what time limit, and what becomes of the balances in circulation. These arrangements are settled in the contract, before the service goes live.
End of programme
The closure of a programme and the right to redemption of the electronic money remain two distinct questions. The treatment of balances is that provided for in the contract.