Signals
First Photo
A short payment note on the first customer screenshot teams should capture before chasing an Instant EFT complaint.
Before anyone says sorted, the first image matters. A complete proof of payment should show the amount, date, reference, and payment rail clearly enough for somebody else to verify it. First Photo is our note on screenshots and payment evidence that stand up to a second look.
First Photo is about the very first screenshot support should ask for when an Instant EFT query starts. The useful image shows the paid amount, the date, the customer reference, and the bank rail on one screen so another person can inspect it later.
The screenshot details that matter
- Paid amount visible in full
- Status screen saved from the banking step
- Reference matches the order record
- Rail named as Instant EFT or PayShap
First Photo is not a bank tutorial, and it is not a dispute script. Read it when a payment screenshot arrives and nobody can yet tell whether the issue is the rail, the reference, or the screen itself.
How First Photo helps in a PayShap incident week
First Photo explains which customer screenshot helps most when an Instant EFT complaint lands with support. It shows teams what to capture first so they can check the bank step, the reference, and the visible status without delay.
A screenshot from a Johannesburg phone on weak data can arrive cropped, compressed, or missing the bank header. Cape Town support teams and Durban finance desks still need the same basics to verify it properly. First Photo focuses on what survives forwarding on WhatsApp, email, and ticket systems without losing the evidence that matters.
Many payment complaints go sideways because the first image is taken too late or from the wrong screen. Ask for the earliest proof that shows the payment attempt clearly, not a later gallery crop with half the details gone. That single habit reduces guesswork when staff compare the customer view with the order timeline.
What the note helps you spot
Teams use First Photo to separate a usable proof of payment from a decorative screenshot. One image can reveal whether the customer reached a completed banking step, whether the merchant reference is legible, and whether the rail shown matches the method selected at checkout. That is more useful than a long message saying the money definitely left.
Use First Photo with the linked notes before widening the incident into a bigger investigation. Save the screenshot against the order record, then compare the visible bank step with your own payment logs and checkout wording. On the contact form, include the current proof screen from your live setup.
- Checks built around screenshot evidence
- First image captured before follow-up starts
- Screenshots sent with the original query
Where South African teams get stuck
Mall counters, call-centre desks, and warehouse admin teams do not receive proof in the same format. A customer in Sandton might send an iPhone banking screen, while a branch in the East Rand gets a blurred Android crop over WhatsApp. First Photo gives staff one standard for what must be visible before anyone says the payment can be checked.
Load-shedding, weak signal, and battery-saving modes often affect when the customer captures the image. Some screenshots arrive after a failed retry, which can hide the first reference or the original bank status. Staff should therefore ask whether the picture is from the first payment attempt or a later screen after another tap.
Operated by Astros Marketing (Pty) Ltd from 2 Makro Place, Sunnyrock 1401.
Using First Photo on incident days
A short payment note on the first customer screenshot teams should capture before chasing an Instant EFT complaint.
Keep this note close to the support queue used for Instant EFT complaints. It works best when paired with an order view, a payment status log, and a short internal rule on which screenshot counts as acceptable customer proof. That way the team checks the same evidence first, even during a busy incident morning.