Amplifin Chat Widget
Talk to us

DebiCheck Payment Stream

An advanced Debit Order solution with consumer-authenticated mandates, early-morning collection processing and multiple presentments through
credit tracking.

Benefits of DebiCheck

Higher Collection Success Rates:

DebiCheck debit orders are processed early in the morning immediately after salary credits, which reduces the chances of insufficient funds responses being received.

Credit Tracking:

DebiCheck debit orders that have failed due to insufficient funds, can be automatically represented for up to 10 days until there are sufficient funds to successfully process the debit order or till the number of days selected lapse.

Real-Time Responses and Settlement:

The DebiCheck payment stream makes use of real-time response processing, meaning that the User is always aware of the state of their collections on a real-time basis, whether the debit order has been successful, is in tracking or failed (with a specific reason for failure). Coupled to this is real-time settlement, meaning successfully collected funds are settled as and when the successful responses are received.

Reduced Disputability:

Due to the Payer authenticating the mandate prior to collection being presented for processing against their bank account, if the collections presented align with the mandate obtained from the Payer, then the Payer cannot successfully dispute the collection, and a reversal of funds will not take place.

How DebiCheck Works

STEP 01

Agreement with Consumer

#

An agreement is concluded between the consumer and the Amplifin client, and the payment terms, which include the amount, payment date and term, are agreed upon in the form of a paper, voice or electronic mandate.

STEP 02

Mandate Creation

#

The Amplifin client creates a DebiCheck mandate based on the agreed payment terms.

STEP 03

Authentication

#

The consumer receives a request from their bank to authenticate the mandate via a specific channel (e.g. banking app, USSD, ATM or Card & PIN).

STEP 04

Confirmation

#

Once authenticated, the mandate is confirmed and stored securely in the bank’s mandate register. If the collection submitted aligns with the mandate authenticated by the debtor then the successful collections cannot be disputed and subsequently reversed.

STEP 05

Debit Order Processing

#

On the agreed date Amplifin will extract and submit the debit order for processing to the debtor bank.

STEP 06

Near Real-Time Responses

#

Response codes are received almost instantly, ensuring the Amplifin client stays continuously informed about the status of their collections.

STEP 07

Settlement

#

The proceeds of all successful DebiCheck debit orders collected in the early morning processing window are settled into the bank account of the Amplifin client on the same day.

How DebiCheck Works

STEP 01

Agreement with Consumer

#

An agreement is concluded between the consumer and the Amplifin client, and the payment terms, which include the amount, payment date and term, are agreed upon in the form of a paper, voice or electronic mandate.

STEP 02

Mandate Creation

#

The Amplifin client creates a DebiCheck mandate based on the agreed payment terms.

STEP 03

Authentication

#

The consumer receives a request from their bank to authenticate the mandate via a specific channel (e.g. banking app, USSD, ATM or Card & PIN).

STEP 04

Confirmation

#

Once authenticated, the mandate is confirmed and stored securely in the bank’s mandate register. If the collection submitted aligns with the mandate authenticated by the debtor then the successful collections cannot be disputed and subsequently reversed.

STEP 05

Debit Order Processing

#

On the agreed date Amplifin will extract and submit the debit order for processing to the debtor bank.

STEP 06

Near Real-Time Responses

#

Response codes are received almost instantly, ensuring the Amplifin client stays continuously informed about the status of their collections.

STEP 07

Settlement

#

The proceeds of all successful DebiCheck debit orders collected in the early morning processing window are settled into the bank account of the Amplifin client on the same day.

DebiCheck Authentication Mechanisms

We Support all DebiCheck Transaction Types

TT1 Real-Time

A consumer is sent an authentication request to their cellphone that they need to respond to within 120 seconds. This Authentication request comes via a USSD Push on the cellphone (consumer cellphone number needs to be the same as registered with the bank) or via their mobile banking app (bank dependent).

TT1 Real-time is typically used in a non-face-to-face environment, but the authentication can be facilitated in a face-to-face environment as well.

TT1 Delayed

The consumer must respond to the Authentication Request before 22:30 on the same day that the request was sent, using one of the Authentication Channels available at their bank. 

These Authentication Channels include ATM, Online Banking, Mobile Banking App, the customer’s Bank Branch or Call Centre.

TT1 Delayed is typically used in a non-face-to-face environment, but the authentication can be facilitated in a face-to-face environment as well.

TT2 Batch

TT2 Authentication Requests are processed in batch by the Debtor Bank, allowing delayed mandate authentication.

The consumer has until 21:00, two days from and including the day that the authentication request was received by the consumer, failing which will result in mandate authentication failure.

