Payat

Version: 1.2

Effective Date: 2026-06-11

1. Purpose

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

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

Pay@ enables Customers to make payments in person at participating retail locations using a payment reference generated by Kwik.

This Policy should be read together with the following documents:

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

2. Scope

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

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

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

3. Underlying Payment Provider

Pay@ transactions are currently facilitated through:

• Pay@

By enabling or using Pay@, the Merchant acknowledges that transactions are also subject to the operational rules, technical requirements and legal documentation of Pay@.

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

• Pay@ Legal Documentshttps://payat.io/

Kwik relies on Pay@'s and each participating retailer's own compliance with Applicable Law and does not independently verify or guarantee that compliance.

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

4. Cash Transactions and Financial Crime Risk

Pay@ transactions completed in cash at a participating retail location may be subject to cash threshold reporting and other obligations under FICA, including obligations applicable to Kwik, Pay@, and the participating retailer.

The Merchant acknowledges that Kwik, Pay@, and participating retailers may, in accordance with the Sanctions and Anti-Money Laundering Policy:

• impose transaction value limits on Pay@ payments;
• request additional information in respect of a Pay@ transaction; and
• decline, delay, or report a Pay@ transaction where reasonably necessary to comply with Applicable Law.

5. Availability

Pay@ is available only:

• where supported by Kwik;
• where supported by Pay@;
• where supported by participating retail stores;
• where a valid payment reference is presented;
• where the payment is accepted by the participating retailer; and
• where the transaction is successfully processed.

Availability may vary due to:

• participating retailer operating hours;
• retailer outages;
• system maintenance;
• connectivity issues;
• operational requirements; or
• regulatory requirements.

Kwik does not guarantee continuous availability.

6. Payment References

Kwik may generate a payment reference for each transaction.

The Merchant acknowledges that:

• payment references may expire;
• payment references may only be used once where applicable;
• payment references may have a limited validity period;
• expired references may not be accepted; and
• payment references remain subject to the operational rules of Pay@.

The Merchant shall not alter, reuse or manipulate payment references.

7. Customer Payments

Customers complete Pay@ transactions directly at participating retail locations.

Kwik does not:

• collect cash from Customers;
• operate participating retail stores;
• control retailer operating hours;
• supervise retailer staff;
• control cash handling procedures; or
• guarantee that every participating retailer will accept every payment.

8. Merchant Responsibilities

The Merchant shall:

• provide accurate payment information;
• clearly communicate payment instructions to Customers;
• fulfil customer orders only after receiving confirmation of a successful payment where appropriate;
• maintain appropriate customer support processes;
• comply with Applicable Law;
• comply with the Merchant Agreement;
• comply with this Policy; and
• comply with the operational requirements of Pay@.

The Merchant shall not:

• accept manual proof of payment in place of a confirmed Pay@ transaction unless the Merchant accepts that associated risk;
• modify payment references;
• attempt to bypass Pay@ operational controls; or
• use Pay@ for unlawful purposes.

9. Settlement

Settlement timeframes depend upon:

• Pay@;
• participating retailers;
• banking operating hours;
• weekends and public holidays;
• operational processing windows; and
• regulatory requirements.

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

10. Refunds

Refunds are governed by the Chargeback & Dispute Policy.

Where refunds are supported:

• refunds remain subject to Applicable Law;
• refunds remain subject to Pay@ operational requirements;
• refunds may require additional verification; and
• refunds may only be processed by authorised users.

11. Disputes

Pay@ transactions generally do not support traditional card Chargebacks.

The Merchant remains responsible for:

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

Where Pay@ requires additional information relating to a transaction, the Merchant shall promptly provide all requested documentation.

12. Third-Party Rules

Pay@ transactions are subject to:

• the Merchant Agreement;
• this Policy;
• the operational rules of Pay@;
• participating retailer requirements; and
• Applicable Law.

Where Pay@ or participating retailers impose more restrictive operational requirements than this Policy, those requirements shall prevail to the extent necessary to process the transaction.

13. Suspension

Kwik may suspend Pay@ immediately where:

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

14. Limitation of Liability

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

• retailer outages;
• retailer operating hours;
• cash handling errors by participating retailers;
• delayed payment notifications;
• expired payment references;
• incorrect payment references supplied by the Customer;
• delays caused by Pay@;
• delays caused by participating retailers; or
• transaction failures outside Kwik's reasonable control.

15. Changes

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

• changes to Pay@ operational requirements;
• changes to participating retailers;
• 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/payat

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