Resources
Install Checklist
A usable guide to an install checklist for South African payment rollouts, from bank setup to internal testing and sign-off.
Launch checks before first transaction
Install Checklist covers the practical steps around a South African payment rollout, from bank setup through internal testing and sign-off. It helps teams confirm that the payment path, reference handling, and staff checks are ready before launch.
An Install Checklist is the handover list for a payment setup before staff use it with customers. It should record the bank account to receive funds, the provider or gateway steps, the checkout or payment link in use, and who verifies settlement on day one. For South African rollouts, include PayShap naming, Instant EFT proof handling, DebiCheck mandate timing, and any cut-off linked to dispatch or account release.
Screenshots matter because payment pages, banking apps, and admin panels change without warning. Save the live payment screen, the success message, the failed-payment message, and the back-office view where references land. Add one short staff note that states what to check first when a payer says money has left their account but the order still shows unpaid.
What the rollout file should contain
A useful pack includes the exact payment route, named owners for each check, and the sign-off points before launch. Reference format should be written down in full, including length, prefixes, and whether spaces or symbols break matching. Internal testing should cover success, timeout, duplicate payment attempts, and refunds or reversals where the payment method allows them.
Link the checklist to the pages your team uses during testing, especially reference rules, settlement views, and customer-facing wording. Before stock is released or access is switched on, compare the bank-side result with the order reference captured in your system, not a copied note from chat. Please include a current screenshot of the payment step that needs review when you fill in the contact form.
- Live account and settlement details checked
- Reference rules tested with real examples
- Contact route saved for payment issues
Launch checks before go-live
Teams here often launch across web checkout, WhatsApp payment requests, and walk-in counter queries at the same time. That means the checklist must cover who sends the payment request, where proof is stored, and which screen settles arguments when a customer presents a banking notification. Add site-specific notes for Johannesburg head office, Cape Town collections, Durban dispatch, or any branch where staff still verify payments manually.
Power cuts, mobile signal gaps, and banking app delays affect payment verification more than slide decks ever admit. Settlement timing can differ from customer expectation, especially when staff confuse a successful initiation with cleared funds. Write down the hold rules for goods, service activation, and account changes so nobody improvises at the counter or in the warehouse.
Operated by Astros Marketing (Pty) Ltd from 2 Makro Place, Sunnyrock 1401.
Sign-off points before go-live
Build the Install Checklist around the live payment setup: gateway steps, bank account checks, settlement expectations, and the snags already seen in testing.
Close the checklist only after bank details, references, notifications, reporting, and exception handling have each been tested by the people who will run them. Keep the signed version with the launch notes, because audit questions usually arrive long after the setup meeting. When someone asks for proof of testing or approval, the checklist should show dates, names, and the exact payment flow that went live.