Authentication channels: ATM, Online Banking, Mobile Banking Application, Debtor Bank Branch visit, or Debtor Bank Call Centre.

TT2 is a non-face-to-face Mandate Authentication Transaction Type – meaning authentication requests are also delayed.

TT3 Card & PIN

Can only be performed when the customer is physically present to use their bank card and PIN on the Amplifin Card Payment Device. Here the bank card and PIN, which should only be in the possession of the account holder, is used to authenticate the DebiCheck mandate.

The Authentication Request and Response is performed in real-time, and TT3 Authentication can occur daily between 00h30 – 23h30. 

Authentication Channel: Bank card and PIN on the Amplifin Card Payment Device.

TT3 is a real-time, face-to-face Mandate Authentication Transaction Type.

How would you like to access DebiCheck?

ALLPS-i

Amplifin’s proprietary platform, ALLPS-i, is an advanced, web-based solution that streamlines payment and collection management. With robust features, ALLPS-i is designed to optimise your payment and collection processes and ensure seamless integration with your existing operations.

Learn more

Integrated Solutions

We understand that every business has unique needs, which is why we offer flexible integration options. From file-based solutions to real-time web services, we provide smooth integration with a variety of debtor management systems (DMS) and admin platforms.

Learn More

DebiCheck FAQ's

DebiCheck fundamentals

What is DebiCheck, and how does it differ from other debit orders?

  • DebiCheck is an authenticated debit order payment stream. The Payer authenticates the debit order mandate with their bank, and the bank stores it in its mandate register. The bank will only process collections against DebiCheck mandates that have been authenticated.

Why was DebiCheck introduced, and what industry problems does it solve?

  • DebiCheck was introduced as part of the modernisation of South Africa’s debit order environment and to replace legacy AEDO and NAEDO payment streams. The goal was to reduce two types of abuse. The first is unauthorised collections by providers that debit accounts without proper permissions. The second is unfair disputes where payers reverse valid debit orders. With DebiCheck, collections that match an authenticated mandate cannot be successfully disputed and refunded, while collections that fall outside the authenticated mandate parameters can be disputed by payers and a subsequent reversal of successfully collected funds can occur.

How does DebiCheck fit into the South African debit order environment alongside EFT Debits and Registered Mandate (RM) Debits?

  • DebiCheck, RM, and EFT Debits are all debit order payment streams in the National Payments System. Businesses choose which stream to use for a given product or Payer profile. EFT Debits are non-authenticated, processed in the evening, and are generally used where Payer behaviour is low risk and disputes are less likely. RM is a non-authenticated debit order, however the mandate details stored in the banks mandate register, collections are processed in the early evening (before EFT Debit Orders), and RM supports credit tracking. DebiCheck is Payer authenticated, collections are presented in the early morning, close to salary credits meaning that the likelihood of successful collections are greater.

What is a DebiCheck mandate, and what information does it contain?

  • In this context, a DebiCheck mandate is the electronic record of a mandate that has been authenticated by a Payer, the mandate is stored in the Payer’s bank mandate register. The mandate typically includes the Payer’s details, bank account information, mandate type, collection day, instalment amount, any maximum collection amount, collection frequency, whether credit tracking is permitted, and whether date changes are allowed. 

How does the authentication process work, and which authentication types (TT1, TT2, TT3) are available?

  • Authentication is the process by which the payer approves the mandate at their bank before DebiCheck debit orders can be presented for collection. The bank sends or makes available an authentication request, and the payer confirms or declines it through the channels supported by their bank. DebiCheck has three authentication types: TT1 (real-time and delayed) for typically for non-face-to-face authentication, TT2 (batch or offline) for delayed non-face-to-face authentication, and TT3 (card and PIN) for face-to-face authentication on a card payment device. Each type has specific timing windows and supported channels, such as USSD, mobile app, internet banking, ATM, branch, call centre, or Card and PIN on a card device.

Does the authentication channel affect how collections are processed?

  • No. Once the mandate has been authenticated, all DebiCheck collections are processed according to the same rules, regardless of whether the payer authenticated using TT1, TT2, or TT3. The presentment window, tracking behaviour, suspension rules, and disputability rules are the same.

What mandate types exist in DebiCheck (fixed, variable, usage-based), and when should each be used?

  • A fixed mandate is used when the instalment amount remains constant for the term of the agreement; for example, a short-term credit product with a fixed monthly repayment. The only time the value will change is when an arrears collection is presented, and additional fees have been levied by the business, for example, interest.
  • A variable mandate is used where the amount can change based on known factors, such as an interest rate or annual premium adjustment, for example, repo-linked home loans or insurance premiums.
  • A usage-based mandate is used where the amount depends on actual usage, for example, utilities, cell phone contracts, or credit cards, and a maximum collection amount is authenticated for these variable amounts. 

