Rails
Collection Mandate
A collection mandate is the customer's permission for you to collect money from their bank account under stated terms. In South African setups, the trouble usually starts when the signed wording, the debit instruction, and the internal handover are treated as the same thing. This note separates those parts so teams can see what must be recorded and what must be checked before any debit run.
Signed consent before the first debit
This Collection Mandate note explains what a collection mandate does in South African payment setups and where teams usually trip over wording or proof. Use it when you need the difference between customer permission, debit rules, and internal process written plainly.
Begin with the collection rail you use, because a standard debit order, DebiCheck collection, and card recurring debit do not rely on the same proof. Amount rules, date rules, and notice wording matter more than polished legal language when a dispute lands on the finance desk. Teams in Johannesburg, Durban, Cape Town, and smaller towns often need one version for digital signup and another for in-person capture at a counter or branch.
Store the original acceptance point, not just the customer profile. That can mean a signed paper form, a recorded voice acceptance where permitted, or a digital acceptance log with date, time, IP and the exact mandate text shown. When a debit is queried later, weak recordkeeping is usually the first gap exposed.
What the mandate must state
The wording should name who is collecting, from which account type, on what date pattern, and for what kind of obligation. Variable amounts need an agreed mechanism or prior notice, otherwise staff may assume the mandate covers changes it does not. Internal process should also say who may amend bank details, pause collections, or cancel a run.
Use this note beside your debit-order procedure, dispute handling note, and customer onboarding copy before changing forms across channels. If a collection fails or is challenged, compare the bank result, the mandate wording, and the customer record in one view rather than relying on memory. Paste the current mandate text or checkout wording into the contact form.
- Authority wording tied to the collection method
- Date, amount, and account fields checked
- Dispute records linked to the original consent
South African debit rules in view
A South African collection mandate sits inside bank and scheme rules, not only your own contract wording. DebiCheck adds an authenticated step for qualifying debit orders, while other collection types may depend more heavily on stored consent and notice records. That is why operations, support, finance, and compliance need the same version of the mandate wording.
Practical conditions change how mandates are captured and defended. Load-shedding can affect in-branch devices, field sales teams may rely on mobile forms with patchy signal, and call-centre scripts must match what the customer later sees on statements and notices. A missing reference, wrong debit date, or vague cancellation route creates friction long before legal terms are read.
Operated by Astros Marketing (Pty) Ltd from 2 Makro Place, Sunnyrock 1401.
Evidence pack for disputed collections
When reviewing a collection mandate, bring the current text, the capture method, and one example of the notice sent before collection if your process uses notice. Include what failed in practice, such as date changes, amount changes, account swaps, or cancellations logged by support.
File the mandate record with the customer account and the collection history, not in a separate folder nobody checks during a dispute. It also helps to keep the acceptance evidence, debit references, and any change requests together when finance needs supporting documents.
What our Real-Time Payments customers say
Verified Google reviews