Resources
Safety Brief
A concise note on safety brief for South African payments, with the checks that help teams avoid fraud, bad account data, and risky shortcuts.
Fraud checks before release
Safety Brief lists the checks that help South African teams avoid fraud, bad account details, and risky shortcuts. It focuses on the moments where payment pressure is high and a weak process usually shows itself.
A Safety Brief starts at the handover point where stock, access, or service could be released against weak proof. It sets out which checks matter for Instant EFT, where PayShap screenshots mislead staff, and when a DebiCheck message is required before collection. South African teams often face pressure near dispatch cut-offs, month end, and after load-shedding interruptions, so the note must name those risk moments plainly.
Teams should capture the payer name, bank reference, amount, and the source of the proof before acting on any message. That record matters when a screenshot is cropped, a reference is reused, or an internal chat strips context from the original request. Keep one short version for the till, front desk, or finance queue so the same checks are repeated every time.
What staff must verify
Spell out the difference between a payment claim and a bank-confirmed status. It should also state when account details must be checked again, who may approve a change of beneficiary banking details, and which wording is safe to send to a payer. Good safety notes remove guesswork from busy payment windows.
Use Safety Brief with incident notes, checkout wording, and staff scripts before any wider process change is published. If DebiCheck applies, include the exact consent step and the point where collections must stop until the payer has approved the mandate. Please include a screenshot that shows the current payment prompt or proof request when you fill in the contact form.
- Bank status checked before goods leave
- Account changes confirmed off-chat
- No POP requests via personal email
Risks common in South Africa
Local payment risk often comes from speed, not complexity. PayShap can move quickly enough to tempt staff into trusting a screenshot, while Instant EFT can create confusion when the customer thinks authorisation means settlement. DebiCheck adds another control point, and the brief should explain that a debit order may not proceed as if consent was assumed.
Branch counters, call centres, and courier desks all need slightly different wording for the same control. During load-shedding or network trouble, staff may be pushed to accept forwarded proof or a verbal promise from a payer, which is exactly when weak habits cause losses. The note should say what may never be accepted over chat or email, including card PINs, banking app passwords, one-time pins, and full login images.
Operated by Astros Marketing (Pty) Ltd from 2 Makro Place, Sunnyrock 1401.
Records worth keeping on file
Write the Safety Brief around fraud checks, account verification, DebiCheck consent, and what staff may never ask a payer to send on chat or email.
Keep the approved script, proof example, and escalation rule together with the transaction record. When fraud is suspected, file the payment reference, time received, staff member involved, and the exact message that triggered the release request. That gives finance and operations a usable trail instead of scattered screenshots.