What is DebiCheck? South Africa's guide to authenticated debit collections
DebiCheck is a uniquely South African debit collection system that requires consumers to authenticate payment mandates directly through their bank before any collection can be processed. Introduced to reduce fraud and disputes associated with traditional debit orders, it gives businesses a more reliable, traceable foundation for recurring collections, and gives consumers greater control over what leaves their accounts.

What is DebiCheck?
DebiCheck is South Africa's authenticated debit order system, introduced to protect consumers from debit fraud and help businesses reduce disputes and failed collections. Unlike traditional debit orders, which rely on the business to hold evidence of a mandate, DebiCheck requires the customer's bank to authenticate and record the mandate digitally before any collection can take place. Once authenticated, the bank verifies each subsequent collection against that mandate before processing it.
The result is a more secure, more traceable system for everyone involved, and measurably better outcomes for businesses collecting recurring payments. In a Stitch pilot using DebiCheck infrastructure, Stitch collected on 74% of previously uncollectable debit order mandates. That number reflects what becomes possible when the authentication burden shifts from the business to the banking system.
How DebiCheck works – step by step
- The business submits a mandate request to the customer's bank, specifying the collection amount, payment method and collection date.
- The bank sends the customer a request to review and confirm the mandate details. This can be done via their banking app, at point of sale, or at certain ATMs.
- The customer confirms or adjusts the terms (for example, changing the collection date) and authenticates the mandate via digital signature.
- The bank records the approved mandate on the DebiCheck register and sends a confirmation to the business.
- When a collection is due, the bank checks the debit order details against the registered mandate. The collection only processes if the details match.
This bilateral verification process is what sets DebiCheck apart. A mandate cannot be created without the customer's explicit consent, and a collection cannot proceed unless it matches the authenticated terms. This makes it significantly harder for customers to dispute authorised payments — and significantly harder for fraudsters to initiate unauthorised ones.

DebiCheck vs traditional debit order: What's the difference?
Traditional Electronic Funds Transfer (EFT) debit orders are fast and cost-effective, but they carry a significant liability: the mandate is held by the business, not the bank. If a customer disputes a transaction, the debtor's bank queries the creditor's bank, which then requests the business to provide evidence of the agreed mandate. If that evidence isn't produced within the specified timeframe, the collection is reversed, and the business absorbs the loss.
EFT debit orders tend to generate high dispute rates as a result. For businesses in insurance, telecommunications, financial services and healthcare, where consistent collections are operationally critical, this creates material revenue risk and ongoing administrative overhead.
DebiCheck shifts this dynamic. Because the bank holds the authenticated mandate, disputes are far harder to sustain. Collections are also prioritised above other collection methods at settlement, processed in the early morning window to maximise success rates against customers' accounts.
Card tokenisation is a third option for recurring collections , enabling headless, pre-scheduled transactions without the customer present. Card does carry higher fees than debit order transactions, however, making it better suited as a fallback method than a primary collection route.
The three types of DebiCheck Mandate
DebiCheck provides businesses with three ways to initiate a mandate request, each suited to different use cases:
Transaction Type 1 (TT1) mandates are sent to the customer's bank in real time. The customer can authenticate immediately, or up until 8pm on the same day. This is typically used for individual mandate requests. If the customer does not authenticate within that window, the process must restart.
Transaction Type 2 (TT2) mandates are sent to the customer's bank overnight, giving the customer two days to action the request. This is typically used for batch mandate files. Again, if the customer does not authenticate in time, the process must restart.
Transaction Type 3 (TT3) uses card-present authentication at point of sale (POS) to authorise the mandate immediately, during the initial transaction. This is the most efficient method for businesses that onboard customers in person, as it eliminates the follow-up authentication step entirely. Stitch supports TT3 mandate creation, enabling businesses to authenticate DebiCheck mandates at POS in real time.

