Electrum Blog

Your DebiCheck Offering Needs a Regulatory Buffer

Written by Sam Ancer | Jun 24, 2026 9:21:37 AM

If Electronic Funds Transfer (EFT) debit orders were sunset, can your systems handle tripling your DebiCheck volume? As the South African government modernises the payments landscape, mature systems like EFT cannot continue without massive overhauls. Navigating these unique local demands requires a partner with on-soil expertise built to global standards.

Regulatory impact on collections

The South African Reserve Bank (SARB) has accelerated work on its Vision 2030+ initiative, prioritising financial inclusion, transparency, and trust. In the collections space, this modernisation has triggered a rapid evolution over the last eight years.

Timeline of collections regulation

  • 2019: DebiCheck is launched

Replacing Early Debit Order (EDO) systems to solve fraudulent collections and dispute abuse by requiring upfront customer verification.

  • 2021: EDO systems sunset

Authenticated Early Debit Order (AEDO) and Non-Authenticated Early Debit Order (NAEDO) systems are officially discontinued, and those collection streams must migrate to DebiCheck.

  • 2022: Introduction of Registered Mandate Services (RMS)

DebiCheck adoption hits a roadblock. Due to low customer adoption and a low 59% mandate authentication success rate, the SARB introduces the Registered Mandate Service (RMS) as a temporary safety net, allowing disputable collections against unverified mandates.

  • 2025: The shift to Registered Mandates (RM)

RMS is sunset and replaced by the Registered Mandate (RM) payment scheme. While functioning similarly to RMS, RM optimises success rates by shifting the collection window from the morning to the early evening.

  • 2026: EFT collection dispute window changes

Automatic refunds for EFT collection disputes are extended from 40 days to 60 days, while removing the ability to dispute collections outside of that window.

What does regulatory pressure mean for DebiCheck?

Over an eight-year period, three collection systems (DebiCheck, RMS, and RM) have been created, and three (AEDO, NAEDO, and RMS) have been discontinued. This, in conjunction with the SARB's 50% acquisition of PayInc (formerly BankservAfrica), highlights the growing legislative activity within the South African payments landscape.

At first glance, extending the EFT collection dispute window appears to be an effort to sustain the legacy scheme. In reality, it’s an intentional push towards DebiCheck.

While capping dispute investigations at 60 days relieves operational strain on banks, extending the overall dispute window by 50% raises a greater concern for your corporate clients. It traps their cash flow in limbo, forcing them to wait longer to guarantee their revenue.

For businesses, especially large corporates, liquidity is oxygen; this delay creates greater urgency to adopt DebiCheck and eliminate their dispute risk entirely.

Finally, the SARB is looking to leverage ISO 20022 and real-time payments to modernise the economy, making a legacy, non-real-time scheme like EFT unsustainable in the long term.

While EFT’s massive volume, with a total of 437 million debit pulls in 2024, means it is too big to be sunset right now, treating it as a permanent fixture is a high-risk strategy. With DebiCheck demand growing, you should not wait for the official sunset announcement to build a resilient architecture.

Why is DebiCheck so challenging?

To fulfil the need of protecting retail customers and creditors, AC was built with stringent requirements:

  • Mandate, authentication, storage, and management for creditor and debtor banks
  • Multiple transaction types
  • Batch and single transaction processing

Timelines to complete all this complexity were tight, as any bank with an EDO system needed to have their DebiCheck scheme ready within four years to ensure their clients could still benefit from early collection windows. As a result, many banks worked with international vendors who retrofitted existing solutions to meet the need. This often led to DebiCheck solutions being directly built into the core infrastructure.

However, as regulations changed and volumes grew, banks needed to keep up with patchwork fixes. Creating more fragility and strain on the ledger.

Coupling your DebiCheck solution with your legacy core systems can cause your databases to become bloated with trillions of transactions over time. This creates a highly fragile system that can operate day-to-day, but when volumes spike during salary cycles, your systems are pushed to their limit and may break without direct intervention.

This system strain forces you to invest significant resources, like investing developer time to:

  • Manually de-bulk large batch files to prevent system crashes.
  • Manage severe concurrency contention issues when processing windows overlap.
  • Hunt down missing responses across misaligned messaging queues.

This is a massive misallocation of overheads and a devastating opportunity cost. Every hour a senior developer spends babysitting a legacy system is an hour lost from product differentiation, feature development, and revenue generation.

How to ensure your DebiCheck solution works today and is ready for tomorrow

At Electrum, we are building our cloud-native, ISO 20022-compliant DebiCheck solution from the ground up. Designed for the rules, not just adapting to them. Giving you the perfect foundation to innovate and differentiate your product line, while still freeing you from the stress of salary cycles.

Built correctly: compliance shouldn’t touch the ledger

Mandate management is notoriously data-rich and highly complex, routinely straining core banking systems during peak collection cycles. However, the reality is that your legacy core does not need to understand or track constantly shifting mandate states. It should focus only on what it needs to do: ledger balances and financial postings.

Electrum is ready to help you overcome your analysis paralysis by owning the complexity of DebiCheck for you. We completely insulate your core from the stress of salary day by deploying our decoupled API layer to create a specialised orchestration buffer. The API layer handles the complex ISO 20022 semantics and validation logic, passing only clean, pre-validated instructions to your ledger.

Our proximity to institutions such as PayInc and the SARB means we can start implementing changes to our solutions as soon as new regulations are issued, without you having to pick up the phone.

Flexibility in the face of regulations means no-dev configurations

Regulatory shifts will not wait for your internal IT sprint cycles. In 2026, a modern bank cannot afford to wait for a six-month global vendor code deployment just to change a cut-off time or implement an urgent scheme update.

Electrum DebiCheck gives your operations team total control with an intuitive user interface that lets them immediately alter specific DebiCheck parameters with no development required. Ensuring you can adapt to new rules rapidly, freeing you from rigid, hard-coded vendor dependencies ten years down the line.

Electrum is a local partner building to a global standard

Electrum is engineering a purpose-built DebiCheck solution designed to absorb the complexity of modern collections, helping you finally free your engineering talent to innovate, and your core ledger overcome the strain of pay day spikes.