News · New this week
FASTag: how the toll gate opens before you stop
The plaza decides locally from a saved blacklist, and the money settles after the gate is already up.
Picture a highway toll at sixty kilometres an hour. Arjun has a FASTag. Vikram is paying cash. Arjun's barrier opens before he even stops. The reason is a design choice we see all over system design: decide locally, settle later.
The gate doesn't wait for your bank
Most people assume the gate waits for the bank to approve the payment. If it did, every car would wait. A network round trip in the middle of the lane would turn a fast road into a queue.
So the lane doesn't ask the bank anything before the gate opens. It only needs to answer one question, quickly, with data it already has.
What happens in the lane
The sticker is a chip with no battery. The lane reader sends out radio waves. Those waves power the chip, and the chip answers with its ID.
That's the exchange at the lane. The chip identifies itself, and that's where its part ends.
Next, the plaza checks that ID against a saved blacklist. Think of the kirana uncle's list of khata defaulters. The plaza works from a list like that, kept on hand, rather than asking anyone else.
Not on the list? The gate opens. That's deciding locally. The check runs against data the plaza has already saved, so there's nothing to wait on.
Where the money moves
The obvious follow-up is who takes the money. That happens after the gate.
The toll goes through NPCI's switch to Arjun's bank, and the bank debits his wallet. It's settled a moment later.
The two halves have different jobs. The lane has to be fast, so it uses a cheap local lookup. The payment has to go through the bank, so it takes the proper path there, just after the gate and not before it.
What to take from it
This is a pattern you can reuse. When a user-facing step has to be instant, split it. Make a quick decision from local data, then do the slow work afterwards.
So next time the barrier lifts before you brake, your money is still on its way.
Look at one slow call in a system you work on and ask whether it needs to block the user. If a saved list can answer the question, move the call to after the gate opens.
