Support
Remote Check
A plain-language route through remote payment checks in South Africa, for teams who already know the operational basics.
How Remote Check fits into a payment week
Remote Check deals with payment verification when the customer is not standing in front of you.
For a Remote Check, start with the payment rail and the point where visibility broke. A PayShap screen, an Instant EFT notification, or a DebiCheck dispute each needs different evidence from the customer and from your own system. In South Africa, power cuts, delayed app alerts, and after-hours release requests often explain why proof arrives before the bank view does.
Capture the first image the customer sent, together with the reference exactly as typed. Then note the timestamp on that proof and the timestamp on your bank-side lookup, because the gap between those two often explains the mismatch. Finance teams usually need that record later when recon, dispatch, or access logs do not line up.
Remote Check output pack
Teams that need a tighter remote verification routine need more than a generic payment explainer. You should finish with a release hold point, a short evidence list, and wording that distinguishes customer proof from bank confirmation. That matters when stock leaves a warehouse or account access is granted before settlement is visible.
Match each Remote Check note to the exact handoff where risk sits, such as order release, booking confirmation, or account activation. Compare the payer reference on the proof with the reference visible in your bank or gateway before anything is handed over. If you get in touch via the contact form, include a screenshot that shows the payment state your team can currently see.
- Reference captured exactly as received
- Proof image saved with visible timestamp
Verification conditions across SA
Remote Check is useful for businesses taking payment instructions from customers who are off-site, whether that is a buyer on WhatsApp, a debtor over email, or a branch client sending proof after leaving the counter. Teams in Johannesburg, Durban, and Cape Town often face the same pattern: proof first, bank confirmation later, pressure to release in between. The note should reflect the channel used and the consequence of getting the call wrong.
Power cuts affect more than the card machine. Teams often need a saved proof image, the payer name, the amount, and the exact reference before stock leaves a Johannesburg storeroom or a Cape Town collection point. Where courier cut-offs are tight, separate bank confirmation from customer proof so staff do not treat a screenshot as settled funds.
Operated by Astros Marketing (Pty) Ltd from 2 Makro Place, Sunnyrock 1401.
Evidence to attach on day one
Brief Remote Check with screenshots, timestamps, and the exact step where the payment journey went wrong. Keep the subject line specific.
Send the first proof image, the bank or gateway view, and the exact time each one was seen. Add the step where the process stalled, such as duplicate reference, pending status, missing payer name, or a release request made before confirmation. That gives a usable remote trail instead of a loose bundle of screenshots.