The DebiCheck Mandate Lifecycle Explained
A DebiCheck mandate is not a once-off event — it is a living record that moves through defined stages from the moment it is initiated until it is finally cancelled. Because the consumer's bank stores an electronic copy of the mandate and verifies every collection against it, keeping the mandate's state accurate matters for every collection you submit.
This page walks through each stage of the lifecycle and what triggers the moves between them.
Stage 1: Initiation
The service provider (or a payments provider like Kwik acting through a sponsoring bank) submits a mandate initiation request containing the debit order terms: payer details, instalment amount, any maximum collection amount, frequency, collection day and the collecting party's details.
The request is routed to the consumer's bank, which sends the consumer an authentication request. The mandate is now pending authentication.
Stage 2: Authentication
The consumer approves or rejects the request through their bank's channels — app, USSD, internet banking, ATM, card-and-PIN device or in branch. Depending on the transaction type, they have from about 120 seconds (TT1) up to the end of the next business day (TT2) to respond.
Three outcomes are possible:
- Authenticated — the bank stores the mandate in its mandate register; collections may begin.
- Rejected — the consumer declined; the mandate cannot be used.
- Expired — no response in time; the request can be re-initiated.
See mandate authentication for channel details.
Stage 3: Active collections
While the mandate is authenticated, the service provider submits collections against it each cycle. The consumer's bank verifies every collection against the stored mandate — matching collections are processed as first priority in the early morning window; non-matching collections are rejected. See collections, tracking and retries.
Stage 4: Amendments
Contracts change: instalments increase at an annual escalation, collection days move to match a new salary date, or account details change. Amendments are submitted as mandate amendment requests. Depending on what changes and the rules of the consumer's bank, an amendment may:
- Be registered without new consumer action (for example, a change already provided for in the mandate), or
- Require the consumer to re-authenticate the amended terms.
Until an amendment is accepted, collections must still match the existing mandate terms. Changes to amounts and frequencies are the most common amendments.
Stage 5: Suspension
A consumer can suspend a DebiCheck mandate at their bank. Suspension blocks all future collections against the mandate, and the service provider is notified at the time of suspension — a significant advantage over ordinary debit orders, where you often only learn of a problem when a collection bounces.
Two points are important:
- Suspension does not cancel the underlying contract. The consumer must still cancel the agreement with the service provider, and the debt continues to accrue in the meantime.
- The service provider can engage the consumer to resolve the issue and have the suspension lifted.
Stage 6: Cancellation
Cancellation ends the mandate permanently. It can be initiated by the service provider (for example when a contract ends or is settled) or by the consumer through their bank. Once cancelled, no further collections can be processed against the mandate; a new contract would need a new mandate.
Lifecycle statuses at a glance
| Status | Meaning | Collections allowed? |
|---|---|---|
| Pending authentication | Awaiting the consumer's response | No |
| Authenticated | Approved and stored at the bank | Yes |
| Rejected | Consumer declined the request | No |
| Expired | Authentication window lapsed | No — re-initiate |
| Suspended | Consumer blocked collections at their bank | No — until lifted |
| Cancelled | Mandate permanently ended | No |
For how these statuses and their reason codes reach your systems, see statuses and reason codes.
Related topics
Mandate Authentication
How payers approve DebiCheck mandates via banking apps, USSD, ATMs and card-and-PIN devices, and what happens when authentication is rejected or expires.
Statuses and Reason Codes
A guide to DebiCheck mandate and collection statuses and the reason codes banks return, including common decline reasons and what to do about them.