Help Section
Payment Methods

Snapscan

 

Version: 1.2

Version: 1.2

Effective Date: 2026-06-11

1. Purpose

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

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

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

This Policy should be read together with the following documents:

2. Scope

This Policy applies to all SnapScan 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 SnapScan integration supported by Kwik.

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

3. Underlying Payment Provider

SnapScan transactions are currently facilitated through:

  • SnapScan

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

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

Kwik relies on SnapScan'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 SnapScan where reasonably necessary for operational, regulatory or commercial reasons.

4. Availability

SnapScan is available only:

  • where supported by Kwik;
  • where supported by SnapScan;
  • 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 SnapScan.

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 SnapScan transactions directly within the SnapScan application or another supported payment application.

Kwik does not:

  • authenticate Customers on behalf of SnapScan;
  • control the operation of the SnapScan 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 SnapScan.

The Merchant shall not:

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

8. Settlement

Settlement timeframes depend upon:

  • SnapScan;
  • 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 SnapScan'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 SnapScan transactions may be subject to SnapScan's operational rules.

The Merchant remains responsible for:

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

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

11. Third-Party Rules

SnapScan transactions are subject to:

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

Where SnapScan'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 SnapScan immediately where:

  • required by SnapScan;
  • 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 SnapScan does not automatically suspend other payment methods.

13. Limitation of Liability

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

  • SnapScan service interruptions;
  • QR Code scanning failures;
  • Customer device failures;
  • network connectivity issues;
  • payment application failures;
  • delays caused by SnapScan;
  • 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 SnapScan'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/snapscan

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

Pay By Bank

Version: 1.2

Zapper

Version: 1.2