Apple Pay Integration with PAR Pay

Overview

Apple Pay is a secure, tokenized payment method that enables customers to complete transactions using payment cards provisioned on their Apple devices.

This guide defines the platform-level Apple Pay integration model within PAR Pay. PAR Pay functions as a payment orchestration layer, abstracting gateway-specific complexity while securely routing Apple Pay payment tokens through supported payment gateways for processing. By standardizing Apple Pay handling at the platform level, PAR Pay enables secure, consistent, and scalable Apple Pay support across supported gateways and environments.

The guide also defines the responsibility boundaries across Apple, PAR Pay, and the payment gateway, and describes how Apple Pay payment tokens are securely processed throughout the payment flow.

Gateway-specific onboarding, certificate management, certification, enablement, and operational procedures are intentionally documented in separate gateway onboarding guides to maintain a clear separation of concerns and simplify long-term maintenance. Teams implementing or operating Apple Pay integrations should refer to the appropriate gateway onboarding guide for gateway-specific configuration and execution details.

Prerequisites

Before Apple Pay transactions can be processed through PAR Pay, the following prerequisites must be satisfied.

Apple Merchant Configuration

• A valid Apple Merchant Identifier must be created and approved through Apple.
• The merchant identifier must be associated with the appropriate domain(s) and environment(s).
• Apple Pay must be enabled for the business account.

Gateway Onboarding

• The selected payment gateway must be fully onboarded and enabled for Apple Pay.
• Required Apple Pay certificates must be generated, uploaded, and validated at the gateway.
• Apple Pay must be verified in the target gateway environment (Sandbox and/or Production).

PAR Pay currently supports Apple Pay through the following gateways:

How Apple Pay Works in PAR Pay

Apple Pay functions as a tokenized card payment method. Sensitive card data is never exposed to PAR Pay or businesses. Instead, Apple generates a cryptographically secure payment token that represents the underlying card.

PAR Pay treats the Apple Pay token as an opaque payload and is responsible for:

• Validating the request context
• Determining the configured payment gateway
• Forwarding the token to the gateway for processing
• Returning the normalized gateway response to the caller

All Apple Pay-specific enablement — including merchant identifiers, certificates, and domain verification — is managed by the payment gateway.

Architectural Responsibilities

End-to-End Apple Pay Flow

1. The client initiates Apple Pay on an Apple-supported device.
2. Apple validates the device, card, and business context.
3. Apple generates a tokenized payment payload.
4. The client submits the Apple Pay token to PAR Pay.
5. PAR Pay validates the request and determines the configured payment gateway.
6. The token is forwarded to the gateway.
7. The gateway performs authorization and returns the transaction result.
8. PAR Pay returns a normalized response to the client.

Note: This flow is consistent across all supported gateways.

Passing the Apple Pay Token to PAR Pay

Once generated on the client device, the Apple Pay payment token is submitted to PAR Pay as part of the payment request. PAR Pay does not decrypt or interpret the token — it forwards it unchanged to the configured payment gateway.

Supported Payment Flows

The request structure and token handling are identical for both flows; the only difference is the endpoint used.

Example Request (Purchase / Preauthorize)

curl --location 'https://SERVER_NAME_GOES_HERE.partech.com/creditcard/v1/purchase' \
  --header 'X-LocationId: XXXXXXXXXXXXXXXXXXXXX' \
  --header 'X-ApplicationSource: <application-source>' \
  --header 'Content-Type: application/json' \
  --header 'Authorization: Bearer XXXXXXXXX' \
  --data '{
    "saveCard": true,
    "userId": "test-123456",
    "isPreferred": true,
    "referenceNumber": "258",
    "invoiceNumber": "02148",
    "transactionDateTimeUTC": "2026-07-28T14:19:02.051Z",
    "transactionDateTimeLocal": "2026-07-28T14:19:02.051",
    "transactionAmountDetails": {
      "taxAmount": 0,
      "discount": 0,
      "productTotalAmount": null,
      "totalAmount": 24
    },
    "walletPay": {
      "applePay": "<apple-pay-token>"
    }
  }'

Token Handling Notes

• The Apple Pay token is generated by Apple on the client device.
• PAR Pay does not decrypt, validate, or modify the token contents.
• Token decryption and authorization are performed exclusively by the payment gateway.
• The same payload structure is used across all supported gateways.