Registered Mandates vs DebiCheck vs EFT Debit Orders
South African collectors have three main debit order rails to choose from: DebiCheck, registered mandates (RM) and ordinary EFT debit orders. They differ in how the mandate is established at the payer's bank, how early collections process, and how much protection you have when a payer disputes a debit.
Choosing the right rail for each payer segment directly affects your unpaid rates, dispute losses and operational cost. This page compares the three side by side.
How do the three collection types compare?
| Feature | DebiCheck | Registered mandate (RM) | EFT debit order |
|---|---|---|---|
| Payer approval | Payer actively authenticates the mandate electronically | No approval — mandate registered at payer's bank, payer notified | None — mandate held only by the collector |
| Bank record of mandate | Yes, authenticated | Yes, registered but not authenticated | No |
| Payer notification | Authentication request | Notification of registration (e.g. SMS or app message) | None |
| Processing window | Early window, first priority | Early window, second priority behind DebiCheck | Later than the early window |
| Tracking for funds | Yes, up to ten days | Yes, up to ten days | Limited or none, depending on service |
| Dispute protection | Strongest — payer authenticated the mandate | Stronger than EFT — registered details as evidence | Weakest — collector's mandate is the only evidence |
| Typical use | Consumers who can authenticate | Juristic, multi-signatory and non-authenticatable payers | Legacy books not yet migrated |
What makes DebiCheck the strongest option?
With DebiCheck, the payer must electronically confirm the mandate — usually via USSD, banking app or ATM — before you can collect. The authenticated mandate is stored at the payer's bank, which gives you the strongest possible dispute position: the payer approved the exact terms on record.
DebiCheck collections process first in the early morning processing window, giving you the best chance of reaching funds before other debits. Different transaction types (TT1, TT2, TT3) determine how the authentication is requested.
Where do registered mandates fit in?
Registered mandates exist because authentication is not always possible. Company accounts, multi-signatory accounts and payers without cellphones cannot complete DebiCheck authentication, and some authentications simply fail or expire repeatedly.
With an RM, the mandate details are registered at the payer's bank without approval. The payer is notified of the registration and can query or dispute it, but no authentication happens. In exchange:
- RM collections process in the early window, but as second priority behind authenticated DebiCheck collections.
- RM collections support tracking for available funds for up to ten days, like DebiCheck.
- In a dispute, the registered record is stronger evidence than a plain EFT mandate, but weaker than DebiCheck's payer authentication.
See What Is a Registered Mandate? for the fundamentals.
Why do EFT debit orders still exist?
EFT debit orders are the legacy rail. The mandate lives only in your records; the payer's bank processes the debit without any knowledge of the underlying agreement. That makes EFT simple and cheap to run, but it also means:
- Collections process later than DebiCheck and RM collections.
- Payers can dispute debits relatively easily, and without a bank-side mandate record the dispute usually succeeds.
- There is no built-in tracking comparable to the DebiCheck and RM services.
The industry direction is to migrate collections off EFT and onto DebiCheck and registered mandate rails, so new collection books should generally start on the modern rails.
Which one should you use?
A practical rule of thumb:
- Consumer payers who can authenticate: use DebiCheck.
- Juristic, multi-signatory or non-authenticatable payers: use a registered mandate. See Juristic and Multi-Signatory Accounts.
- Existing legacy books: continue on EFT while planning migration to DebiCheck or RM.
Many collectors run all three in parallel, routing each payer to the strongest rail available for their account type. Kwik supports DebiCheck, registered mandate and EFT collections on one platform, which makes this kind of routing straightforward.
Related topics
RM vs RMS
Clarify the difference between a registered mandate (RM) and the Registered Mandate Service (RMS), and how the service fits into debit order collections.
Registration and Notification
How mandate registration works with the payer's bank, how and when payers are notified of a registered mandate, and what happens if the payer objects.