Skip to main content
Accept Apple Pay through Ecrypt’s hosted checkout products. Apple Pay lets shoppers check out with any credit or debit card saved to Apple Wallet, authorizing the payment with Face ID, Touch ID, or their device passcode. Ecrypt handles the wallet flow on our hosted pages, so you can enable Apple Pay without building or certifying the wallet integration yourself.

​
At a glance

​
Where Apple Pay is available in Ecrypt

Apple Pay is currently offered only through Ecrypt’s hosted checkout surfaces. When a shopper lands on one of these pages from a compatible Apple device and browser, the Apple Pay button renders automatically alongside the standard card form:
  • Dynamic Checkout: full-featured, hosted checkout page created with the /v1/dynamiccheckout endpoint.
  • Hosted iFrame: populate Apple Pay in Ecrypt’s hosted iFrame underneath card fields.
  • Payment Links: shareable URLs that accept a single payment or kick off a subscription.
  • Invoices: customer-facing invoice pages with a pay-now action.
Because the button renders through Apple’s own JavaScript API, it always displays the current, correctly localized Apple Pay button style. Ecrypt does not create custom Apple Pay buttons or alter Apple’s artwork, in line with Apple’s Human Interface Guidelines and Marketing Guidelines.

​
Turn Apple Pay on

Apple Pay is activated by the Ecrypt team. Ecrypt registers and manages the Apple Pay configuration on your behalf. You don’t need an Apple Developer account, and you don’t manage any Apple Pay keys or certificates. To enable Apple Pay:
  • New merchants: request Apple Pay with your Ecrypt account representative during initial onboarding.
  • Existing merchants: reach out to your Ecrypt account representative or contact support to request activation.
Once activated, the Apple Pay button begins rendering on your hosted checkout surfaces. If you embed Dynamic Checkout or the hosted iFrame on your own domain, complete the one-time domain verification step below.
Ecrypt manages token decryption and processing on your behalf. You never handle raw card numbers.

​
Accepting inbound international payments

Ecrypt accepts Apple Pay from shoppers in any country or region where Apple Pay operates. The cardholder selects a card from Apple Wallet, and Ecrypt processes it as a standard card transaction. Settlement happens in USD to your merchant account, following your normal funding schedule. For an up-to-date list of countries and regions where shoppers can use Apple Pay, see Apple’s supported countries and regions.

​
Recurring billing and subscriptions

Apple Pay works with Ecrypt subscriptions. When a customer completes their first payment through Dynamic Checkout that includes a subscription object, Ecrypt stores the resulting tokenized payment credential and reuses it for each recurring charge on the cycle you define. For recurring, automatic-reload, and deferred payments, Ecrypt requests an Apple Pay merchant token where the card issuer supports it. A merchant token links the card, merchant, and shopper so billing continues even if the shopper upgrades their device or removes the card from one device. Where the issuer does not yet support merchant tokens, Ecrypt falls back to the standard device token automatically — no change on your end. Ecrypt marks the stored credential appropriately so follow-on charges run as merchant-initiated transactions. For details on cycle types and billing dates, see the Subscriptions reference.

​
Post-payment operations

Apple Pay transactions settle as standard card transactions in Ecrypt, so you can manage them exactly like any other credit card charge. Refunds (full or partial), voids on unsettled authorizations, and chargeback responses all run through the same endpoints and dashboard workflows you already use for card payments. Apple Pay transactions appear in reporting with the paymentNetwork set to the underlying card brand (Visa, Mastercard, and so on) and are flagged as Apple Pay, making them easy to identify and reconcile alongside your other card volume.

​
Data verification

Payment data
Ecrypt handles the generation of the Apple Pay payment request and manages the encrypted payload securely. Merchants are not required to manually configure merchant identifiers, supported networks, or certificates — Ecrypt maps the decrypted Apple Pay token (including the one-time cryptogram and ECI values) to the authorization message for you. Billing and shipping data
Ecrypt automatically configures the contact fields collected in the Apple Pay payment sheet and uses them for address verification during checkout. Apple does not verify the contact information a shopper provides, so Ecrypt validates it on our side and surfaces any correctable fields back through the payment sheet. No additional code or custom configuration is required on the merchant’s end.

​
Testing

To test the Apple Pay flow end-to-end:
  1. Generate a Dynamic Checkout, Payment Link, or Invoice in your Ecrypt sandbox environment.
  2. Sign in to iCloud on a physical Apple device using an Apple Pay Sandbox Tester account, and add one of Apple’s sandbox test cards to Wallet.
  3. Open the resulting URL in Safari (or a supporting third-party browser) and complete the flow. Sandbox charges are not settled.
  4. Also test in your production environment with a real card to confirm the end-to-end flow before going live.
Apple Pay only renders on devices and browsers that meet Apple’s eligibility rules: an Apple Pay-capable device, an HTTPS connection, a supported browser, and at least one card in Wallet. On desktop, the shopper needs an Apple Pay-capable iPhone or a Mac with Touch ID to authorize. If the button doesn’t appear, those are the first things to check.

​
Embedding Dynamic Checkout in an iFrame

If you’re testing Dynamic Checkout inside an <iframe> on your own page, the Apple Pay sheet requires the frame to be allowed to invoke the Payment Request API, and the top-level page domain must be registered and verified for Apple Pay. At minimum, include the allow="payment" attribute:
  • allow="payment" enables the Payment Request API that Apple Pay relies on.
  • allow-same-origin is required so Ecrypt’s checkout page can talk to its own origin.
  • allow-scripts and allow-forms are required for the page itself to function.
The simplest option is omitting the sandbox attribute entirely, which gives the iFrame full permissions. Only use sandbox if you have a specific reason to restrict what the frame can do. Remember that the top-level domain — not the iframe’s src — is the one that must be verified for Apple Pay.

​
Acceptable use and terms

Merchants using Ecrypt’s hosted checkout with Apple Pay enabled must ensure their implementation complies with Apple’s Acceptable Use Guidelines for Apple Pay on the Web and follow Apple’s branding requirements in the Human Interface Guidelines and Marketing Guidelines. Among other things, you may not use Apple Pay on a site that violates any law or that involves restricted activities without Apple’s approval.

​
Resources from Apple

Apple Pay is a trademark of Apple Inc., registered in the U.S. and other countries and regions.