Apple Pay in hosted checkout: how EPD Commerce handles it
EPD Commerce now supports Apple Pay inside hosted checkout, giving customers a one-click payment path on any compatible Apple device or browser, while the platform handles every piece of merchant onboarding and verification behind the scenes.
What this feature does and who it helps
Checkout abandonment is largely a friction problem. Customers who have to re-enter a card number they already have stored in their phone often don’t. Apple Pay closes that gap by letting buyers authorize a purchase with Face ID or Touch ID, without retyping anything.
For merchants on EPD Commerce, the benefit runs in both directions:
- Customers get a faster path to purchase.
- Merchants get a wallet payment option that is fully set up at the platform level, with no separate Apple Pay merchant ID registration required on their end.
How the platform manages onboarding
Most wallet integrations put the setup burden on the merchant: register a merchant ID, verify domain ownership, configure certificates, pass those credentials into the processor. EPD Commerce takes a different approach.
Apple Pay onboarding and merchant verification are managed at the platform level. Merchants do not go through the Apple registration process independently. The platform handles domain verification and credential management, then passes correctly formed payment tokens to the underlying processor for authorization.
Visa-backed Apple Pay network tokens are supported, which means the token passed through the network carries the card’s network-level credential rather than a static card number. That matters for authorization rates and for recurring billing flows where token continuity affects success.
Supported environments
Apple Pay appears in checkout only where the device and browser combination actually support it. Displaying the button in an unsupported environment and then failing at authorization is a bad experience. The platform resolves this by rendering the Apple Pay option conditionally, based on environment detection.
Supported environments at launch:
- Safari on iPhone and iPad
- Safari on Mac
- Chrome on iPhone and iPad
- Edge on iPhone and iPad
- Firefox on iPhone and iPad
- Chrome on Mac, where Apple Pay browser requirements are met
- Compatible Apple WebKit browser environments
If a customer arrives in a browser or on a device that does not meet these conditions, the Apple Pay button is not shown. The rest of checkout is unaffected.
Transaction handling: auth, capture, refunds, and voids
Apple Pay transactions inside EPD Commerce follow the same authorization, capture, refund, and void workflows as card payments. If a transaction is declined, canceled, or fails at the processor, the customer returns to the checkout session without losing their cart or session state. No re-entry, no lost context.
Wallet transaction indicators are available in transaction reporting, so Apple Pay activity is visible alongside all other payment types in the same reporting view. There is no separate dashboard or export needed.
For merchants running subscriptions, Apple Pay supports recurring billing on processors that handle recurring Apple Pay credentials. Processor-managed recurring credential handling is supported where available at the processor level. Which processors support this at launch is still being confirmed as the feature moves through beta.
Sandbox and testing
A sandbox and test environment are included. Developers building against the EPD Commerce checkout flow can test Apple Pay transactions without live credentials, using the same environment structure that covers other payment methods.
For technical reference on the Apple Pay on the web specification, see Apple’s developer documentation for Apple Pay on the web.
FAQ
What is Apple Pay in EPD Commerce hosted checkout?
Apple Pay in EPD Commerce hosted checkout is a wallet payment option that lets customers authorize purchases using Face ID, Touch ID, or their device passcode, without entering card details manually. It is available in Beta ahead of EPD Commerce’s public launch.
Do I need to register a separate Apple Pay merchant account to use this?
No. Apple Pay onboarding and merchant verification are managed at the platform level by EPD Commerce. Merchants do not register independently with Apple or manage their own merchant IDs or domain certificates.
Which browsers and devices show the Apple Pay button?
Apple Pay appears in Safari on iPhone, iPad, and Mac; Chrome on iPhone, iPad, and Mac (where Apple Pay browser requirements are met); Edge on iPhone and iPad; Firefox on iPhone and iPad; and compatible Apple WebKit browser environments. The button is not shown in unsupported environments.
Do Apple Pay transactions appear in my reporting alongside other payments?
Yes. Apple Pay transactions appear in the standard transaction reporting view with a wallet transaction indicator. No separate report or export is needed to see wallet activity.
Does Apple Pay work with subscriptions and recurring billing?
Apple Pay supports recurring billing on processors that handle recurring Apple Pay credentials. Processor-managed credential handling is supported where the underlying processor allows it. Specific processor support is being confirmed during the beta period.
Get Access to EPD Commerce before public launch: epd.com#apply