Which mandate parameters determine disputability (amount, date, maximum value, frequency, arrears, etc.)?

  • Disputability depends on whether the collection aligns with the parameters stored in the authenticated mandate register. Key parameters include the authenticated collection day, the collection amount, the maximum collection amount (where applicable), the mandate type (variable and usage-based mandates), and whether the collection is an arrears collection attempt. Collections presented with a value greater than the authorised collection value are disputable, except where the rules for that variable mandate type permit. 
  • All arrears collections are disputable, even if within the mandated collection value or authenticated collection date. 

Can a business adjust the collection date, and how does the Date Adjustment Indicator affect disputability at 6-day vs 7-day banks?

  • A business can move the presentment date if the payer allowed date changes during authentication. This allows certain movements without affecting disputability, such as moving a Sunday or public-holiday collection to a business day before the weekend or public holiday. For 6-day processing banks, if the collection is scheduled for a day or date when the bank doesn’t process DebiCheck collections, the collection can be presented the next business day, and the collection will not be disputable. For 7-day processing banks, presenting after the authenticated collection day, will make the successful collection disputable if the Action Date no longer aligns with the authenticated collection day. 

How does early morning processing work, and why does timing matter for successful collections?

  • DebiCheck collections are processed in the early morning after banks have completed incoming credit postings, such as salaries and wages. All participating banks prioritise DebiCheck over other debit-order payment streams. Aligning the authenticated collection day with the Payer’s salary cycle improves the probability of successful collections.

What is credit tracking, and how do full tracking and limited tracking banks differ?

  • A feature that re-presents a failed collection (due to insufficient funds) automatically for a defined number of tracking days. Banks implement either full or limited tracking depending on their processing systems.

  • Full-tracking banks run tracking in near real time throughout the day, so collections can be successfully proccessed if there are sufficient funds  credited to the Payers bank account during the course of the day. 

  • Limited-tracking banks have a second DebiCheck debit order processing window which is typically early afternoon, on a best-effort basis, meaning that collections can be successfully proccessed if there are sufficient funds  credited to the Payers bank account during the course of the day. 
  • Tracking only runs on days when the bank processes transactions.

How many days can a DebiCheck collection track for, and what events stop tracking?

  • DebiCheck allows tracking for up to ten days after the original failed attempt (due to insufficient funds), starting from the Presentment Date. Tracking stops when a collection is successful, or when the selected tracking days have lapsed, or when the mandate is suspended or cancelled.

What are typical unpaid reasons for DebiCheck transactions?

  • Common unpaid reasons include insufficient funds, an account that is closed,  or frozen. Unpaid items can also occur where the mandate has been suspended at the bank or where the account is subject to legal restrictions such as not being FICA compliant. The unpaid reason code returned by the bank indicates the specific cause.

When can a DebiCheck collection be legitimately disputed and subsequently reversed?

  • A DebiCheck collection may be disputed when it does not meet the parameters approved in the authenticated mandate. This includes collection dates that fall outside the permitted date-movement rules, amounts that exceed the authorised collection value or maximum value for that mandate type, and all arrears collections (collections re-presented after an original failure). 

What happens when a payer suspends a mandate, and how does suspension differ from cancellation?

  • When a payer suspends a DebiCheck mandate at their bank, future collections under that mandate will not be processed. The business will receive a suspension notification so it can engage the Payer. Suspension affects collections only; it does not cancel the underlying commercial agreement between the Payer and the business. Any cancellation of the contract or changes to the payment terms must be handled directly between the business and its payer.

How do banks handle disputes for authenticated vs non-authenticated debit orders?

  • For authenticated DebiCheck mandates, the bank maintains an electronic record of what the consumer agreed to, including the amount and date parameters. This gives the bank greater certainty when assessing a dispute, and not all DebiCheck disputes will result in a reversal of successfully collected funds. For non-authenticated debit orders, such as EFT Debits or RM, the payer has not authenticated the mandate, therefore the bank will entertain the dispute raised by the Payer and a reversal of the successfully collected funds will occur.

What information does a business need to collect from customers to create a compliant DebiCheck mandate?

  • At a minimum, a business needs the payer’s identity details, correct bank account details, and a signed paper, voice or electronic mandate where the payer gives consent for collections to be processed against their bank account. For the DebiCheck mandate itself, the business must define the mandate type, collection day, instalment value, maximum collection value where applicable, tracking days, and whether date changes are allowed. The mandate should also reference the underlying agreement, specify the frequency or term, and align with the actual product structure to avoid misalignment between the agreement and mandate. All of this must be captured accurately when the mandate is created and before authentication.

