Introduction

Notes

• API endpoints are RESTful GET/POST HTTP requests
• Body type must be application/json
• All API calls made must include the authorization key in the header of the call.
• Requests to the API will be limited to 100 requests per second to reduce the load on the platform.
• Dates are to be specified as 'YYYY-MM-DD'
• Timestamps are specified as 'YYYY-MM-DD HH:mm:ss' GMT+2 (South African Standard Time)

Path

Staging

https://staging.app.kwik.co.za/1.0/

Live

https://api.kwik.co.za/1.0/

Authentication

Follow the ‘Basic Authorization’ standard, below is an example:

const hexString = Buffer.from(`${api_key}:${api_secret}`).toString('base64');
const headers = {
 'Authorization': `Basic ${hexString}`,
};

Staging Bank Account Numbers

These testing bank account numbers can be used in the staging environment when creating payments.

EFT Debit Order Payments

Payment status changes can be made from the dashboard or via API payment status update API call.

If you use any other bank account number the resulting transaction status will be 'Pending'.

DebiCheck Payments

The cellphone number used on the payment will not receive a notification, this notification will only be sent on the live environment, instead a resulting payment status is simulated as shown below:

If you use any other bank account number the resulting payment status will be 'Pending' or 'Stopped' with 'no reply from debtor' payment failed at reason. DebiCheck transactions can not be disputed UNLESS you allow payment tracking and failed transactions are re-submitted. Refer to EFT debit order payments for testing all possible transaction statuses.