Apple Pay uses the shared wallet options described in Wallets plus a few Apple-only extras.
Example
Availability
Apple Pay renders on Safari (macOS and iOS). On Chromium browsers, the sheet is delivered via a QR handoff to a supported Apple device; control the presentation with renderApplePayCodeAs.
Apple Pay requires HTTPS. It does not render on http:// origins.
Match your surrounding UI:
Use 'plain' when the surrounding CTA already describes the action (“Pay with”). Use 'buy' on ecommerce checkouts.
Chromium QR handoff
On Chromium, tapping the Apple Pay button opens a QR code the shopper scans with a nearby Apple device. Pick where the code renders:
'window' opens a new browser window; 'modal' renders in-page. Modal is generally the better default because it stays inside your checkout container.
supportedNetworks
Restrict the card networks Apple presents inside the sheet:
Omit the option to accept every network your merchant configuration supports.
Recurring payments
Attach a recurring payment request to display subscription copy inside the sheet:
Google Pay does not surface a comparable option; the field is Apple-only.
Requirements escape hatch
Use require for the common fields (name, email, phone, billing address, shipping address). When you need a field Apple supports that require doesn’t cover — such as phoneticName — pass requirements.requiredBillingContactFields or requirements.requiredShippingContactFields to fully replace the derived contact-fields array. Similarly, pass shipping choices under requirements.shippingMethods. See Apple’s PaymentRequest documentation for the field values.
See also
Last modified on July 29, 2026