The rails
Every collection travels on one of a few roads.
In South Africa, a recurring payment can leave a customer's account by only a small number of routes, and each route has its own manners. Broadly there are two families. On one side sits the card - collections taken online, at a point of sale, or on a recurring card token. On the other sits traditional collection against a bank account: DebiCheck, the debit order, and the registered mandate.
They are not interchangeable. A card runs on scheme rails and is authorised card-side; a bank-account collection runs through the shared clearing that every South African bank plugs into. Same goal, different plumbing - and the plumbing decides almost everything about timing, disputes, and what happens when a payment misses.
Pick the wrong road and the money doesn't move faster. It doesn't move.
The mandates
Authenticated is not the same as registered.
On the traditional side the whole game is the mandate - the customer's standing permission to be debited. How that permission was captured decides how strong the collection is. There are three, firmest to softest: DebiCheck is bank-authenticated at the customer's own bank; the Registered Mandate is registered at lower fees, without that authentication; and the plain debit order rests on a mandate the business holds itself - the most familiar, and the most disputable.
The bank saying yes up front is worth more than any letter you keep on file.
Each earns its own page - the exact terms matter, and they're laid out in full in the lessons below. Each runs on national payment-system rules overseen by the SARB - DebiCheck under its authenticated-collections directive, Registered Mandate and debit orders under the industry's clearing rules.
The clock
Why card settles daily and traditional clears in windows.
A collection landing is one thing; the cash reaching your account is another. Here the two families part company most visibly.
Card collections settle on the card-scheme rails, typically the next business day. Settlement comes with a detailed, transaction-level breakdown of every batch. For a recurring book, that is the difference between cashflow you can see coming and cashflow you have to chase.
Traditional rails work differently. Bank-account collections clear in shared processing windows that every bank submits into together, so the money settles on a delay rather than the same day. It is not worse; it is a different clock. Daily, next-day settlement is a card characteristic - traditional collections resolve in their windows and pay out afterwards.
Same rand. Different clocks.
The difference
What cross-payment functionality actually means.
A static platform treats a failed collection as an ending: it bounced, so it retries the same instruction on the same rail and hopes for a kinder day. That is not thinking. That is repetition.
A platform with cross-payment functionality does something else. Its payment channels are flexibly interwoven, so when a collection fails it isn't simply re-run - it can be worked on another channel, and when it lands it shows in your settlement reports with its references, ready to line up with the deposits in your bank.
The result is fewer rejections, lower costs and higher success rates - a book worked to its process end. It works from what actually happened.
A failure on one rail can become a landing on another.
