Payment Methods

Zapper

Version: 1.2

Version: 1.2

Effective Date: 2026-06-11

1. Purpose

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

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

Zapper enables Customers to make payments by scanning a QR code using the Zapper mobile application or other supported applications.

This Policy should be read together with the following documents:

2. Scope

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

Hosted Checkout;
Embedded Checkout;
Payment Links;
Merchant APIs;
Mobile Applications;
Static QR Codes;
Dynamic QR Codes; and
any other Zapper integration supported by Kwik.

Zapper transactions are facilitated through an Underlying Payment Provider approved by Kwik.

3. Underlying Payment Provider

Zapper transactions are currently facilitated through:

Zapper

By enabling or using Zapper, the Merchant acknowledges that transactions are also subject to the operational rules, technical requirements and end-user terms imposed by Zapper.

The Merchant agrees to comply with the applicable Zapper legal documentation available at:

Zapper Legal Documentshttps://www.zapper.com/legal/

Kwik relies on Zapper's own licensing and compliance with Applicable Law and does not independently verify or guarantee that compliance.

Kwik may suspend, replace or discontinue support for Zapper where reasonably necessary for operational, regulatory or commercial reasons.

4. Availability

Zapper is available only:

where supported by Kwik;
where supported by Zapper;
where the Customer successfully authorises the payment;
where the Customer uses a supported payment application; and
where the transaction is successfully approved.

Availability may vary due to:

provider availability;
Customer device compatibility;
network connectivity;
maintenance windows;
operational issues; or
regulatory requirements.

Kwik does not guarantee the continuous availability of Zapper.

5. QR Codes

Kwik may generate:

static QR Codes;
dynamic QR Codes;
reusable payment QR Codes;
transaction-specific QR Codes; or
other supported QR payment formats.

The Merchant shall:

ensure QR Codes are displayed accurately;
prevent unauthorised modification of QR Codes;
protect QR Codes from tampering where reasonably possible;
verify that QR Codes relate to the correct Merchant Account; and
immediately notify Kwik if a QR Code is suspected of being compromised.

6. Customer Authorisation

Customers authorise Zapper transactions directly within the Zapper application or another supported payment application.

Kwik does not:

authenticate Customers on behalf of Zapper;
control the operation of the Zapper application;
manage Customer wallet credentials;
determine authentication outcomes; or
control Customer devices.

7. Merchant Responsibilities

The Merchant shall:

provide accurate payment information;
accurately describe the goods or services being purchased;
fulfil customer orders promptly;
provide appropriate customer support;
comply with Applicable Law;
comply with the Merchant Agreement;
comply with this Policy; and
comply with the operational requirements of Zapper.

The Merchant shall not:

interfere with the Zapper payment flow;
manipulate QR Code values after presentation to the Customer;
misrepresent Zapper functionality;
attempt to bypass Zapper security controls; or
use Zapper for unlawful purposes.

8. Settlement

Settlement timeframes depend upon:

Zapper;
banking operating hours;
weekends and public holidays;
operational processing windows;
payment verification processes; and
regulatory requirements.

Settlement estimates published by Kwik are indicative only and do not constitute a guarantee.

9. Refunds

Refunds are governed by the Chargeback & Dispute Policy.

Where supported:

refunds must comply with Zapper's operational requirements;
refunds remain subject to Applicable Law;
refunds may only be processed by authorised users; and
refunds may only be processed to the original payment source where required.

10. Disputes

Disputes relating to Zapper transactions may be subject to Zapper's operational rules.

The Merchant remains responsible for:

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

Where Zapper requires information relating to a dispute, the Merchant shall promptly provide all requested documentation.

11. Third-Party Rules

Zapper transactions are subject to:

the Merchant Agreement;
this Policy;
the operational rules of Zapper;
applicable banking requirements; and
Applicable Law.

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

12. Suspension

Kwik may suspend Zapper immediately where:

required by Zapper;
required by Applicable Law;
fraud is suspected;
suspicious activity is identified;
excessive disputes occur;
continued processing presents an unacceptable operational, financial or regulatory risk; or
the Merchant breaches this Policy or the Merchant Agreement.

Suspension of Zapper does not automatically suspend other payment methods.

13. Limitation of Liability

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

Zapper service interruptions;
QR Code scanning failures;
Customer device failures;
network connectivity issues;
payment application failures;
delays caused by Zapper;
Customer authentication failures;
banking delays; or
transaction failures outside Kwik's reasonable control.

14. Changes

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

changes to Zapper's operational requirements;
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/zapper

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

Snapscan

Version: 1.2

Payshap

Version: 1.2