DebiCheck API vs Host-to-Host: Which Integration Should You Use?
Banks expose DebiCheck through two kinds of technical interface: real-time APIs and batch host-to-host file exchanges. Both support the full set of operations — mandate initiation, amendment, cancellation and collections — but they behave very differently, and the right choice depends on how and where your customers sign up and how many collections you process.
Many businesses end up using both: API for the sign-up moment, host-to-host for the monthly collection run. A payments provider like Kwik can expose a single integration that routes to either channel behind the scenes.
How does a DebiCheck API integration work?
With an API integration (for example Absa's CAPI), each operation is an individual real-time message:
- Your system calls the API to initiate a mandate while the customer is signing up.
- The bank pushes the authentication request to the customer — for TT1, a USSD prompt or app notification the customer actions within about 120 seconds.
- The outcome (authenticated, rejected, expired) is returned to your system via the API response or a callback, per message.
- Collections, amendments and cancellations follow the same request-and-response pattern.
The defining benefit is immediacy: a TT1 sign-up can go from "customer says yes" to "authenticated mandate" inside a single phone call or checkout session, and your sign-up flow can react to the result in real time.
How does host-to-host integration work?
Host-to-host is a batch file interface: you assemble mandate requests, amendments, cancellations and collection instructions into structured files, transmit them to the bank over a secure connection, and receive response files with statuses and reason codes per record in return.
The defining benefit is throughput: tens or hundreds of thousands of records move in a single exchange, which suits scheduled monthly collection runs and bulk onboarding. The trade-off is latency — outcomes arrive when the response files do, not in the moment.
API vs host-to-host at a glance
| Aspect | Real-time API | Host-to-host (batch files) |
|---|---|---|
| Message model | One request/response per operation | Files containing many records |
| Result latency | Seconds (per message) | Batch cycles |
| Best for mandates | TT1 real-time sign-ups | TT2 bulk initiation, migrations |
| Best for collections | Low volume or event-driven debits | High-volume scheduled runs |
| Status delivery | API responses and callbacks | Response and reply files |
| Build effort | REST-style integration, webhook handling | File generation, secure transfer, file reconciliation |
Statuses and reason codes are returned per message in both channels — the semantics are the same even though the transport differs. See statuses and reason codes.
Which should your business choose?
- Choose API if your sign-ups happen in real time — call centres, in-app flows, point-of-sale — and you want TT1 authentication with an immediate answer.
- Choose host-to-host if you run large scheduled collection books, migrate existing mandate bases, or already operate bank file exchanges.
- Choose both if, like most collectors at scale, you need real-time sign-up and high-volume monthly collections.
Direct integration with a bank requires a sponsoring bank relationship, conformance to the bank's technical specifications and certification testing. Integrating through Kwik gives you one modern API for mandates and collections, with Kwik operating the underlying bank API and host-to-host connections, normalising statuses and reason codes across banks.
The same considerations apply to Registered Mandate integrations — see RM API vs host-to-host. For the general integration trade-offs beyond DebiCheck, see batch files vs APIs.
Related topics
Troubleshooting
Fixes for common DebiCheck issues, including expired authentication requests, rejected mandates, failed amendments and collections that keep declining.
Is DebiCheck Safe?
DebiCheck was designed by South African banks to industry security standards. Learn how mandate approval works safely and how to spot phishing attempts.