Resources
Photo Protocol
A useful note on photo protocol for South African payments, covering which screenshots and banking proofs actually help when tracing a transaction.
Screens that matter during tracing
Photo Protocol covers which screenshots and payment proofs actually help when tracing a transaction. It also points out the images that create noise, especially when a team needs to verify a reference or follow up with a bank.
Photo Protocol is about collecting images that help a bank or finance team identify one payment event without guesswork. For South African support desks, that usually means the screen with the amount, the beneficiary name, the date, the time, and the payer reference shown exactly as entered. A cropped banking app image can be enough if those fields are visible and the account holder has hidden unrelated balances.
The most useful image is often the step just before the failure or submission, not a later chat screenshot saying payment was done. Capture the error message, the selected rail such as Instant EFT or PayShap, and the confirmation page if one appears. When a reference mismatch is being checked, a proof that shows only the bank logo and amount creates extra work.
Proof set for one payment case
A workable set is small and specific. Keep one image of the payment initiation, one image of the result or error, and one image where the reference can be read without zooming. If the issue involves DebiCheck, include the mandate prompt or decline message rather than a general account screenshot.
Store the images with the order or ticket that triggered the query, and label them with the internal case number. Link this note to Rails, Playbooks, or Signals only when the payment rail or failure pattern truly matches. If you send material through the contact form, attach the current proof examples and remove card numbers, ID numbers, and unrelated transaction history first.
- Reference visible without pinch-zoom
- Error text captured on the same screen
- Images grouped with one payment query
Common South African proof problems
Support teams in Johannesburg, Durban, and Cape Town often receive WhatsApp images that are too compressed to read the reference field. Another frequent problem is a gallery photo of a desktop monitor, taken at an angle, with glare over the bank name or timestamp. A bank statement excerpt may help later, but it should not replace the original payment screen when tracing starts.
Power cuts, weak signal, and branch queues affect how people capture proof, so the process should allow for a second image if the first one is blurred. Ask for the screen before logout where possible, because some banking apps hide useful fields after the session ends. For walk-in support, staff should know which details to cover before saving or forwarding any image.
Operated by Astros Marketing (Pty) Ltd from 2 Makro Place, Sunnyrock 1401.
Minimum fields every screenshot needs
Set a Photo Protocol for payment support: capture the error screen, the reference, the bank name, and the step before the failure, without exposing card or ID details.
Check for five things before filing a payment image: amount, date, time, bank name, and reference. Add the merchant or beneficiary name when it appears, because that helps separate a genuine proof from an old image reused by mistake. A short note beside the screenshots explaining what failed is often more useful than another full-screen capture.