System overview
Kwik Payments is built around a clear structure to help you manage your collections efficiently. Here's a breakdown of each level and its purpose:
The starting point for all payment processing.
Capturing your customer's
Personal information (name, ID, contact details)
Bank account details (account number, bank, branch code, etc.)
Every mandate, payment, and transaction is linked to a customer.
Authorisation to debit the customer’s bank account.
Purpose:
Legally required approval from the customer.
Links directly to a customer's bank account.
Supports standard debit orders and DebiCheck.
A customer can have multiple mandates, and a payment can only be created on active mandates.
A payment plan should get linked to an active mandate to start collecting.
You get one-time and recurring payment types.
Payments generate transaction instructions.
The actual debit instruction sent to the bank.
Generated automatically based on the rules set in the payment (e.g., R500 every month).
Each transaction has a status (e.g., Sent to bank, Accepted by bank, Paid, Unpaid, in Tracking etc.) To get the full list of transaction statuses, follow this link..
All reporting and tracking happens at the transaction level.
In Summary:
Customer ➜ Mandate ➜ Payment ➜ Transaction
Customers hold personal and banking details.
Mandates give permission to debit their account.
Payments define how much and when to debit and triggers transactions.
Transactions are the actual debit attempts based on the payment rules.
Last updated