No surprises. Three confirmation points, the same names every transit card top-up uses anywhere in the world.
You arrive on the recharge page, type the 10-digit serial printed on the card front and the mobile number that should appear on the receipt. Pick a preset amount or type a custom one. The page validates the form on the spot — no server round-trip yet.
On our side: the input never leaves the browser at this stage. We do not pre-flight the serial against any registry.
Clicking Continue to payment takes you to the dedicated checkout subdomain. The bank-card form there is rendered by our PCI-compliant acquirer; their script handles the network call. You enter the 16-digit number, expiry and CVV, then press Pay.
On our side: we never see the card number. The acquirer returns an approval token plus the masked last-4. Nothing else.
If the bank approves the charge, the confirmation page shows the order id, the amount and the masked last-4 of the card. We post the credit to the smart-card account in the same instruction — most of the time within seconds.
On our side: the order record now contains order id, amount, mobile, masked last-4 and the credit-posting status. The card number you typed earlier is not stored beyond the next 24 hours.
The bus card system occasionally returns a posting error — typically when the card is blocked, lost or pending re-issue. In that case the bank charge is reversed automatically. The smart-card account is never partially credited. If 24 hours pass without resolution, the chargeback is initiated to your card at our cost. Refund window for traced-but-not-delivered top-ups is 14 calendar days.