Signals
Power Windows
A short payment note on power windows and what to document when a customer loses signal mid-payment.
There is a recurring payment snag worth fixing. In South African workplaces it tends to show itself before midday: banking cut-off confusion, delayed posting after an EFT, or a same-day payment expected from a rail that does not work that way. Power Windows is our note for teams trying to plan around real payment windows.
Power Windows is about the messy middle of a payment attempt, not the polished ending. When a customer drops signal in the banking app, staff need a record of what was seen on screen, what was not confirmed, and which rail was being used.
Checks after a dropped session
- Time of signal loss logged
- Last visible banking screen saved
- Reference copied exactly from checkout
- Rail identified before follow-up begins
Use this note beside the rail pages, not instead of them. Power Windows covers interruption points, missing proof, and later verification after the customer leaves the screen. The method pages explain what Instant EFT, PayShap, or DebiCheck can and cannot confirm at that stage.
Mid-payment signal loss at noon
The awkward moment comes when a customer loses signal halfway through a payment. Record what was shown, verify what can be checked later, and separate a genuine interruption from an unconfirmed transfer.
This snag often appears when mobile coverage dips, branch Wi-Fi falls over, or a customer swaps from app to SMS and never gets back to the payment screen. Around midday, teams also mix up posting times with payment initiation, especially when an EFT was started but not visibly completed. The note helps separate a stalled attempt from money that actually moved.
Capture the first useful evidence before anyone starts guessing. A spinner, bank app error, lost session message, or half-loaded confirmation page can matter later when finance checks incoming entries. Without that snapshot, staff tend to rely on memory and the reference gets altered on the retell.
What this note tells staff
It gives teams a short record set for interrupted payments and a way to speak about status without overstating it. One line should show whether the payment was only initiated, whether proof exists, and whether the customer must verify with their bank later. That keeps handover, release, and reconciliation on separate tracks.
Link Power Windows to the matching playbooks note and a signals entry only when the interruption pattern is clear. Record the attempted payment time, the channel used, and whether the customer reached a bank confirmation screen. Please add a screenshot of the current payment or checkout setup when you fill in the contact form.
- Records for interrupted payment attempts
- Evidence saved before screen refresh
- Notes shared with finance teams
South African conditions that affect checks
In Johannesburg, Durban, and Cape Town, the same interruption can mean different follow-up depending on the rail and the customer setting. A counter payment at a mall, a warehouse collection in Crown Mines, or a phone-assisted checkout near OR Tambo all produce different proof habits. Staff need wording that fits walk-ins, remote buyers, and internal handover notes.
Load-shedding, weak indoor signal, and banking app time-outs all change what can be verified on the spot. Some customers leave with only a screenshot of the transfer setup, while others show a successful debit that has not yet posted to the recipient side. The note should tell staff when to wait, when to ask for bank confirmation, and when to mark the transfer unconfirmed.
Operated by Astros Marketing (Pty) Ltd from 2 Makro Place, Sunnyrock 1401.
Power Windows briefing points
A short payment note on power windows and what to document when a customer loses signal mid-payment.
File the interruption note while the sequence is still fresh. Include the rail used, the exact time, the last screen seen, and what the customer said happened next. That same note can then sit with the order, query, or release decision without being rewritten later.