MAPS confirms incoming payments.
MAPS receives credit notifications from supported South African banks and posts each transaction to an endpoint you host, so your workflow continues from the bank’s own notification.
How a payment reaches your system.
The customer pays
The customer makes an EFT or other bank payment into your account at a supported South African bank.
The bank reports the credit
The bank generates a credit notification for the incoming payment.
MAPS receives the notification
MAPS receives the bank-sourced notification through Debitech’s bank connectivity.
MAPS posts it to your endpoint
MAPS sends the transaction details to an endpoint you host and retries any delivery your system does not acknowledge.
Your system acts
Fulfil the order, activate the account, credit the wallet or release the ticket.
What MAPS gives your team.
Bank-sourced
Credit notifications come from supported banking channels, not from a statement file or a manual check.
Delivered to your endpoint
Your system receives structured JSON and acknowledges each delivery. Deliveries that are not acknowledged are retried.
Your rules
Use the notification to trigger fulfilment, allocation or other downstream processing.
Availability
MAPS availability depends on the bank and account type, and is confirmed during onboarding.
Where teams use it.
Wallets and gaming
Credit the wallet when the bank notification arrives, without waiting for end-of-day reconciliation.
Subscription services
Activate or renew a service from the credit notification, without a manual reconciliation step.
Merchants and retailers
Release goods or continue fulfilment when the bank-sourced credit notification arrives.
Prepaid services
Issue the voucher or token when MAPS reports the customer’s payment.
Discuss your integration.
Describe the use case. We will map it to the relevant product and integration path.