This is wede’s own test, with wede’s own test data. The terminals were simulated in software; the platform and every check were the real wede environment. wede never publishes, names or identifies its clients, their data or their use cases.
The scenario
A payment terminal (POS) and a cash machine (ATM) of a test organisation kept working without network, then reconnected. Each operation reached wede between 2 h 19 min and 3 h after it was captured.1
Devices registered
Both devices registered as hardware of the organisation, each with its own reconciliation source (terminal counter, ATM journal), plus a bank statement source. See Devices.
2
Captured without network
5 operations on the POS (4 payments and 1 reversal) and 4 on the ATM (3 withdrawals and 1 reversal), each protected on the device with an integrity checksum.
3
Synced out of order
The ATM sent a reversal before the withdrawal it reverses. The POS sent its batch, then the same batch again.
4
One message altered
A captured message was changed after capture (50.00 EUR became 500.00 EUR) and sent with the others.
5
The organisation's records arrived
The POS counter, the bank statement and the ATM journal, with one value deliberately different and two records that match no operation. See Reconciliation.
The results
Totals as captured: 115.89 EUR in and 212.00 EUR out.
What it means
An outage stops being a gap in the books. Operations taken without network come back whole, once, with their origin and their time, and they meet the organisation’s own records by rule.
wede sets no limit of its own. Amount limits are the organisation’s decision, set in its offline policy, and there is no maximum time without network.
Repeat it with your own equipment
Run the same proof with your own devices and systems, in your own sandbox, and keep a sealed report. Production is never touched, and the report belongs to you.1
Open a proof run
In the dashboard, open Proof kit, or call the API.
2
Run your equipment
With your sandbox key, go through the seven situations: capture without network, out of order, a batch sent again, an altered message, completeness, your own records and your offline policy.
3
Finish and keep the report
The report says, check by check, whether anything was lost, stored twice or accepted altered. A check you did not exercise is never reported as passed. Anyone with the report can compute its seal again.
Proof kit
How to run a proof and read the report.
Banking: payment continuity
The full integration for payment points and agents.