Keeping parking customers informed: live charges from a QR code

The most frequent question in a car park is "how much is it so far?", and in most places the answer lives in the attendant's head. Yet the same information is already in the record: the arrival time, the running duration, the amount so far. If the customer can see it on their own phone, the conversation in the booth gets shorter and the argument at the exit stops. This page describes how the customer side of parking can be made digital without asking anyone to install an app.

Three things a paper ticket cannot do

• The charge is not live. A ticket shows the arrival time but no amount, because the amount is unknown until the car leaves. The customer cannot work it out alone.
• Tickets get lost. Paper in a pocket is gone three hours later, and whoever calls cannot say which vehicle they are asking about.
• It is no evidence in a dispute. There is no shared screen to settle "I stayed two hours" against "it has been three".

All three are solved by one thing: a link that opens the record itself, and only that record.

How the per-record QR code works

The moment a vehicle is taken in, a QR code is created for that record. The attendant shows it from the record detail, the customer scans it with their phone camera, and the page opens in the customer's own browser.

What the customer sees:

• their own plate and a receipt number,
• the arrival time and the time elapsed so far,
• the running charge — live, from the tariff,
• the status: parked or checked out; after the exit the page shows the final amount paid.

What they do not see matters just as much: no other record, no plate list, no revenue and no till figures appear on that page. The link opens one record and cannot be guessed.

"Has my car left yet?" — the notification side

Keeping a live page open is not practical for someone parked for hours. The same page offers two routes:

• Apple Wallet pass (iPhone): the customer adds the pass to their wallet, and the charge and status update on it.
• Browser notification: where the browser supports it, "turn on notifications" sends word when the vehicle checks out.

Honesty is due here: the Wallet pass is an Apple feature, its counterpart on Android is the browser notification, and browser support varies by device. If neither is available, reopening the page shows the same information. Neither route costs anything per message.

Payment: less cash in the booth

The second step in digitising the customer side is collection. At exit the customer is shown a payment link or a QR code, pays by card on their own phone, and the exit completes by itself the moment the payment lands. Nobody stands waiting to ask "did it go through?".

The path of the money should be equally clear: the collection goes into the business's own PayTR or Stripe account. The app does not move money or hold a balance; it only receives the "paid" signal from the provider. Connecting the account is covered in the payment account guide.

The screen at the entrance is a channel too

When the booth television shows live free spaces and the tariff, drivers who have not even entered yet are informed: is there room, what does it cost. The same screen carries a QR code as well, so a driver can scan it and follow their own vehicle.

Plates and amounts never appear on the board. That is a deliberate limit: what someone paid is not public information. Setup happens once — the six-digit code shown on the television is typed into the phone. Details are in the TV setup guide.

When does this genuinely help?

1. Long stays.The customer sees the amount before walking back to the car and has the money ready; the exit moves faster.
2. Disputed exits.The arrival time is the same on both screens, so the conversation runs on the record rather than on memory.
3. Valet and handover flows.When the person dropping the car off is not the one collecting it, the link shows both of them the same record.
4. Night shifts.As card payment spreads, less cash accumulates in the booth.