Press
Catalogue Refresh
A practical note on updating payment guides in South Africa, written for teams that need old EFT assumptions replaced with current rails and wording.
Where old EFT wording breaks
Catalogue Refresh covers the work of updating old payment guides that still treat EFT language as if nothing has changed. It helps teams replace dated assumptions with current wording on South African payment rails and customer-facing explanations.
Many payment guides still tell customers to use EFT language that no longer matches what they see in banking apps. Catalogue Refresh replaces that drift with current wording for Instant EFT, PayShap and DebiCheck, including the labels banks actually show during authorisation, proof and status checks. Teams use it when checkout text, order emails and finance notes are saying different things about the same payment.
The first pass usually starts at the page where payment is chosen, not at the bank statement. We check the payment name, the customer instruction, the proof request, and the release rule so staff are not relying on a dated assumption about clearance. That matters when a screenshot is treated as final proof, or when a reference field is copied in three different ways across the process.
What gets updated
Catalogue Refresh focuses on the live wording people touch during a transaction. That can include checkout labels, payment request emails, order confirmation text, dispatch holds, support macros and internal finance notes. The aim is to stop one team saying EFT while another team is describing a bank app flow that is not ordinary EFT at all.
Useful briefs include the current payment screen, the exact bank terms visible to customers, and the points where staff manually verify a status. On the contact form, include a screenshot of the wording that still refers to old EFT assumptions. Link the revised note to related entries in Rails, Playbooks and Signals only where that connection helps the payment explanation stay accurate.
- Checkout labels aligned to current rails
- Proof rules stated before dispatch
SA payment language in use
South African teams often inherit payment text from old invoices, copied FAQs and checkout plugins that were never reviewed together. Catalogue Refresh is written for that exact mess, whether the issue sits in a Sandton office, a Durban fulfilment desk or a Cape Town support queue. It is especially useful where customer-facing wording still treats every transfer as if bank rails and mobile flows never changed.
Bank naming matters here because customers act on the labels they recognise. A PayShap prompt, an Instant EFT hand-off and a DebiCheck approval request each create different expectations about timing, proof and reversals. During load-shedding, branch visits and courier cut-offs, weak wording turns into avoidable disputes about whether payment was made, seen or cleared.
Operated by Astros Marketing (Pty) Ltd from 2 Makro Place, Sunnyrock 1401.
Notes to send with examples
Brief Catalogue Refresh with the current payment flow, the exact bank terms on the page, and what customers already misunderstand. Keep the subject line specific.
Send the current wording exactly as it appears, including button text, pop-up instructions and any line about proof of payment. Add one or two examples of customer confusion, such as a screenshot being accepted too early or a reference being entered in the wrong field. That makes the refresh note specific to the flow your team is actually running.