Skip to main content
This page compares four Apple Pay integration options and their different requirements for runtime environment, frontend work, and token handling. Waffo supports Apple Pay through hosted Checkout and Merchant-built payment experiences.

​
Choose an integration option

​
Option 1: Redirect to Waffo Checkout

Call /api/v1/order/create, parse orderAction from the response, and open orderAction.webUrl in the browser’s top-level page. Waffo Checkout displays Apple Pay in this option. You don’t integrate Apple Pay JS on your page or handle an Apple Pay token. Use the Webhook or the /api/v1/order/inquiry result as the source of truth for payment status.

​
Option 2: Load Waffo Checkout in an App WebView

Open orderAction.webUrl in your App WebView. Send userTerminal=APP when creating the order so Waffo returns a link suitable for an app.

​
Option 3: Load Waffo Apple Pay Checkout in an iframe

An iframe integration must use the Waffo frontend SDK @waffo/payment-sdk. Before integration, contact Waffo technical support to complete Apple Pay domain verification and registration. Do not load orderAction.webUrl in a plain <iframe>.
The frontend SDK renders and manages the Checkout iframe on your page. Your integration must also meet the Checkout iframe requirements for allow="payment", Referrer Policy, and responsive layout. See Frontend SDK usage and iframe embedding considerations. Do not launch iframe Apple Pay before domain verification and registration are complete. The Apple Pay button may not appear, or payment authorization may not proceed.

​
Option 4: Integrate directly with Apple Pay

For the complete prerequisites, decryption steps, and pass-through format, see Direct Apple Pay integration.