Rails
Debicheck Basics
DebiCheck Basics explains authenticated debit orders in plain South African terms. It helps operations, finance, support, and product teams understand what the customer approves, what the bank records, and why this payment rail is handled differently from older debit order collections.
Customer approval before first collection
DebiCheck Basics gives a plain-language introduction to how authenticated debit orders work in South Africa. It is aimed at teams that need to understand customer approval, dispute risk, and the reason DebiCheck is treated differently from older debit order flows.
A DebiCheck mandate is not just a box ticked on a website or call recording kept in a folder. The customer must authenticate the mandate through their bank, and the bank checks the details presented, such as the collecting party, amount rules, and collection date pattern. That extra approval step matters when teams compare DebiCheck with ordinary EFT, card payments, or older NAEDO style debit orders.
Most confusion starts when staff treat a mandate request as if money has moved. Authentication only confirms the instruction. Collection still follows the agreed debit order process, so reconciliation, customer messaging, and dispute handling should keep mandate approval separate from successful collection.
Details customers actually approve
The focus is the information a customer sees and confirms at the bank. That usually includes the creditor name, the debit amount or amount rules, the frequency, and the date. If those details do not match the business record, the risk shifts straight into returns, complaints, and avoidable support work.
Teams often need one reference point before changing scripts or checkout wording. Keep your dispute notes, your internal debit order process, and the customer facing screens that mention authentication together. If you send a query through the contact form, include the current mandate wording so the discussion stays on the actual DebiCheck setup.
- Authenticated mandate before debit order collection
- Bank presents mandate details to customer
- Dispute risk framed in plain language
What changes in South Africa
DebiCheck sits inside South African bank rails and local debit order rules, so teams need local language rather than generic subscription billing advice. A customer may authenticate in a banking app, through internet banking, at an ATM, or through another bank supported channel. That means support teams should know that approval depends partly on the customer bank's presentation and not only on the merchant system.
South African customers are used to debit orders, but not always to the difference between an ordinary debit order and an authenticated one. Good notes explain why a DebiCheck mandate can reduce certain disputes, why failed authentication blocks the setup, and why date or amount changes cannot be waved through with vague wording. This is especially useful for collections, insurance, telecoms, lending, and membership teams.
Operated by Astros Marketing (Pty) Ltd from 2 Makro Place, Sunnyrock 1401.
Checks before rollout or retraining
Review the exact mandate details shown to customers, the channels your bank or sponsor bank supports, and the wording agents use when asking for approval. Also check what happens when the customer ignores the request, declines it, or approves after the expected collection cycle has passed.
A base note for onboarding, QA reviews, and support scripts works best with examples of approved mandates, failed authentications, and returned collections, so teams can see the difference between bank confirmation, customer consent, and settled money.
What our Real-Time Payments customers say
Verified Google reviews