Built to Raise the Standard
A radically improved, purpose-built DebiCheck solution for South African banks
Creditor and debtor bank mandate management
Creditor and debtor collections clearing
Scheme processing
Transaction state management
Observability
Operator control
The Challenge
The hidden cost of retrofitting DebiCheck
DebiCheck brings its own rules, messages, processing windows, exceptions, and transaction state management. Layer those requirements onto software built for another scheme and every change has more existing behaviour to account for. Processing becomes harder to trace. Changes take longer to implement and test, and support becomes more demanding.
Electrum DebiCheck: built for the scheme, not adapted to it
We started with the scheme. We understand its transaction journeys, rules, processing conditions and operating requirements. Your bank connects to a defined Electrum interface.
You keep control of
Customer channels
Authorisation
Order management
Corporate collector integration
Core banking
The direct PayInc relationship
We manage
Scheme communication with PayInc
Transaction orchestration and state management
File handling
Scheme-rule application
Processing windows
Supported exception behaviour
Key Features
Four services in one processing foundation
Implement the services you need first and expand from there. The services stay distinct, while sharing the same foundation for integration, orchestration, transaction state management, and scheme communication.
Mandate Management
Collections
Creditor bank
Mandate Management
Collections
Debtor bank
Mandate Management
Collections
Exception handling is built in
The happy path is only one part of Electrum DebiCheck.
Our software also manages:
Validation failures
Missing or delayed responses
Cancellations
Error corrections
Scheme rejections
Duplicate transactions and files
Disputes
Authorised intervention
See what is happening
Through the Electrum Console, authorised users can move from a service-level signal to the underlying transaction. See the state, the history, related information and where a rejection occurred.
Structured logs, dashboards, and alerts support monitoring and relevant transaction events can also move into downstream bank systems.
Transactions
Collections
SLA conditions
Processing-window risk
Mandates
Processing states
Scheme rejections
Regulatory Buffer
Contain scheme changes
Electrum DebiCheck provides an ISO 20022-aligned REST API for bank integration.
We manage the relevant DebiCheck scheme messaging behind it, while scheme-specific processing stays inside the product rather than spreading across surrounding bank systems.
Where a scheme change does not affect the bank-facing integration, we absorb it within the processing layer and isolate change wherever possible.
Scale and Stability
Built to handle changing demand
DebiCheck volumes are not static. We plan capacity against forecast transaction volumes and increase it ahead of known load events.
Processing becomes harder to trace. Changes take longer to implement and test, and support becomes more demanding.
Scale is planned for, monitored, and managed.
Partnership
We don’t stop at go-live
We deploy, operate, monitor, and support the deployed software within your bank's environment. What we learn through implementation, operation, support, and client engagement feeds back into Product and Engineering. The service model includes:
01
Proactive monitoring
02
Severity-based incident handling
03
Escalation
04
Reporting
05
Post-incident reporting for significant events
Local Expertise
South African payments expertise, where it matters
DebiCheck sits inside a specific South African payments environment. Our teams work closely with South African banks, regulators and retailers, and that experience informs how we build, implement, operate, and support the software.
Local
schemes
Local
industry requirements
Local
change
Evidence behind the build
The complexity of DebiCheck is not theoretical, and neither is our operating capability. Our CHP deployments prove how we run critical payments software under real banking conditions.
Integrate critical payments software
Run cloud-based services
Operate it in production
Test against expected
processing demand
Accommodate scheme change
Modernise payment
infrastructure in stages
Future-Ready Payments
Electrum DebiCheck applies that operating experience to how we designed software specifically for the scheme, building on our broader CHP experience, including how we enabled PayShap at a leading bank.
Your technical questions answered
Can we implement it in stages?
Yes. Start with the creditor or debtor side, mandate management or collections, or both. Expand as your requirements change.
What remains with the bank?
- Customer channels.
- Authorisation.
- Order management.
- Corporate collector integration.
- Core banking.
- Your direct PayInc relationship.
We manage the DebiCheck processing between those boundaries.
What can payment teams see?
- Transactions.
- Mandates.
- Collections.
- State.
- History.
- Rejections.
- Processing-window risk.
How do you handle scheme change?
Scheme-specific behaviour sits inside the processing layer. Where the bank-facing integration does not need to change, the change stays with us.
What proof exists today?
Our Clearing House Payments software already runs in South African banking environments and is available for evaluation and demonstration.
Explore Electrum DebiCheck in detail
Go deeper with our Product Book to see how Electrum DebiCheck is put together, from architecture and service design to operational control and implementation.
See Electrum DebiCheck in action
See scheme processing, transaction state, exception behaviour, and observability in practice.
