Playbooks
Service First
A practical guide for service-led payment teams in South Africa, written for people resolving proof-of-payment and settlement confusion.
Support desks during payment confusion
Service First is for teams that spend much of the day clearing up payment confusion for customers or colleagues. It offers calm explanations for proof of payment disputes, settlement misunderstandings and other issues that sit between service and finance.
Service First is built for teams that sit between a customer, an order system, and the bank result. It focuses on South African cases such as Instant EFT proof that does not equal settlement, PayShap payments sent to the wrong identifier, and DebiCheck questions passed from support to finance. The material works for contact centres, branch counters, and internal service desks that need plain wording for repeat issues.
Include the first screen the payer saw, the message your staff relied on, and the exact reference captured in your system. A pinned note can then show what to verify before stock, booking access, or account changes move ahead. That record is useful when the same dispute returns through another channel later in the day.
What the pack covers
The pack sets out the payment method, the evidence that matters, and the point where service should hand over to finance or operations. It also gives wording for proof of payment disputes, pending settlement questions, and mismatched references. The aim is fewer improvised explanations during a live customer interaction.
Match Service First to the relevant playbook and any signals note before expanding the brief. Check the bank-side status against the reference actually received before goods, bookings, or account access are released. If you get in touch via the contact form, include a screenshot of the current checkout, message, or payment screen.
- Checks tied to your service workflow
- Reference capture before handover begins
- Forms for service-side payment issues
South African service conditions
South African payment support has its own pressure points. PayShap can be quick but still needs the right identifier and internal matching, Instant EFT often creates proof before funds settle, and DebiCheck questions usually involve mandate status rather than a simple yes or no. Service First keeps those distinctions visible so support teams do not rely on generic bank wording.
Load-shedding affects when screens are saved and when bank checks can be repeated. Branch traffic changes how much explanation a customer will absorb at the counter, while courier cut-offs can force an earlier decision on release. Johannesburg, Durban, Cape Town, and smaller towns all see the same core problem when proof, reference, and settlement do not line up.
Operated by Astros Marketing (Pty) Ltd from 2 Makro Place, Sunnyrock 1401.
What to send with the brief
Brief Service First with screenshots, support pain points, and what has already gone wrong. Keep the subject line factual.
Send screenshots, the support pain point, and a note on what failed in the current process. Include any proof-of-payment example, checkout wording, settlement query, or staff script that caused confusion. That gives the note a service view instead of only a finance one.
What our Real-Time Payments customers say
Verified Google reviews