When a cabinet loses connectivity during a rental, the most useful first question is what happened before the interruption. Did the payment finish? Did a battery actually release? Was a return recognized? Rebooting everything immediately can make those questions harder to answer.
An Estonian reader-rental pilot should prepare a recovery runbook before public use. This article proposes a staff procedure and acceptance record; it does not claim that CoreCharge already operates a local fleet or that every interrupted transaction resumes automatically.
Pass the access gate before procuring the reader
As reviewed on 17 October 2026, Stripe’s Estonia country section labels Terminal availability Private preview. Obtain confirmation of preview access for the intended account and Estonian market before reader procurement or a launch commitment. A country appearing in the general reader table is insufficient evidence that a particular account is enabled.
The proposed route uses an eligible Estonian receiving account, Estonian Terminal Location and EUR. The operator buys and registers the approved local reader through its own account. Confirm the installation’s attended, semi-attended or unattended conditions separately; preview access and technical compatibility do not themselves approve every setting.
Record a baseline while the station is working
For CoreCharge’s matched WisePad 3 integration, the cabinet’s internal controller runs the native Android rental application and Terminal SDK. The reader connects through the agreed data path, without an external phone as the normal host. Stripe processes the payment into the operator’s account; CoreCharge connects it with the order, dispensing, return and tariff.
Record the cabinet identifier, reader, application version, network arrangement and last successful controlled rental. This gives support something to compare with the interrupted condition. Keep the evidence free of full card data and account secrets.
A runbook with explicit stopping points
| Observed condition | Staff action | Evidence before proceeding |
|---|---|---|
| Guest reports a stalled attempt | Pause repeated payment or release attempts and contact the operator | Order reference, time, visible message and physical battery outcome |
| Station appears offline | Check power and the agreed connection without dismantling equipment | Dashboard status, local observations and network availability |
| Connection returns | Reconcile the original payment and rental first | Known financial result and release or return evidence |
| Unresolved discrepancy remains | Keep the affected service unavailable under the approved procedure | Named support owner and documented next action |
| Reopening is proposed | Run the agreed controlled borrow-and-return check | Matched order, battery events and financial outcome |
These are operational recommendations, not a description of automatic alerts or a native incident workflow. The local team needs a named person who notices service problems and can reach the authorized operator.
Distinguish fallback connectivity from offline operation
For the BST0332, automatic Wi-Fi-to-4G fallback is available only with a compatible active SIM, the correct configuration and cellular signal. Confirm that specific arrangement in the supplied unit. Do not extend the claim to every cabinet or interpret it as operation during a power cut.
Nor does a network fallback establish that every payment, dispense or return can safely complete offline. Test the agreed configuration under controlled conditions, with an explicit plan for uncertain outcomes. A customer should not be asked to pay again merely because a screen has not updated.
Turn a restart into acceptance evidence
Use Stripe’s Terminal testing guidance for supported test scenarios, then validate the actual approved local setup. Keep testing separate from public operation. Log which condition was interrupted and what was observed after restoration rather than writing only “restart passed.”
The full-journey validation guide helps define the acceptance record. The cabinet architecture explanation helps separate reader connectivity from cabinet-control and rental-service issues.
After access and site suitability are confirmed, review the CoreCharge reader solution and request an Estonian pilot recovery checklist. Include the intended model and network arrangement so the runbook reflects the equipment that will actually be supplied.
References and project scope
Technical references checked on 17 October 2026. The operating procedures above are planning guidance; hardware, account access and payment settings are confirmed for each deployment.