Doocat

DebiCheck Mandate: A Guide for South African Lenders

Content authorBy DoocatPublished onReading time12 min read
A bank advisor demonstrates a mobile banking app to a customer in a bright, modern office, both engaged in conversation.

This article is an operational guide to running mandate-controlled debit orders as authenticated collections in South Africa. It covers the parties involved and the submission and response sequence, then the exception outcomes your staff will actually see and the questions to put to your sponsoring bank before go-live.

DebiCheck mandate basics

A DebiCheck mandate is an electronic authorization that your customer confirms directly with their own bank, which then stores the agreed terms and validates later collections against them. It sits at the center of Authenticated Collections, the stream that replaced the early debit order systems discontinued in 2021.

Here's the distinction that matters in operations. Authentication establishes who can collect and on what terms. It says nothing about whether money will be in the account on the day. RealPay, a South African collections provider, states it directly: "DebiCheck guarantees the validity of the mandate and provides strong dispute protection. Actual collection success still depends on the customer having sufficient funds on the debit date."

So treat the DebiCheck mandate as a permission record and the collection as a separate event with its own outcome. Everything below builds on that separation.

Who does what

Four parties are involved in every authenticated collection, and each holds a different part of the record. As the lender, you hold the underlying credit agreement and the data you submitted. Your sponsoring bank or technology provider formats and transmits the request, while the customer’s bank authenticates the customer and stores the registered terms against which each collection is validated. PayInc, the clearing house that rebranded from BankservAfrica in August 2025, clears messages between the two banks. No single party holds the complete picture, which is why your own records must be comprehensive enough to stand alone.

The process begins with mandate initiation, when the lender captures the agreed terms and submits a request through its sponsoring bank or provider. The authoritative record at this stage sits in the lender’s system. During DebiCheck authentication, the customer’s bank contacts the customer through a banking channel and records their response, making the customer’s bank the authoritative source for the authentication record. During validation, the customer’s bank checks each submitted collection against the registered terms and remains the authoritative source for those terms. Finally, the collection is presented during the early-morning window, after bulk salary credits, with the clearing and settlement records providing the authoritative evidence of the transaction’s processing and settlement.

DebiCheck mandate workflow

A clean banking app interface shows a flowchart for DebiCheck mandate authentication, featuring rounded UI cards and supporting charts.

The sequence below runs from signed credit agreement through to mandate maintenance. Each step has one control point, and skipping any of them produces the exception patterns described later in this guide. Volumes make the discipline worth it: PayInc processed 329 million Authenticated Collections transactions in FY2025, with 5% year-on-year growth even after Registered Mandate volumes were split out in May that year.

Capture agreed details

Before anything is submitted, the DebiCheck mandate data must match the credit agreement exactly. The customer's bank validates against what you send, so a typo in the account number or an instalment that differs from the signed schedule turns into a rejection you pay for.

  • Customer identity details and a current cellphone number held at their bank, because that number is where the authentication prompt lands

  • Account number, account type and branch, noting that DebiCheck runs against current, savings and transmission accounts of natural persons and sole proprietors

  • Instalment amount, maximum collection amount, first collection date and collection day

  • Frequency, tracking indicator, your abbreviated short name as it will appear on the customer's statement, and the contract reference number

Ready to digitise your financial institution?

Talk to our team about your roadmap and discover scalable digital banking solutions tailored to banks, fintechs and microfinance institutions.

Request a Demo →

Send DebiCheck authentication

Submission goes through your sponsoring bank or a technology provider, and the transaction type you pick decides how long the customer has to respond. TT1 is real time, with roughly 120 seconds to respond through a banking app or USSD prompt, or until 8pm the same day on the delayed variant. TT2 goes out in a batch and gives the customer until the end of the next business day. TT3 authenticates at a card terminal with card and PIN, which suits in-branch onboarding.

What comes back is a response code and a mandate reference, together with a timestamp and the authenticated parameters. Store all four. If your sales flow is online and after hours, TT2 is the realistic choice, and your system needs a pending state to hold the record while you wait.

Record the response

A transmission acknowledgement from your provider means the message left your system. It is not DebiCheck authentication. Teams that collapse the two into one status field end up presenting collections against mandates nobody ever approved.

Keep the submitted parameters and the returned response code with its timestamp, along with the mandate reference issued by the customer's bank and the signed or recorded customer agreement that sits behind it. Capitec's 2020 annual report noted that the authentication rate for new debit orders was below 30% in the early years of the scheme, which tells you how much of your book will sit in a non-authenticated state at any time. Your records need to show which accounts those are.

Confirm collection eligibility

Before a collection is submitted, one check runs: does it match an active authenticated DebiCheck mandate on amount and date, as well as on frequency and account? The customer's bank performs the same check and rejects deviations before processing. Doing it first on your side saves the fee and the exception handling.

