1. Purpose
This Merchant Guide provides operational guidance for Merchants wishing to accept Apple Pay® and Google Pay™ through the PAYSTRAX payment platform.
Apple Pay and Google Pay are optional digital wallet payment methods made available by PAYSTRAX as part of its payment services. These payment methods allow customers to make card payments using eligible payment cards stored in supported Apple or Google digital wallets.
Transactions initiated using Apple Pay or Google Pay are processed as standard card payment transactions and remain subject to:
- the Merchant Framework Agreement (hereinafter referred to as „MFA“) between PAYSTRAX and the Merchant;
- the applicable Card Scheme Rules;
- the applicable requirements published by Apple and Google; and
- applicable laws and regulations.
This Merchant Guide is intended to assist Merchants with the operational use of Apple Pay and Google Pay and does not amend or replace the MFA.
2. Merchant Eligibility
To accept Apple Pay or Google Pay through PAYSTRAX, the Merchant must:
- maintain an active Merchant account with PAYSTRAX;
- be approved by PAYSTRAX for card acquiring services;
- complete the applicable technical integration;
- operate a secure HTTPS enabled website or application;
- satisfy PAYSTRAX onboarding, compliance and risk requirements; and
- comply with the MFA and this Merchant Guide.
The availability of Apple Pay or Google Pay may depend on the Merchant’s business model, integration method, supported markets and PAYSTRAX approval.
3. Roles and Responsibilities
The following table summarises the principal responsibilities relating to Apple Pay and Google Pay.
| PAYSTRAX | Merchant |
| Enables Apple Pay and/or Google Pay for approved Merchants. | Correctly implements and maintains the selected PAYSTRAX integration. |
| Provides and operates the payment platform and payment infrastructure. | Maintains a secure website, application and checkout environment. |
| Processes wallet transactions submitted through the PAYSTRAX platform. | Protects API credentials, certificates, keys and other credentials under the Merchant’s control. |
| Provides transaction reporting and settlement in accordance with the MFA. | Maintains its domain, website and technical configuration. |
| Manages PAYSTRAX-operated Apple Pay merchant configuration, merchant validation and platform certificates, where applicable to the selected integration model. | Hosts any required Apple Pay domain verification files or completes any merchant-managed configuration where applicable. |
| Applies operational monitoring, fraud prevention and payment processing controls. | Complies with applicable technical, security, legal and operational requirements published by Apple, Google, the Card Schemes and competent regulatory authorities. |
| Provides reasonable technical support relating to the PAYSTRAX platform. | Provides customer support relating to its products, services, fulfilment, refunds and customer communications. |
The allocation of responsibilities may vary depending on the selected integration method. Merchants remain responsible for any activities, credentials or technical components under their control.
4. Apple Pay and Google Pay requirements
Merchants accepting Apple Pay or Google Pay are responsible for complying with all applicable requirements relating to their use of these payment methods.
This includes, where applicable:
- Apple Pay programme requirements;
- Google Pay programme requirements;
- applicable Card Scheme Rules;
- applicable technical and security requirements;
- applicable branding and trademark guidelines; and
- applicable laws and regulations.
Where required by the selected integration model, the Merchant must complete any Apple Pay domain verification, Google Pay merchant registration or other wallet-specific onboarding requirements.
5. Security and PCI DSS
The Merchant remains responsible for maintaining an appropriate level of security for its website, application and payment environment.
The Merchant’s PCI DSS obligations depend on the selected integration method.
Hosted payment page or hosted checkout integrations are generally designed to reduce the Merchant’s PCI DSS scope, while server-to-server integrations may require additional PCI DSS compliance responsibilities.
Nothing in this Merchant Guide limits or replaces the Merchant’s own PCI DSS obligations.
6. Operational Information
Apple Pay and Google Pay availability depends on a number of factors, including:
- customer device compatibility;
- supported browsers;
- eligible payment cards;
- issuing bank participation;
- applicable Card Scheme Rules;
- customer authentication requirements; and
- PAYSTRAX operational and risk controls.
Transactions initiated using Apple Pay or Google Pay may be authorised, declined, challenged, reversed, refunded or charged back in accordance with the MFA and the applicable Card Scheme Rules.
7. Intellectual Property
Apple Pay® is a trademark of Apple Inc.
Google Pay™ is a trademark of Google LLC.
The Merchant must use Apple Pay and Google Pay names, logos, buttons and other branding only in accordance with the applicable branding guidelines published by Apple and Google.
8. Relationship with the Merchant Framework Agreement
This Merchant Guide is provided for operational and informational purposes only. It does not amend, replace or supplement the MFA. In the event of any inconsistency between this Merchant Guide and the MFA, the MFA shall prevail. PAYSTRAX may update this Merchant Guide from time to time to reflect changes in applicable laws, Card Scheme Rules, wallet provider requirements or PAYSTRAX services.