Signals
Photo Angles
A practical note on screenshot checks for teams that want fewer awkward reconciliations.
One admin shortcut keeps making payment checks harder. On South African teams it usually shows up early: a proof of payment with half the screen missing, a bank app image that cuts off the time, or a DebiCheck screen grab with no customer name. Photo Angles is our note for people who need usable payment evidence.
A proof of payment can land in WhatsApp or email with no clear sign of whether the image is usable. Cropped banking screens, missing timestamps, hidden account names, and partial images all make recon harder. If you need to refer to it when you write in, include the post path in the contact form.
Screenshot details that matter first
- Time and date visible on screen
- Full payment amount shown without cropping
- Reference captured exactly as displayed
- Bank app and payment rail identifiable
Read this note alongside the pages for the payment rail itself. Photo Angles deals with evidence quality, while the explainer pages cover how Instant EFT, PayShap, or DebiCheck behave in the bank flow. Used together, they help a team separate a weak screenshot from an actual payment result.
Where bad captures cause trouble
Photo Angles looks at screenshot checking when a customer sends proof of payment instead of a bank-confirmed result. The note explains what a screenshot can show, what it cannot prove, and how to avoid messy follow-ups in recon.
Most problems start with an image that looks convincing at first glance but omits the one field the team needs. On South African banking apps that is often the posting time, beneficiary line, payer name, or final status wording. A PayShap screen with the amount only is not the same thing as a completed transfer, and a DebiCheck image without the customer name creates avoidable back and forth.
Teams usually feel this at handover points. The morning admin queue inherits screenshots from the night shift, dispatch asks whether goods can move, and recon then has to chase the customer for a second image with the missing section included. One better capture at the start removes a long thread later.
What to look out for
Not every screenshot proves the same thing. An image can show that a payment was started, but settlement still needs bank-side checking, and a missing reference or time makes a follow-up necessary. Treating every gallery image as proof of settlement is how releases go wrong.
Before access, stock, or service is released, compare the screenshot against the reference and the status your team can verify from the bank side or platform side. Photo Angles also works well next to a process note from Signals or Playbooks when staff need one rule for handling image-based proof. With your contact form message, include one example of the current proof format.
South African screens and habits
This note assumes the proof may come from a major bank app, a downloaded PDF, or a phone screenshot forwarded by a customer to a sales or accounts person. It suits teams in Johannesburg, Durban, Cape Town, and smaller branches where staff still receive proof across the counter or over WhatsApp. The point is not to collect more images than necessary, but to ask for the right one.
Local working conditions shape what counts as usable evidence. Load-shedding can push people onto mobile screenshots instead of desktop banking, in-store staff may photograph a customer phone at the till, and branch rush periods increase the chance of a rushed crop. Those conditions make a screenshot policy worth writing down in plain language.
Operated by Astros Marketing (Pty) Ltd from 2 Makro Place, Sunnyrock 1401.
Using Photo Angles in admin
A practical note on screenshot checks for teams that want fewer awkward reconciliations.
File the proof while the transaction is still fresh and the customer can still resend a complete image if needed. Photo Angles works best as a short reference for accounts, fulfilment, and front-desk staff who must decide whether a screenshot is enough for the next step.