Eligibility and payment success stay in separate fields. A collection can be perfectly eligible and still come back unpaid, and a collection can be funded and still be blocked because the mandate was suspended last week. Tracking is set per collection, up to a ten-day maximum, and where you use it the mandate should disclose it.

Manage mandate changes

Not every change carries the same obligation, and the mandate amendment matrix in FirstRand's collections terms is the clearest published breakdown. A change to the collection day or the first collection date requires re-authentication, as does a change to your abbreviated short name. A change to the maximum collection amount or the tracking indicator triggers notification instead. A change to frequency or the contract reference number needs a new DebiCheck mandate altogether.

FNB's import documentation adds a practical constraint worth building into your rules engine: the first collection date cannot be changed once a collection has already been processed against the mandate. If an amendment times out or fails, the original terms stay in force, so keep collecting on them and re-engage the customer. Suspensions come from the customer's side and you're notified at the time, which makes them a service signal as much as a payments one.

Retain supporting evidence

Your evidence file answers reconciliation and the customer on the phone. It also answers a bank dispute and an audit trail. Under the National Credit Regulations, credit providers must keep the credit agreement and the record of payments made for three years from termination of the agreement, and electronic format is acceptable.

  • The authenticated parameters and mandate reference, with the response timestamp

  • Every submitted collection with its outcome code, tracking period and settlement date

  • Amendment history, with the trigger for each change and whether it required renewed DebiCheck authentication

  • Customer contact logs tied to the mandate reference

Scheme-side retention sits with your sponsoring bank's rules, so confirm the period in writing with them and align your archiving to the longer of that period and the National Credit Act period.

Ready to digitise your financial institution?

Talk to our team about your roadmap and discover scalable digital banking solutions tailored to banks, fintechs and microfinance institutions.

Request a Demo →

Handle mandate exceptions

Most of the operational costs in Authenticated Collections come from exceptions, and many of these are mishandled because staff treat a payment failure and a mandate failure as the same problem. Each requires a different next step, so teams need to distinguish between them using the terminology found in their bank and provider files.

When a collection is authenticated, it is eligible for submission, provided the returned parameters match the agreement. The next permitted action is to submit the collection within the mandate terms. If the outcome is rejected by the payer, the collection is not eligible for submission. Staff should determine whether the customer disputes the terms or the contract and contact the customer before attempting any resubmission.

If the outcome is no response (NRSP), the collection is not eligible. Staff should verify the cellphone number held by the customer’s bank and either re-initiate the process or register a Registered Mandate within 10 calendar days. In the case of a validation failure, the collection is also ineligible. Staff must identify the field-level mismatch against the registered record, correct the data, and then resubmit or amend the mandate as appropriate.

An unpaid collection due to insufficient funds is different because the collection remains eligible, subject to the applicable terms. Staff should check the tracking window and the collection date against the salary date, then track the payment, re-present it within the permitted terms, or amend the date where allowed. Finally, if a mandate is suspended, the collection is not eligible. Staff must establish when and why the customer suspended it and resolve the underlying service issue so the customer can lift the suspension.

No customer response

An unanswered request is the most common outcome and the least informative. The usual cause is an outdated cellphone number at the bank, so the first call is to the customer. Cap automatic retries, because every attempt carries a fee.

Registered Mandate is the fallback, and its availability depends on your arrangement. Under FirstRand's terms a user may only request one after the DebiCheck mandate request produced a no-response code, and only within 10 calendar days of receiving it. Registered Mandate replaced the older Registered Mandate Service on 12 May 2025 and now clears in the evening window, so check what your sponsoring bank supports before you design the fallback path.

Rejected or mismatched

A customer rejection is a relationship event. Someone understood the request and said no, which means the terms or the sales conversation needs attention before you try again. Resubmitting an identical request to a customer who declined it wastes money and erodes trust.

A validation mismatch is a data event. The amount sits above the authenticated instalment or the date falls outside approved terms. Another mismatch is a mandate reference on the collection that differs from the registered reference. Kwik's troubleshooting guide is blunt about the remedy: fix the data or amend the DebiCheck mandate, because retrying an unchanged mismatching collection will fail every time. Where the change touches frequency or the contract reference, you need a fresh agreement and a new request.

Collection unsuccessful

Insufficient funds against a valid DebiCheck mandate is not a mandate problem, and routing it to your mandate queue clogs the queue. The tools for it are tracking and date alignment. Since DebiCheck already presents first in the early morning window after salary credits, repeated failures point at the collection date.

Reconciliation should close the loop daily so that outcome codes match back to instalments and unpaid items stay distinguishable from tracked and settled ones. Escalate to the mandate team only when the return code indicates suspension or cancellation, and also when it indicates validation failure. Weaver Fintech reported that it responded to industry changes by migrating 95% of collections onto DebiCheck. It described the result as "improving reliability and predictability of cash flows," which is the payoff for keeping these two queues apart.

Compare collection options

The three payment streams differ in where the mandate is stored and who validates it, and these two factors determine how each process works. The comparison follows the structure published by the Payments Association of South Africa.

