Google Pay

Version: 1.2

Effective Date: 2026-06-11

1. Purpose

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

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

Google Pay is a digital wallet payment method that enables Customers to make payments using eligible Android devices and supported Google services.

This Policy should be read together with the following documents:

• Merchant Agreement
• Card Payments
• Fees & Pricing
• Privacy Notice
• Data Processing Addendum
• Information Security Policy
• Security Requirements
• Acceptable Use Policy
• Sanctions and Anti-Money Laundering Policy
• Chargeback & Dispute Policy

Unless expressly stated otherwise, all provisions applicable to Card Payments also apply to Google Pay transactions, including the prohibition on requiring Customers to waive dispute rights set out in the Merchant Agreement.

2. Scope

This Policy applies to Google Pay transactions processed through:

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

3. Availability

Google Pay is available only:

• where supported by Kwik;
• where supported by Google;
• where supported by the applicable issuing bank;
• where supported by the applicable card network; and
• on compatible Android devices and supported platforms.

Availability may vary by country, device, operating system version or payment card.

Kwik does not guarantee the availability of Google Pay.

4. Digital Wallet

Google Pay stores payment credentials using secure tokenisation technologies.

Kwik does not:

• issue Google Pay credentials;
• manage Google Accounts or Google Wallet;
• control Google Pay availability;
• control Android device functionality; or
• control Google's authentication mechanisms.

Google Pay remains subject to Google's own terms and conditions. Kwik relies on Google's own compliance with Applicable Law in respect of Google Pay and does not independently verify or guarantee that compliance.

5. Authentication

Google Pay transactions may require Customer authentication using methods determined by Google and the issuing bank, including:

• fingerprint authentication;
• facial recognition;
• device PIN or passcode;
• device pattern;
• biometric authentication; or
• other supported authentication methods.

The Merchant must not interfere with or attempt to bypass Google Pay authentication.

6. Network Tokens

Google Pay transactions generally use network tokens instead of the underlying card number.

The Merchant acknowledges that:

• network tokens are issued and managed by the applicable payment network or authorised service providers;
• tokens may be refreshed, replaced or withdrawn;
• token availability is outside Kwik's control; and
• tokenisation does not eliminate the possibility of fraud or Chargebacks.

7. Merchant Responsibilities

The Merchant shall:

• integrate Google Pay in accordance with Kwik's technical documentation;
• comply with Google's branding and user interface requirements where applicable;
• provide accurate transaction information;
• fulfil customer orders promptly;
• maintain appropriate customer support processes; and
• comply with all applicable card network requirements.

The Merchant shall not:

• modify Google Pay authentication flows;
• misrepresent Google Pay functionality;
• collect prohibited payment credentials; or
• attempt to circumvent Google's security controls.

8. Refunds

Refunds for Google Pay transactions are governed by the Chargeback & Dispute Policy.

Where supported, refunds must be processed back to the original payment method.

9. Chargebacks

Google Pay transactions remain card transactions.

Accordingly:

• Chargebacks;
• disputes;
• fraud claims;
• retrieval requests; and
• payment scheme rules

are governed by:

• Card Payments; and
• Chargeback & Dispute Policy.

The use of Google Pay does not eliminate the Merchant's liability for Chargebacks.

10. Suspension

Kwik may suspend Google Pay where:

• required by Google;
• required by a card network;
• required by an acquiring bank;
• required by a sponsoring bank;
• required by Applicable Law;
• fraud levels become unacceptable; or
• continued processing presents an unacceptable risk.

Suspension of Google Pay does not automatically suspend other payment methods.

11. Third-Party Requirements

Google Pay is provided through third-party infrastructure.

The Merchant acknowledges that Google, issuing banks, payment networks and other third parties may impose additional operational or technical requirements.

Kwik is not responsible for:

• Google service outages;
• Google Wallet availability;
• device compatibility;
• operating system issues;
• issuer restrictions; or
• Google policy changes.

12. Changes

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

• changes to Google Pay;
• changes to payment network rules;
• acquiring bank requirements;
• regulatory developments;
• security improvements; or
• operational enhancements.

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

/legal/payment-methods/google-pay

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