FAQ Section
DebiCheck

Which Banks Support DebiCheck?

 

Most major South African banks participate in DebiCheck, including Absa, Capitec, FNB, Nedbank and Standard Bank. See how participation affects mandates.

Most major South African banks participate in DebiCheck, including Absa, Capitec, FNB, Nedbank and Standard Bank, along with a number of other banks. However, not every bank in South Africa participates — some smaller banks and niche institutions do not — and not every service provider chooses to collect via DebiCheck.

Participation matters in both directions: a consumer can only authenticate a DebiCheck mandate if their bank participates, and a business can only collect via DebiCheck from payers whose banks are on the system.

Which major banks participate in DebiCheck?

Participating banks include the major retail banks:

  • Absa
  • Capitec
  • FNB (First National Bank)
  • Nedbank
  • Standard Bank
  • Plus several other participating banks

Bank participation can change over time, so for a current list consumers and businesses can check www.debicheck.co.za or confirm with the specific bank.

Does every bank offer the same authentication channels?

No — the approval channels vary per bank. One bank may lean on app push notifications and USSD, another may emphasise ATM or internet banking approval. Common channels across the industry include:

  • Banking app
  • USSD
  • Internet banking
  • Cellphone banking
  • ATM
  • Card and PIN on a device
  • In branch

Whatever the channel mix, every participating bank supports the core promise: the consumer approves the mandate, the bank stores it, and collections are verified against it. See mandate authentication for how each channel works.

What if the payer's bank does not participate?

If a payer banks with a non-participating institution, a DebiCheck mandate cannot be initiated against that account. Businesses then have alternatives on the same rails:

  • Registered Mandates (RM/RMS) — the related non-authenticated route, where the mandate is registered with the bank without consumer authentication. See what is a Registered Mandate.
  • EFT debit orders — the traditional collection stream. See EFT debit orders.

A well-designed collections strategy routes each payer to the strongest available option. Kwik does this automatically, using DebiCheck where the payer's bank participates and falling back to the appropriate alternative where it does not.

Do all service providers use DebiCheck?

No. DebiCheck is used at the discretion of the collecting business, and many still collect via EFT debit orders or Registered Mandates. As a consumer, this means not every new contract will trigger a DebiCheck authentication request — the absence of one does not necessarily mean anything is wrong. As a business, offering DebiCheck signals to customers that their bank will police your collections, which builds trust.

What should businesses check before going live?

  • Payer bank coverage: what share of your payer base banks with participating banks? That determines how much of your book can move to DebiCheck.
  • Channel behaviour per bank: authentication user experience differs by bank; your sign-up scripts and customer messaging should reflect what each payer will actually see.
  • Transaction type support: confirm that the transaction types you plan to use (TT1, TT2, TT3) fit your sign-up channels.
  • Fallback strategy: decide upfront how you will collect from payers whose banks do not participate.
Copyright © 2026 Kwik Payments