Rails
Merchant Checklist
Merchant Checklist is for South African teams setting up a bank payment method and trying not to miss the unglamorous setup work. It focuses on what must be decided before launch, from checkout wording to who handles unmatched references and failed customer queries.
Checks before go-live
Merchant Checklist is a practical note for teams preparing to use a bank payment method without missing the boring but important setup details. It pulls together the questions merchants should answer around channels, reconciliation, support, and customer wording.
List the rail first, then map what staff must verify at each step. Instant EFT needs clear proof rules, PayShap needs amount and account checks, and DebiCheck needs mandate wording that matches the collection process. Add cut-off times, after-hours handling, and load-shedding workarounds before anyone publishes customer instructions.
Screenshots matter when more than one team touches payments. Capture the checkout prompt, the payment confirmation view, and the screen used for reconciliation so support, finance, and operations are looking at the same reference fields. That reduces disputes over whether goods can be released or access can be granted.
Decisions to document
Record who owns bank-side checks, what status counts as acceptable proof, and where exceptions are logged. Customer wording should name the method plainly, explain any waiting point, and tell staff what not to promise when a payment is still being checked.
Use Merchant Checklist alongside your internal release rules before expanding a payment option across more channels. Match the payer reference, amount, and bank status to the order actually in front of you, especially where manual review still happens. If you use our contact form, include a screenshot of the current checkout or payment message.
- Checkout wording reviewed by operations
- Reference format tested in reconciliation
South African operating conditions
A merchant setup note in Sandton may look different from one used at a counter in Durban or a warehouse office near Cape Town. Some teams rely on self-service checkout, while others still explain payment steps over the phone or in person. The checklist should reflect the actual channel mix, not an ideal diagram.
Power cuts can interrupt confirmation checks and delay handover between support and finance. Weekend trading, courier collection windows, and month-end volumes also change how tightly payment verification must be managed. In South Africa, those constraints belong in the setup note, not in someone's memory.
Operated by Astros Marketing (Pty) Ltd from 2 Makro Place, Sunnyrock 1401.
Material to gather first
Bring the current checkout text, refund wording, support macros, and a sample reconciliation file. Add any bank messages customers see during Instant EFT, PayShap, or DebiCheck so the checklist reflects the wording people meet in the wild.
Keep the final note where support, finance, and fulfilment can all reach it without asking for another copy. Review it whenever the payment provider changes a screen, a bank changes a flow, or your team adds a new approval step.
What our Real-Time Payments customers say
Verified Google reviews