Resources
Warranty Note
A plain-language note on warranty note for South African payments, explaining what is covered, what is not, and where bank rules take over.
Where a Warranty Note stops
Warranty Note explains what is covered by an internal payment process and what sits outside it once bank rules apply.
A Warranty Note marks the edge between your internal process and the banking system. It states what your team is willing to treat as acceptable proof, what still depends on bank settlement, and when a payment status is only provisional. For South African teams, that usually means spelling out the difference between an Instant EFT success screen, a PayShap notification, and an actual reflected credit in the right account.
Screenshots cause trouble when they are treated as payment instead of evidence. A useful note records the reference used, the account expected, the channel shown to the customer, and the point where bank rules override internal handling. That gives finance, support, and fulfilment one version to work from when a payer says the money has gone off their side.
What the note should cover
Set out the boundaries in plain terms. Include whether the note applies to release of goods, account activation, service booking, mandate collection, or manual reconciliation, then name the event that changes status from pending to accepted. If there are exceptions for weekends, public holidays, or batch-based bank processes, put them in the body instead of leaving staff to infer them.
Use the note alongside checkout wording, support macros, and internal handover rules. That keeps the discussion tied to the actual flow rather than a generic payment complaint.
- Boundary between proof and payment
- Accepted statuses named clearly
- Examples for ops and finance
Bank-rule limits worth naming
South African payment methods do not all behave the same way, so a Warranty Note should not pretend they do. PayShap can look immediate to a sender while your release rule may still require a reflected incoming payment or a matched reference. DebiCheck adds mandate and authentication questions that sit outside a simple proof-of-payment discussion.
Operational conditions matter as much as the rail itself. Load-shedding, device swaps at a branch counter, delayed bank app notifications, and late-day cut-off pressure can all distort what staff think they are seeing. A note that mentions these conditions is more useful than a generic statement that every payment must just be 'confirmed'.
Operated by Astros Marketing (Pty) Ltd from 2 Makro Place, Sunnyrock 1401.
Useful inputs
Use the Warranty Note to spell out what can and cannot be treated as confirmed payment, especially where screenshots and pending statuses cause confusion.
Bring the current wording your team uses when a customer sends a screenshot, disputed reference, or pending transfer notice. It also helps to include the handover point between support, finance, and fulfilment so the note reflects real responsibility rather than an ideal process map.