Signals
Demo Day
A plain note on demo sessions for teams comparing Instant EFT and PayShap before they brief sales or support.
A live demo helps when teams keep talking past each other about what a payment screen means. One person says paid, another says pending, and nobody is looking at the same fields. Demo Day is our note on showing Instant EFT, PayShap, and DebiCheck clearly enough for operations, finance, and support to use the same language.
Demo Day is written for internal sessions where support, sales, ops and finance need to look at the same payment journey and stop naming different things. The note focuses on what appears on screen during Instant EFT, PayShap and DebiCheck examples, what staff should capture, and which status labels tend to cause avoidable arguments.
Checks before the demo starts
- Training screen and role named
- Sample proof image saved for discussion
- Customer reference copied exactly as shown
- Chosen rail stated in full
Read the payment method notes that match the examples shown in your session. Run the comparison and note what each team should watch for. The method pages then cover the bank-side terms, customer actions and status wording in more detail.
How Demo Day plays out for PayShap training teams
Demo Day is a plain-language note for teams comparing Instant EFT and PayShap before they brief sales or support. It helps turn a product demo into a clear explanation of what the customer actually sees and does.
A useful Demo Day starts with the exact journey under review, not a vague request for payment training. Teams usually need to compare one PayShap flow, one Instant EFT flow, or a DebiCheck mandate step against the messages their staff currently use. In Johannesburg, Durban and Cape Town, the friction is often less about the rail itself and more about what gets said when a screen reads pending, processing or successful.
During the session, capture the first proof screen and the exact reference before anyone clicks ahead. We include a short handover note that can sit in a finance channel or next to an order record. That record matters when morning recon starts and two teams are reading different payment statuses.
What teams should leave with
The useful takeaway is shared wording for the main screens, not a thick training pack nobody opens again. A good Demo Day gives each team one reference example, one status checklist and one release check before stock, service access or delivery moves ahead. That matters more than polished slide language when the first live query lands.
Keep Demo Day next to the relevant note in Playbooks and the matching journal entry in Signals before you expand the session into wider process work. When goods, access or fulfilment depend on payment status, compare the customer reference with the bank-side result shown in the example you are using. With your contact form message, include a screenshot of the current checkout, payment prompt or proof screen.
- Session notes tied to one live flow
- Opening status screen saved before discussion
South African conditions that change training
A Demo Day for South African teams has to reflect the rails people are actually fielding questions about. PayShap prompts, Instant EFT bank redirects and DebiCheck approval steps each create different misunderstandings between front-line staff and finance. Where a merchant is live already, the session should focus on the exact handover or wording gap instead of repeating basic payment definitions.
Power cuts still affect when devices charge, when screenshots get saved and when a branch can pull up the same example twice. Courier cut-off times can also change how strict the release rule must be after a payment appears to go through. At a counter or on a support line, customers need a plain explanation of the next check, not bank language copied from a terms page.
Operated by Astros Marketing (Pty) Ltd from 2 Makro Place, Sunnyrock 1401.
What to bring into Demo Day
A plain note on demo sessions for teams comparing Instant EFT and PayShap before they brief sales or support.
File the demo note while the screens and questions are still fresh in the room. Keep it with the order note and the proof-of-payment record so finance has one trail to check. That avoids a later hunt for screenshots, references, and the version of the checkout shown in training.