Resources
Handoff Template
A working guide to handoff template for South African payment teams, so unresolved transactions move cleanly between support, finance, and ops.
Fields that prevent a bad handover
Handoff Template sets out what should travel with an unresolved payment issue when support, finance, and ops pass it along. It covers the basics such as reference, amount, payment method, customer wording, and what has already been checked.
A useful Handoff Template captures the pieces the next team will ask for first. That usually means the payment method, amount, payer name, merchant reference, bank reference if visible, order number, and the exact point where the issue stalled. In South African payment flows, the same case can move from front-line support to finance recon and then to ops, so the note must travel with enough detail to avoid retelling the story.
Screenshots matter most when they show time, status, and reference on the same screen. Add what the customer said, what staff checked, and whether goods, access, or service were held back while the payment status stayed uncertain. A short timeline helps when Instant EFT proof arrives before settlement, or when a PayShap transfer appears with wording that does not match the order record.
What a usable template includes
Teams need one place for the transaction facts, attached proof, customer wording, internal actions taken, and the decision still waiting to be made. That structure is especially helpful when DebiCheck queries sit between mandate status, collection dates, and customer disputes.
Use this Handoff Template when one payment issue needs to move between inboxes, shifts, or departments without losing context. Link the case to the matching order or account record, note which checks were completed, and record who is expected to pick it up next. Through our contact form, include a screenshot that shows the current payment status.
- Reference, amount, and payment rail
- Customer wording copied exactly
- Proof attached to one case file
Checks that suit South African rails
Instant EFT cases often need proof of payment, merchant-side status, and a note on whether bank confirmation was still pending. PayShap handovers work better when the receiving team can see the sender detail, transfer amount, timestamp, and the reason the payment could not yet be matched. For DebiCheck, include mandate state, collection attempt date, and any customer statement about approval or non-approval.
Operational conditions also shape the handover note. Load-shedding can interrupt screenshots, branch verification, or access to back-office tools, so record what could not be checked at the time. Where dispatch or service activation depends on cleared funds, state clearly whether fulfilment was paused, released, or reversed while the case was under review.
Operated by Astros Marketing (Pty) Ltd from 2 Makro Place, Sunnyrock 1401.
When to open a fresh handover
Use the Handoff Template when finance, support, and ops need the same payment story, including references, screenshots, and what the payer already tried.
Start a new handoff note when the payment story changes, not every time someone adds a comment. A fresh template is useful after a new proof of payment arrives, a bank status changes, a second payment is made, or the issue shifts from customer query to reconciliation problem. Keep the older references linked so finance, support, and ops can trace the sequence without mixing two different transaction paths.