Help Section
Payment Methods

Payshap

 

Version: 1.2

Version: 1.2

Effective Date: 2026-06-11

1. Purpose

This PayShap Policy ("Policy") forms part of the Merchant Agreement.

This Policy governs the Merchant's acceptance of PayShap transactions processed through the Services.

PayShap enables Customers to make real-time account-to-account payments using participating South African financial institutions, operating on the rapid payments programme established under the National Payment System Act 78 of 1998 and operated by BankservAfrica under the oversight of the Payments Association of South Africa (PASA) and the South African Reserve Bank.

This Policy should be read together with the following documents:

2. Scope

This Policy applies to all PayShap transactions processed through the Services, including transactions initiated through:

  • Hosted Checkout;
  • Embedded Checkout;
  • Payment Links;
  • Merchant APIs;
  • Mobile Applications; and
  • any other PayShap integration supported by Kwik.

PayShap transactions are facilitated through participating South African financial institutions and any Underlying Payment Providers approved by Kwik.

3. Underlying Payment Infrastructure

PayShap transactions are processed using the South African real-time payment infrastructure.

By enabling or using PayShap, the Merchant acknowledges that transactions are subject to:

  • participating bank requirements;
  • payment infrastructure rules;
  • operational requirements imposed by Kwik;
  • Applicable Law; and
  • any additional rules imposed by participating payment partners.

Kwik relies on the payment infrastructure operator's and participating financial institutions' own compliance with Applicable Law and does not independently verify or guarantee that compliance.

Kwik may add, remove or replace supporting payment infrastructure without requiring an amendment to this Policy.

4. Availability

PayShap is available only:

  • where supported by Kwik;
  • where supported by the participating financial institution;
  • where the Customer successfully authorises the payment;
  • where sufficient funds are available; and
  • where the transaction is successfully approved.

Availability may vary due to:

  • banking outages;
  • maintenance windows;
  • network interruptions;
  • operational issues;
  • fraud controls; or
  • regulatory requirements.

Kwik does not guarantee uninterrupted availability.

5. Customer Authorisation

Customers authorise PayShap payments directly with their participating financial institution.

Kwik does not:

  • collect internet banking credentials;
  • authenticate Customers on behalf of banks;
  • control Customer authentication methods;
  • determine authentication outcomes; or
  • manage Customer banking sessions.

The Merchant shall never request or collect Customer banking credentials.

6. Payment Finality

Once a PayShap transaction has been successfully authorised and processed, it is generally considered final.

Completed PayShap payments cannot ordinarily be cancelled or reversed solely because:

  • the Customer changes their mind;
  • goods are returned;
  • services are cancelled;
  • an ordering mistake occurred; or
  • the Customer disputes the commercial transaction.

Where Applicable Law, a participating financial institution or the applicable payment infrastructure permits a reversal, such reversal shall be governed by the applicable operational rules.

7. Merchant Responsibilities

The Merchant shall:

  • provide accurate payment information;
  • accurately describe the goods or services being purchased;
  • fulfil customer orders promptly;
  • maintain appropriate customer support processes;
  • comply with Applicable Law;
  • comply with the Merchant Agreement;
  • comply with this Policy; and
  • comply with all operational requirements applicable to PayShap.

The Merchant shall not:

  • interfere with the PayShap payment flow;
  • misrepresent PayShap functionality;
  • attempt to manipulate payment confirmations;
  • request Customer banking credentials; or
  • use PayShap for unlawful purposes.

8. Settlement

PayShap is designed to support near real-time payments.

However, settlement timing may vary depending upon:

  • participating financial institutions;
  • fraud monitoring;
  • operational verification;
  • maintenance windows;
  • regulatory requirements;
  • weekends or public holidays; and
  • exceptional operational circumstances.

Kwik does not guarantee a specific settlement timeframe.

9. Refunds

Refunds are governed by the Chargeback & Dispute Policy.

Where a Customer is entitled to receive funds, the Merchant must initiate a separate refund transaction.

A completed PayShap payment should not be regarded as automatically reversible.

Refunds remain subject to:

  • Applicable Law;
  • banking requirements;
  • fraud screening;
  • sanctions screening; and
  • Kwik's operational requirements.

10. Disputes

PayShap does not operate under traditional card Chargeback rules.

The Merchant remains responsible for:

  • customer communications;
  • refund obligations;
  • supporting evidence;
  • product fulfilment; and
  • resolving commercial disputes.

The absence of Chargebacks does not limit Kwik's rights under the Chargeback & Dispute Policy, the Merchant Agreement, or Applicable Law.

11. Fraud Prevention

Kwik may delay, suspend or refuse PayShap transactions where reasonably necessary to:

  • prevent fraud;
  • investigate suspicious activity;
  • comply with Applicable Law;
  • comply with sanctions obligations;
  • comply with financial crime obligations;
  • comply with participating bank requirements; or
  • protect the integrity of the Services.

Fraud prevention measures may be implemented before or after payment initiation.

12. Third-Party Rules

PayShap transactions are subject to:

  • the Merchant Agreement;
  • this Policy;
  • the rules of participating financial institutions;
  • applicable payment infrastructure requirements;
  • Applicable Law; and
  • any additional operational requirements imposed by participating payment partners.

Where those operational requirements are more restrictive than this Policy, they shall prevail to the extent necessary to process the transaction.

13. Suspension

Kwik may suspend PayShap immediately where:

  • required by a participating financial institution;
  • required by Applicable Law;
  • fraud is suspected;
  • suspicious activity is identified;
  • continued processing presents an unacceptable operational, financial or regulatory risk; or
  • the Merchant breaches this Policy or the Merchant Agreement.

Suspension of PayShap does not automatically suspend other payment methods.

14. Limitation of Liability

Without limiting the Merchant Agreement, Kwik shall not be liable for:

  • banking outages;
  • delayed payment confirmations;
  • Customer authentication failures;
  • incorrect payment details provided by the Customer or Merchant;
  • failures within participating banking systems;
  • delays caused by participating financial institutions;
  • transaction failures outside Kwik's reasonable control; or
  • losses resulting from the Merchant's failure to verify payment status before fulfilling goods or services.

15. Changes

Kwik may amend this Policy from time to time to reflect:

  • banking rule changes;
  • regulatory developments;
  • operational improvements;
  • security enhancements;
  • technological developments; or
  • industry best practices.

The latest version of this Policy will always be available at:

/legal/payment-methods/payshap

Continued use of PayShap after an updated version becomes effective constitutes acceptance of the revised Policy where permitted by Applicable Law.

Zapper

Version: 1.2

Moneybadger

Version: 1.2