Seraph Technologies ← Back to the presentation

What happens when the internet goes down?

The short answer: the agent carries on, and no patient is turned away. Here is why, without the jargon.

Most systems a bank uses talk to a computer far away. If the line to that computer drops, the system stops. Staff start writing in a book, and someone reconciles it by hand later.

This system is built the other way round. The computer that matters sits in the diagnostic centre, in the same building as the agent. The agent's laptop talks to it over the centre's own network — a cable and a switch, no internet involved. Collecting a payment never leaves the building.

The internet is only needed for the last step: passing the day's activity on to the bank. That step can wait. Serving the patient in front of you cannot.

The same morning, three ways

1

A normal morning

Inside the diagnostic centre
Agent's laptop Looks up the invoice, takes the payment, prints the receipt
Centre's server Holds every transaction for the site
The bank Receives the day's activity over the internet
Everything flows. The patient pays, the receipt prints, the bank sees it.
2

The internet drops at 10:40

Inside the diagnostic centre — unaffected
Agent's laptop Still looking up invoices and taking payments
Centre's server Still recording every transaction7 waiting
The bank Temporarily out of reach
The break is outside the building. Everything the agent touches is inside it, so collection continues. The screen shows the agent that sync is pending — nothing is hidden from them.
3

The line comes back at 11:15

Inside the diagnostic centre
Agent's laptop Carried on throughout — no gap in service
Centre's server Sends the 7 waiting payments, oldest first
The bank Receives all 7, each exactly once
Sync happens on its own. Nobody re-keys anything, and the end-of-day totals match without manual correction.

The questions people actually ask

Does the agent have to do anything differently during an outage?

No. Same screen, same steps, same receipt. The only change is a status indicator showing that transactions are waiting to be sent. There is no separate "offline mode" for the agent to remember to switch on.

Can a payment be lost?

A payment is written to the server in the building the moment it is recorded — before anything is sent anywhere. Losing it would mean losing the server itself, which is what backups are for. An internet outage cannot lose a payment, because the internet was never holding it.

Could a payment be posted twice when the line returns?

Every transaction carries its own reference. When the queue is sent, anything the bank has already received is recognised and skipped. This is the deduplication step, and it is the reason the queue can be re-sent safely if a sync is interrupted halfway.

Can the patient still get a receipt?

Yes. The receipt is produced by the printer next to the agent, from the record on the server in the building. It does not need the bank, the internet, or the VPN.

What actually does stop working?

Reaching the bank, and anything that depends on it — sending the day's activity onward, and the online portal. Card payments also depend on the POS device's own connection, which is the provider's network, not ours. Cash and mobile money collection continue to be recorded either way.

What if the power goes out, not the internet?

That is a different problem, and an honest one: this design protects against loss of connectivity, not loss of power. The server, the laptop and the printer all need power. Backup power at the site is the bank's responsibility, and it is worth planning for alongside this system.

Why this matters commercially. The diagnostic centre partnership is a proof of concept for institutional agency banking. The fastest way to lose that reputation is a morning where patients queue and are turned away because a line went down. Local-first is what keeps that morning ordinary.