Signals
Courier Notes
A short payment note on courier-style reference notes, so support can match the payer, the proof, and the order.
Courier language is not the issue here, bank wording is. A payment note with no reference, no payer name, or no clue whether it was Instant EFT or PayShap creates the same sort of scramble. Courier Notes is our note on writing payment updates people can actually action.
Support teams often spend too much time decoding payment messages after dispatch has started. The note focuses on the three details that matter most in a handover: payer identity, usable reference, and proof that can be checked against the order.
Checks before a courier note goes live
- Order or parcel number recorded
- Proof image saved with date visible
- Reference copied exactly from payment
- Instant EFT, PayShap, or DebiCheck named
Courier Notes sits between the explainer pages and the support queue. It shows staff what to capture when a customer says payment was made but the delivery record still needs a match. That keeps the note useful at the point where message, payment, and parcel details meet.
How Courier Notes fits into a merchant support week
Courier Notes explains how to record references and proof of payment so support can match the payer to the order. It is aimed at teams that deal with fast handovers and need fewer mismatches between message, payment, and delivery record.
A workable courier payment note starts with the handover point, not with bank jargon. Staff need to see whether the money came by PayShap, Instant EFT, or a DebiCheck-linked collection, and whether the parcel is still at pick, packed, or out for delivery. In Johannesburg, Durban, and Cape Town, that distinction changes who checks the proof and which reference gets trusted.
Use the first usable proof, not the fifth forwarded screenshot after three chat transfers. A bank app capture, a merchant confirmation page, or a clear proof PDF can all help, provided the amount and reference are readable. Save the note where support and dispatch can both find it when a customer asks why the parcel has not moved.
What to record
A payment update should let another person act without guessing. Save the reference, keep the amount and wording exact, and pause a courier release for a second check when the money cannot yet be matched. Fancy phrasing does not help when support is trying to match money to an order under dispatch pressure.
Read Courier Notes alongside the linked payment explainers before changing message templates or release rules. Check the bank-side status against the exact reference received before stock, access, or delivery instructions move forward. Please include a screenshot that shows the current checkout or payment message when you fill in the contact form.
- Notes tied to dispatch handover steps
- First proof saved before escalation starts
South African dispatch realities included
We write for OR Tambo travel desks, Sunnyrock warehouse teams, Crown Mines offices, and mall-based payment counters where staff still handle walk-ins. We do not assume every business needs the basics repeated. If your team works at a deeper operational level, say so. Keep urgent payment exceptions apart from the standard support process.
Load-shedding affects when proof gets saved and who can verify it. Bank wording affects whether support understands if the payer used PayShap or a delayed EFT route. Courier cut-off times affect how much checking can happen before a parcel misses the vehicle.
Operated by Astros Marketing (Pty) Ltd from 2 Makro Place, Sunnyrock 1401.
Notes to gather before writing
A short payment note on courier-style reference notes, so support can match the payer, the proof, and the order.
Capture the payment note while the order is still fresh in the queue. Include the payer name used, the reference shown, the amount, and the order or parcel marker your team will search later. That record is more useful than a vague message saying payment was done.