Getting Started

Native Apple Pay — Partner Integration Guide

Native Apple Pay integration. Enable seamless Apple Pay checkout directly on your website or application. Your frontend manages the user interface and Apple Pay interaction, while Mercuryo handles payment processing on the backend.

What You Can Build

  • Native Apple Pay checkout — process payments directly on your site, without redirecting users to the Mercuryo widget; users complete the entire payment flow without leaving your application.
  • Headless integration — full control over the UI while Mercuryo handles payment processing, KYC/AML and the final status callback.
  • Built-in compliance — KYC can be completed in advance, in your own interface, or the user is handed over to the Mercuryo widget when verification is needed during the payment.
  • Secure processing — a two-certificate model ensures maximum security and a clear separation of responsibilities.

How It Works

The integration is based on a "headless" model: your application manages the user interface and the interaction with Apple, and Mercuryo's backend executes the payment.

  1. Quote — your backend requests a quote from Mercuryo and receives a quote_token. If native Apple Pay can't be offered for this user, the quote request is rejected.
  2. Apple Pay — your frontend shows the Apple Pay payment sheet. Your backend validates the merchant session with Apple using your own Merchant Identity Certificate, and Apple returns an encrypted payment token.
  3. Payment — your backend sends the encrypted token, the quote_token and the user's data to Mercuryo. Mercuryo decrypts the token using your Payment Processing Certificate and processes the transaction.
  4. KYC (if required) — the user can pass KYC before the payment, in your own interface, or in the Mercuryo widget when the payment response requires it.
  5. Final status — Mercuryo sends the final transaction status to your callback URL.

Step-by-step instructions are in Native Payment.

Availability and Restrictions

  • Cards: Visa and Mastercard.
  • United Kingdom (GB) and the European Economic Area (EEA): Native Apple Pay is currently not available for users from these regions. The region is determined by the user's IP address.
  • Cards issued in the United Kingdom: payments with bank cards issued in the United Kingdom are not processed, regardless of the user's location.
  • United States (US): Native Apple Pay is available for US users through a dedicated flow — see the US-specific rules in Transaction Limits for Light KYC Users and KYC.

Mercuryo enforces these rules on the backend, but we recommend you also apply them on your frontend to improve the user experience.

Transaction Limits for Light KYC Users

Non-US user

For users who have not completed full KYC, there is a cumulative transaction limit: the total turnover across all their transactions, converted to EUR, cannot exceed €700. Above this limit, full KYC is required.

US user

For users from the United States, light KYC with SSN is required for every payment. Which verification is needed depends on the user's cumulative turnover across all their transactions, converted to EUR:

  • Cumulative turnover < 1500 EUR — light KYC with SSN.
  • Cumulative turnover >= 1500 EUR — full KYC.

Once the relevant limit is reached, a dedicated KYC flow is triggered instead of a simple rejection. See KYC for the available scenarios.

Support

Contact your integration manager or email sales@mercuryo.io.

Next
Onboarding