How DebiCheck protects against fraud
DebiCheck was designed specifically to address the fraud vulnerabilities of traditional debit orders. The protections built into the system include:
- Mandate authentication: the customer must authenticate the mandate via their bank before any collection can take place, confirming the amount, date and merchant details are correct.
- Unique mandate reference: each DebiCheck mandate carries a unique reference number linked to the customer's approval, preventing unauthorised alterations or resubmissions.
- Real-time notifications: customers receive a notification when a mandate is created, allowing them to flag unauthorised requests immediately.
- Mandate visibility and control: customers can view and manage their DebiCheck mandates via their banking app and cancel any they did not authorise.
- Biometric and multi-factor authentication (MFA): DebiCheck integrates with bank mobile apps that use fingerprint, facial recognition and MFA to confirm transactions, raising the barrier for fraudulent activity.
- Merchant verification: before confirming a mandate, the customer sees the merchant's details — making it harder for fraudsters to pose as legitimate businesses.
What DebiCheck can be used for
DebiCheck is suitable for any business that collects recurring payments. Common use cases include:
- Insurance: monthly premiums, annual policy renewals and instalment-based cover. DebiCheck reduces the disputed collections and failed payments that contribute to the high negative sentiment Stitch and DataEQ have observed in South African insurance payment conversations.
- Financial services: loan repayments, investment contributions and savings plans. Consistent, authenticated collections reduce arrears and support better customer outcomes.
- Telecommunications: mobile contracts, data plans and device payment arrangements. DebiCheck's 'set it and forget it' model suits customers who want consistent billing without manual intervention.
- Healthcare: recurring medical aid contributions and payment plans for ongoing treatment.
- Subscription services: streaming, gym memberships, software plans and any service billed on a regular cycle. DebiCheck mandates can be scoped to a fixed period, after which the bank stops processing payments automatically — reducing disputes and manual cancellation management.
Best practices for DebiCheck implementation
Offer multi-method collections: customers should be able to choose which account their recurring payments come from, and have a fallback method – such as card or Pay by bank – in place for instances where a collection fails. This reduces missed payments without requiring manual intervention.
Maintain clean mandate data: collections fail when mandate information is outdated or incorrectly stored. Keeping mandate status and collection data consistently updated before attempting collection , and using multiple fallback banks, materially improves success rates.
Match the mandate type to the use case: TT1 works well for immediate, individual onboarding. TT2 suits batch processing. TT3 is the most efficient option when customers are being onboarded at a physical point of sale. Stitch can help identify the right setup for your specific collections flow.
Can a DebiCheck be reversed?
A DebiCheck order cannot be reversed. However, if a customer believes they did not authorise a mandate, they can raise a dispute with their bank. Customers can also cancel future DebiCheck collections via their banking app, though a small fee may apply depending on the bank..
How Stitch supports DebiCheck
Stitch is integrated directly with South African banks and the DebiCheck system, enabling businesses to set up and manage authenticated debit mandates across TT1, TT2 and TT3 transaction types. Stitch's Collections solution is engineered to support multi-method fallbacks, real-time mandate tracking and the kind of operational visibility that keeps recurring payment programmes running efficiently at scale.
FAQs
What is DebiCheck in South Africa?
DebiCheck is South Africa's authenticated debit order system, introduced by the South African banking industry to reduce debit fraud and disputes. It requires customers to authenticate payment mandates directly through their bank before any collection can be processed. The bank then verifies each collection against the registered mandate before it proceeds, making unauthorised debits significantly harder to execute.
How is DebiCheck different from a normal debit order?
A traditional EFT debit order relies on the business to hold the mandate — if a customer disputes a transaction, the business must produce evidence of consent or the collection is reversed. DebiCheck shifts this responsibility to the bank, which authenticates and stores the mandate digitally. This makes disputes harder to sustain and collections more reliable for businesses.
Can a DebiCheck be cancelled or reversed?
A DebiCheck collection that has already been processed cannot be reversed. However, customers can dispute a mandate they believe they did not authorise, and can cancel future collections via their banking app. A small fee may apply depending on the bank.
What are TT1, TT2 and TT3 mandates?
These are the three transaction types used to initiate a DebiCheck mandate. TT1 is a real-time request that must be authenticated on the same day. TT2 is sent overnight and gives the customer two days to respond, making it suited to batch processing. TT3 uses card-present authentication at point of sale, enabling immediate mandate authorisation during the initial customer interaction — the most efficient option for in-person onboarding.
Which industries benefit most from DebiCheck?
DebiCheck is particularly valuable in insurance, financial services, telecommunications, healthcare and any subscription-based business where consistent recurring collections are operationally critical. Businesses in these sectors that still rely on traditional EFT debit orders face disproportionate dispute rates and revenue loss from failed collections.
How does DebiCheck improve collection rates?
Because mandates are authenticated by the bank and verified at each collection attempt, there is less scope for disputes and fewer grounds for reversal. DebiCheck collections are also prioritised above other collection methods at settlement, processed in the early morning window to maximise success. In a Stitch pilot using authenticated debit order infrastructure, Stitch collected on 74% of previously uncollectable mandates.
Optimise your DebiCheck payments




