Specs
Training Day specs
Training notes and briefing figures for Training Day.
How Training Day specs support onboarding
Use it to prepare teams for the exceptions that appear once the basics seem settled.
Training Day specs sets the frame for a payment session before the examples start. It names which rail is being taught, who handles the check at counter or desk, and which exception must be tested in front of the group. For this site that usually means Instant EFT proof checks, PayShap reference handling, and DebiCheck mandate disputes under South African trading conditions.
Include the exact screen, slip, or dashboard view staff will see on the day. A training pack works better when the first verification point is shown plainly and the common wrong turn is marked beside it. Teams can then save the note with a customer query, a branch file, or an internal onboarding pack without rewriting the basics.
Session pack contents
Trainers get named scenarios, role prompts, and a check order that matches live payment handling. It avoids vague advice and focuses on the moment someone must decide whether to wait, verify again, or decline release. That is more useful than a slide deck full of bank terms nobody uses at the counter.
Link Training Day specs to the matching example note on Rails, then add any wider handling points from Playbooks or warning cases from Signals before the session plan is signed off. When stock, access, or service depends on payment status, trainers should require a bank-side check against the exact reference shown to staff. When you write in through our contact form, include a current screenshot so the training example matches the live setup.
- Role cards for teller, admin, customer
- Proof screen marked with first check
- Contact route kept on the session brief
Cases drawn from SA trading days
These specs should reflect how payment questions arrive in Gauteng, Durban, and Cape Town operations, not only in tidy demo flows. A warehouse office may need dispatch hold examples, while a mall kiosk needs walk-in wording for delayed confirmation. Training Day is strongest when the session copies the places where staff actually answer payment questions.
Load-shedding can interrupt device access, saved proof, and callback routines, so the training notes must state what gets checked first when systems return. Branch queues also change the wording staff can use when explaining PayShap limits or why an Instant EFT screenshot is not final proof. Courier cut-offs matter because a late verification decision can turn into a returned parcel or a service complaint.
Operated by Astros Marketing (Pty) Ltd from 2 Makro Place, Sunnyrock 1401.
Trainer prompts and exception checks
Use Training Day when staff need plain-English guidance on Instant EFT, PayShap, and DebiCheck before going live.
Use the briefing sheet for the person running onboarding or refresher training. It should sit beside the process note, the sample proof images, and any sign-off record used by supervisors. Keeping those pieces together makes it easier to run the same payment exercise across teams without changing the facts each time.
What our Real-Time Payments customers say
Verified Google reviews