With DebiCheck, the customer authenticates the mandate through their bank, which stores the registered terms and validates each collection against them. Collections are processed in the early-morning window with first priority, and tracking is available for up to 10 days. Disputes can be raised within 60 calendar days, with the authenticated record serving as supporting evidence. Operationally, you rely on the bank-held authenticated terms alongside your own records.

With a Registered Mandate, the customer does not authenticate the mandate directly; instead, the bank notifies them of its registration. The mandate is stored at the customer’s bank, and collections are validated against the registered parameters. Processing takes place in the evening at 19:00 SAST, and tracking is available for up to 10 days, from noon to midnight. Disputes can also be raised within 60 days. Your supporting evidence consists of the registered terms and your own records.

With a standard EFT debit order, the customer acknowledges the mandate through the service provider, which stores the mandate. The bank does not validate each collection against registered parameters, and tracking is not available. Processing takes place late in the evening, after Registered Mandate processing. Disputes can be raised within 60 days, but you must produce the mandate yourself. This means your own records are the primary operational evidence.

The important point in the dispute comparison is that the 60-day window is the same across all three streams. The difference lies in the strength of the evidence available when a dispute arises. For lenders experiencing high dispute volumes, that is a key reason to consider DebiCheck mandates.

Implementation questions

Put these to your sponsoring bank and technology provider before you sign, and get the answers in writing.

  • Connectivity model, supported transaction types, and which DebiCheck authentication channels reach your customer base

  • Certification and test coverage, including negative paths for rejection and validation failure

  • Response handling: which field confirms authentication rather than transmission, and how mandate records and amendments are exposed

  • Reconciliation files, support hours, failover arrangements, reporting, and the audit trail available to your compliance team

Doocat builds core and digital banking software for lenders and microfinance institutions, with loan servicing and integrations into national payment systems. If you're designing or reviewing how your systems carry a DebiCheck mandate end to end, book a call with our team.

Ready to digitise your financial institution?

Talk to our team about your roadmap and discover scalable digital banking solutions tailored to banks, fintechs and microfinance institutions.

Request a Demo →

Use a unique request identifier for each mandate and store it with the submission status. Your system should reject a second attempt when the original request remains unresolved, unless the provider confirms that the first message failed before acceptance. This control prevents duplicate authentication prompts and conflicting mandate references.

Keep the affected records in a pending reconciliation queue and avoid treating missing data as a failed collection. Compare the provider’s eventual file with your submission log, then record the final response, settlement result, and processing date. Set an escalation deadline with your sponsoring bank before production launch.

Staff can update internal records, but they shouldn’t overwrite the authenticated terms without an approved amendment process. Preserve the original values, record who made each change, and route regulated changes through the required re-authentication or new-mandate path. This keeps the audit trail tied to the customer’s approved agreement.

Test successful authentication and each expected exception with controlled accounts or the bank’s certification environment. Include duplicate submissions, delayed responses, invalid account details, amount mismatches, amendments, suspensions, and reconciliation failures. Confirm that each response changes the correct internal status and that support staff can retrieve the related evidence.

Ask Doocat to review the workflow when mandate records, loan servicing, reconciliation, or exception queues sit in separate systems. The review should map data ownership, response handling, and evidence retention from capture through settlement. You can book a call with the client to assess those integration points before finalising the design.

Schedule a Meeting

Book a time that works best for you

You Might Also Like

Discover more insights and articles

Two diverse professionals engaged in a friendly discussion over a tablet in a bright, modern office with large windows and blurred coworkers.

Murabaha Financing: Contracts and Examples for African Banks

This article walks through how murabaha financing becomes a working bank product: the transaction sequence and the controls your core system has to enforce. It is written for the teams who have to build the thing and then defend it in an audit.

A mid-aged manager reviews documents at a warm wood desk in a sunlit office, with a monitor displaying analytics in the background.

SACCO Management System: A Buyer’s Guide for Kenyan SACCOs

This article walks through how a Kenyan savings and credit cooperative can define what it actually needs from new software and check vendor claims against evidence before it plans a migration that doesn't break member balances. It ends with a checklist you can score vendors against before any price talk begins.

Close-up of hands holding a smartphone displaying a banking app, set in a cozy home office with blurred background elements.

Mobile Money Interoperability in Ghana: How GhIPSS MMI Works

This article maps the four transfer flows supported by Ghana's national mobile money interoperability platform and shows who owns each step of them. It covers transaction direction and the questions to settle before a new connected channel goes live.

A business manager discusses loan strategies in a bright office, holding a tablet displaying a banking dashboard, with employees working nearby.

How African MFIs Can Reduce Fraud in Cash Loan Collections

Cash collection fraud shrinks when every repayment carries a unique, device-generated receipt reference tied to one borrower and one loan, and when the officer who collects cash never posts or reconciles it. Add daily handover matching and an independent borrower complaint channel, and most leakage becomes visible within 24 hours instead of months.