Playbooks
Demo Path
A practical guide for payment demos in South Africa, for teams showing Instant EFT, PayShap or DebiCheck to others.
Running a payment demo people can follow
Demo Path helps teams prepare payment demos that make sense to colleagues, clients or branch staff. It shows how to explain Instant EFT, PayShap and DebiCheck with realistic examples instead of bank-speak and product theatre.
Demo Path is for showing how a payment works without drifting into product theatre. Use it when a team needs to present Instant EFT, PayShap or DebiCheck to colleagues, clients, branch staff or operations leads in a way that matches what happens on the screen. South African conditions matter here, including app prompts, bank wording, references, device handover and what staff do when a customer asks questions mid-demo.
Start with the exact first screen the audience will see, not the polished summary at the end. A useful demo pack usually includes a reference example, a status check, and one image of the point where people most often hesitate or choose the wrong option. That makes it easier to stop, explain, and restart without losing the room.
What sits inside the demo pack
The pack focuses on one payment method at a time and shows the order of events from prompt to proof. Expect short presenter notes, example references, common questions from viewers, and wording for the moment when someone asks whether money has actually moved. It is built for sessions where people must understand the difference between a screen message and cleared funds.
Before expanding the session, connect Demo Path to the matching Playbooks note and any Signals entry that explains risk or confusion points. When stock, access or booking release depends on payment, compare the bank-side status with the reference captured during the demo, not the one someone remembers afterwards. Through our contact form, include a screenshot of the current checkout, app flow or mandate screen.
- Presenter notes for one payment method
- Status checks shown in the right order
- Screen examples for staff briefings
Load-shedding, branches, courier cut-offs
A demo in Sandton boardrooms lands differently from one at a branch counter in Durban or a warehouse office near Cape Town. Demo Path accounts for the way people actually ask questions here, including whether PayShap arrived, whether Instant EFT proof means settlement, and what DebiCheck acceptance looked like on the customer side. It also helps teams separate training language from release decisions.
Power cuts, mobile signal drops and shared office devices can all interrupt a live payment walkthrough. Branch traffic changes how much detail people can absorb on the spot, while courier cut-off times and dispatch rules affect which examples feel credible to the audience. A South African payment demo should match those pressures instead of pretending every session happens under perfect conditions.
Operated by Astros Marketing (Pty) Ltd from 2 Makro Place, Sunnyrock 1401.
What to send before a session
Send the payment method, the audience type, the screens you plan to show, and the exact point where previous demos became confusing. Include any bank wording, amount limits, reference format, or mandate step that needs plain explanation. Good prep starts with the awkward part, not the polished ending.
It helps to capture the note while the flow is still fresh and the screenshots still match the product. Pair Demo Path with a process note and a reference sheet when someone needs sign-off, training material or a record of what was shown in the session.
What our Real-Time Payments customers say
Verified Google reviews