Presentment Date

  • The date on which a DebiCheck collection is scheduled to be presented at the paying bank. The Presentment Date must align with the authenticated collection day in the mandate register, unless the Date Adjustment Indicator permits movements to avoid collections being disputed and subsequently reversed.

Allow Date Change / Date Adjustment Indicator

  • A mandate parameter indicating whether the presentment date or day may be moved under certain conditions. If set to ‘Yes’, limited adjustments may occur without making the transaction disputable.

Arrears Collection

  • A collection that has previously failed and is rescheduled (represented) for collection. All arrears (represented) DebiCheck collections are disputable, even if the value or date is within the mandate’s parameters.

Authentication

  • The payer’s approval of the DebiCheck mandate via their bank is required before collections can begin. A record of the Authentication is stored in the bank’s mandate register and used to validate future collections.

DebiCheck Authenticated Collection Day

  • The day of the month or week that the payer approves as the once off or recurring collection day during authentication. This forms a core part of the mandate and determines disputability if changed.

Batch Authentication (TT2)

  • A non-real-time authentication method in which the payer can approve an authentication request, the Payer has two days to accept or decline the mandate before the mandate request will expire. Used when immediate authentication is not required.

Card and PIN Authentication (TT3)

  • A face-to-face authentication method where the payer authenticates the mandate using their card and PIN on a card payment device.

Collection Amount

  • The Rand value to be collected under the mandate. For Fixed mandates, this amount remains constant (unless arrears collection). For Variable and Usage-Based mandates, rules apply to change the maximum amounts.

Collection Cycle / Frequency

  • The agreed interval at which collections occur (e.g., monthly, weekly, every two weeks, last day of the month). Frequency must match the commercial agreement.

Credit Tracking (Tracking)

  • A feature that automatically re-presents a failed collection (due to insufficient funds) for a defined number of tracking days. Banks implement either full or limited tracking depending on their processing systems.

Early Morning Processing

  • The priority processing window is where DebiCheck collections are processed after salary credits have occurred. Timing improves the likelihood of successful collections.

Fixed Mandate

  • A mandate with a fixed instalment value for the full term. Any attempt to debit a value higher than the fixed instalment is disputable. Lower values are permitted, and a dispute will not be successful if the value collected is less than the original value authenticated.

Full Credit Tracking

  • Bank behaviour where tracking runs throughout the processing day, in near real time. If the payer receives sufficient funds during the day, the collection can be processed immediately.

Limited Credit Tracking

  • A bank behaviour where one additional DebiCheck processing window occurs later in the day (typically around mid-afternoon) on a best-effort basis.

DebiCheck Mandate

  • The electronic record stored by the payer’s bank that defines the parameters under which DebiCheck collections may occur. It is created by the business and authenticated by the payer.

Mandate Amendment

  • A change to mandate parameters after authentication. Whether re-authentication is required depends on the parameters being amended.

Mandate Register

  • The paying bank’s internal record of all authenticated mandates. The bank validates each incoming collection against this register before processing.

Maximum Collection Amount

  • The highest Rand value that may be collected under a Fixed, Variable or Usage-Based mandate. 

Non-Authenticated Collections

  • Collections such as EFT Debits or RM Debits, where the payer does not authenticate the mandate with their bank. Successful collections can be disputed and subsequently reversed.

Real-Time Authentication (TT1)

  • An authentication request that the payer approves immediately via channels such as a mobile banking app or USSD.

Re-Authentication

  • A new authentication is required when key parameters of the mandate change beyond what the current mandate type allows (e.g., collection value, frequency).

Registered Mandate (RM) Debit Order

  • A non-authenticated debit order stored in the bank’s mandate register and processed in the early evening window, which allows credit tracking. All RM collections are disputable.

DebiCheck Mandate Suspension

  • A payer-initiated stop was placed on a DebiCheck mandate at their bank. Suspended mandates block future collections until a new mandate authentication is obtained along with a new paper, voice or electronic mandate.

Credit Tracking Days

  • The number of days (up to ten) during which a failed collection (due to insufficient funds) will automatically be re-presented through credit tracking.

Usage-Based Mandate

  • A mandate used for variable consumption billing (e.g., utilities, telecoms). Collections may vary monthly within the maximum collection value approved during authentication.

Variable Mandate

  • A mandate where instalments may change based on known or contractually defined  mandate value variables. 

6-Day Bank / 7-Day Bank

  • A 6-day bank processes DebiCheck collections on six days per week. A 7-day bank processes collections every day.

Ready to embrace DebiCheck?

Let us help you sign up for the DebiCheck Payment Stream today.

Contact us