Navigate DebiCheck Requirements for Netcash Debit Orders
Your debit orders are being rejected because DebiCheck mandates were never authenticated correctly through Netcash. Without bank-level approval, collections bounce, cash flow stalls, and your team spends the week reworking failed batches.
Get the DebiCheck mandate flow right once, and collection success rates recover.
Sound Familiar?
These are the DebiCheck failures collections leads bring us after months of rejected Netcash batches:
- Debit orders bounce because the DebiCheck mandate was never authenticated with the customer's bank
- TT1 real-time requests expire in 120 seconds while your team is still explaining the SMS to the client
- Failed authentications fall through to Registered Mandate (formerly RMS), then collect later with weaker priority and full dispute risk
- Collections that do not match an authenticated mandate are rejected before funds ever move
- Finance spends hours every week chasing rejected batches and re-registering mandates that should have worked the first time
RMS ended in May 2025. Unauthenticated mandates now run on Registered Mandate (RM) with evening processing and full dispute exposure. Authenticated DebiCheck stays in the early morning window, where funds are most likely to be available. Delaying a proper DebiCheck setup locks you into the weaker rail.
DebiCheck Mandate Authentication That Actually Completes
Contract signed → correct TT authentication → bank-verified mandate → early-window collection.
Contract Creates Mandate
CRM or onboarding form loads the DebiCheck template in Netcash with amount, frequency, and tracking rules
Customer Authenticates
TT1 real-time, TT2 batch, or TT3 Card and PIN, timed to how you sell so the request does not expire unused
Bank Stores Mandate
Authenticated mandate sits with the customer's bank. Collections that match it process; mismatches reject cleanly
Early-Window Collect
Authenticated DebiCheck runs in the morning window after salary credits, when collection success is highest
Everything You Need for Reliable DebiCheck Authentication
TT1 Real-Time Authentication
Customer approves the DebiCheck mandate within 120 seconds via banking app or USSD while they are still on the call or in the checkout flow.
TT2 Batch Mandates
Overnight batch authentication for high-volume onboarding. Customers have up to two days to approve before the request expires.
TT3 Card and PIN
Face-to-face mandate authentication at a card terminal. Ideal for branches, agents, and any onboarding where the customer is physically present.
Mandate Failure Recovery
Expired and declined authentications are flagged immediately. Retry paths, RM registration rules, and escalation keep revenue from leaking quietly.
CRM to Netcash Mandate Sync
New contracts in your CRM trigger the correct DebiCheck template in Netcash. Status (pending, authenticated, expired) flows back without spreadsheet chase.
Collection Success Monitoring
Dashboards show authentication rate, early-window collection success, and rejection reasons so your collections lead can act the same day.
Systems We Connect Around Netcash DebiCheck
From 54% Authenticated to 91% Authenticated
How a short-term insurer stopped DebiCheck rejections, left the RM evening rail, and recovered R840,000 in year one.
Broken Mandate Flow
- 160 monthly policies averaging R2,400, with DebiCheck requests fired hours after sale
- Only 54% of mandates authenticated; the rest expired or fell to RMS, then RM after May 2025
- Collection success stuck at 63%, with disputes reversing funds that had already landed
- Collections lead spent 10+ hours a week reworking rejected Netcash batches
- No TT3 path for agents writing policies face-to-face
Authenticated DebiCheck Flow
- TT1 fired during the sales call while the customer still had their banking app open
- TT3 Card and PIN for branch and field agents; TT2 batch for after-hours digital sign-ups
- Authentication rate climbed to 91%; authenticated collections stayed in the early morning window
- Collection success lifted to 81%, matching the industry gap between authenticated and unauthenticated rails
- Mandate status visible in CRM: pending, authenticated, expired, or declined
Before vs After DebiCheck Authentication Setup
How It Works
From mandate audit to authenticated live collections in 2 to 4 weeks.
Audit Your Mandates
We review authentication rates, TT mix, expired requests, and how many collections are still running on unauthenticated RM rails.
Free Scoping Call
30-minute call to map onboarding channels (digital, batch, face-to-face) and design the DebiCheck authentication flow for each.
Configure & Pilot
DebiCheck templates in Netcash, CRM triggers, TT1/TT2/TT3 paths, and a pilot batch against live accounts before full cutover.
Go Live & Lift Rates
Authenticated collections run in the early morning window. Monitoring tracks authentication rate and collection success week by week.
Frequently Asked Questions
What is DebiCheck and why are my Netcash collections being rejected?
DebiCheck is South Africa's authenticated debit order system, mandated by PASA. The customer must electronically approve the mandate with their bank before collections can run against an authenticated DebiCheck mandate. If the mandate was never authenticated, or the collection amount or date falls outside what was approved, the bank rejects the debit before funds move. That is the usual reason Netcash DebiCheck debit order authentication failures show up as bounced collections.
What is the difference between TT1, TT2, and TT3 DebiCheck authentication?
TT1 is real-time (customer has about 120 seconds) or delayed same-day approval via banking app or USSD. TT2 is batch authentication: requests are submitted overnight and the customer has up to two days to approve. TT3 is face-to-face Card and PIN on a payment terminal. The right mix depends on how you onboard customers. Using only one type when your sales process needs another is a common cause of expired mandates.
What happened to RMS, and how does Registered Mandate (RM) affect collection success?
The Registered Mandate Service (RMS) was a temporary path for unauthenticated DebiCheck mandates. From May 2025 it was replaced by Registered Mandate (RM). Unauthenticated RM collections process later in the day, remain fully disputable, and industry figures show roughly a 16 percentage-point lower success rate than authenticated DebiCheck collections. Getting DebiCheck mandate authentication right is how you stay in the early morning priority window.
How long does DebiCheck setup with Netcash take?
A focused DebiCheck authentication setup typically takes 2 to 4 weeks: mandate audit, DebiCheck template configuration, CRM triggers for authentication requests, pilot batch, and go-live. Businesses already on Netcash debit orders can often lift authentication rates within the first two weeks of a corrected flow.
Will customers actually approve DebiCheck mandates?
Industry-wide, only about 62% of DebiCheck mandate requests were authorised in 2024, largely because of friction and poor timing. When TT1 is fired while the customer is still engaged, or TT3 is used at the point of sale, authentication rates climb sharply. We design the customer prompt, channel, and follow-up so approval happens before the request expires.
How much does Netcash DebiCheck setup and integration cost?
DebiCheck-focused Netcash configuration with CRM mandate sync starts from around R18,000. Broader setups covering TT1/TT2/TT3 paths, failure recovery, and accounting reconciliation typically range from R30,000 to R55,000. Most collections teams presenting 100 or more debit orders a month recover the investment within 2 to 3 months from improved collection success alone.
Fix DebiCheck Authentication Before the Next Batch Fails
If your Netcash debit orders are bouncing because mandates never authenticated, you are leaving collections on the weaker rail every month.
Tell us how many debit orders you present, which TT types you use today, and where mandates expire. We will show you the authentication path that lifts collection success for your business.