Press
Partner Note
A practical note on partner payment processes in South Africa, written for teams that share settlement steps, customer references, and reconciliation work.
Partner teams using one payment note
Partner Note explains payment processes that are shared across partner teams rather than handled in one place. It covers settlement steps, customer references and reconciliation work so South African teams can use the same language across both sides.
A Partner Note is useful when checkout sits with one team while settlement and matching sit with another. Include the rail used, customer reference format, bank cut-off considerations, and whether the payment was an Instant EFT, PayShap, or DebiCheck collection. South African handovers often break on naming, so the note should state exactly which screen, report, or bank message each side relies on.
Begin with the checkout view that the customer actually saw and the reference captured at that point. Add the first proof image, any PSP event text, and the bank status used for release decisions. Finance teams can then compare one record across orders, inboxes, and settlement files without guessing which reference mattered.
What the note must carry
The finished note should show who raises the payment, who verifies it, and who closes the reconciliation item. It also needs the exact customer-facing wording for references, the bank rails in play, and any release hold that applies before stock, tickets, or access moves. Short notes work best when every line points to an operational check.
Link the Partner Note to the pages your teams actually use, such as checkout steps, settlement reports, and exception handling. Before any handover, compare the bank-side result with the customer reference stored on the order, not a copied label from chat. If you send details through the contact form, include rail used and screenshots from the current journey.
- Reference wording shared across both teams
- First proof image saved with the order
- Settlement steps listed in team order
Shared checks across both teams
Teams in Johannesburg, Durban, and Cape Town may use the same bank rail but handle exceptions differently across branches, counters, and warehouses. A Partner Note should record where walk-in queries land, who can view bank confirmations, and which references appear on statements or PSP exports. This matters when one side speaks in order numbers and the other works from bank descriptions.
Load-shedding, mobile signal drops, and late-day bank processing can all change how proof is captured and reviewed. For PayShap, small-value speed can create false confidence if the wrong reference was used. For DebiCheck, mandate status and collection timing need their own line so partner teams do not treat an instruction as settled money.
Operated by Astros Marketing (Pty) Ltd from 2 Makro Place, Sunnyrock 1401.
Material to attach with it
Send the Partner Note with checkout screenshots, bank rails involved, timing, and what the merchant or PSP has already tested. Keep the subject line direct.
Attach the checkout screenshots, customer reference example, bank rail name, and a sample settlement line from the report your team reads first. Where a PSP is involved, add the status names exactly as they appear in that dashboard. Keep the note with the order record so reconciliation staff can retrieve one packet instead of hunting across mail and chat.