Specs
Debicheck Basics specs
Setup notes and briefing numbers for Debicheck Basics.
Mandate fields your team must capture
The DebiCheck Basics specs page breaks the topic into the checks, states, and records that matter during implementation. It is useful when you need a working list of what must be captured, confirmed, and stored.
DebiCheck Basics specs starts with the minimum record set behind a valid debit order mandate. Capture the account holder name, bank account details, collection amount, frequency, debit day, and the exact authority wording shown to the payer. Add channel details too, because TT1, TT2 and electronic mandate flows do not leave the same trail.
Store the first confirmation outcome with the mandate record, not in a separate inbox or chat. The useful items are the reference used at registration, the response received from the bank, and the date and time stamps tied to that event. When a dispute appears later, those three records usually matter more than a long internal note.
Statuses that affect collection handling
The specs page separates mandate setup from collection processing so teams do not mix approval state with payment result. A mandate can be awaiting confirmation, accepted, rejected, suspended, amended, or cancelled, while the debit instruction can still have its own outcome. Keeping those states apart helps finance, support, and ops read the same case correctly.
Use Debicheck Basics specs alongside checkout wording, signed authority text, and exception rules before any rollout grows wider. Check how the payer sees the request, how your system stores the bank response, and what staff must do if details change after confirmation. It helps to include a sample of the current mandate or collection screen with your contact form message.
- Mandate data fields listed clearly
- Bank response codes saved with timestamps
- Amendment and cancellation records retained
SA banking conditions that change implementation
South African debit order work is shaped by sponsor bank rules, PASA messaging formats, and the customer experience inside major banking apps. A DebiCheck request that reads clearly on one bank screen can look cramped or unfamiliar on another. That is why the specs should note field lengths, reference wording, and what must still make sense on a phone.
Collection timing also matters locally because debit day behaviour differs around month-end, weekends, and public holidays. Teams should define what happens when confirmation has not been completed before the intended run date, and who may move a collection to a later cycle. Keep call centre scripts aligned with that rule so customers hear one explanation.
Operated by Astros Marketing (Pty) Ltd from 2 Makro Place, Sunnyrock 1401.
Implementation pack for Debicheck Basics
Bring the current mandate wording, sample bank responses, screen captures, and the list of fields your platform sends downstream. Note whether the flow is once-off setup, recurring collections, or a change to an existing authority. Failed test cases are useful here because they show which state changes your records missed.
File the specs with the operational note that tells staff when to retry, when to stop, and when to request a new mandate. Include where evidence is stored, how references are searched, and which record is treated as the source of truth. That keeps audits, disputes, and customer queries tied to the same facts.
What our Real-Time Payments customers say
Verified Google reviews