Apple Pay Desktop QR (Chrome)
Desktop Chrome Apple Pay via QR scan — iPhone Safari native sheet (Wasl QR pattern).
When a customer opens DigetPay Hosted Checkout in Chrome on desktop, Apple Pay is not presented as a native in-browser Apple Pay sheet. Instead, DigetPay displays a QR code that the customer scans with a compatible iPhone to continue the Apple Pay payment in Safari — the Wasl QR pattern.
Prerequisites: Apple Pay on Hosted Checkout — include
customerPhonewhen creating the payment link.
The customer must scan the QR code using the iPhone Camera or a supported Apple Wallet flow. The QR flow opens the hosted checkout on the iPhone so the customer can complete the payment using the native Apple Pay sheet.
Desktop Chrome does not display the native Apple Pay sheet directly. Do not expect an in-browser Apple Pay button on unsupported desktop browsers.
Customer flow
sequenceDiagram participant Desktop as Chrome Desktop participant Checkout as DigetPay Checkout participant iPhone as iPhone Safari participant Apple as Apple Pay Desktop->>Checkout: Opens redirectUrl in Chrome Checkout->>Desktop: Displays Apple Pay QR code Desktop->>iPhone: Customer scans QR code iPhone->>Checkout: Opens hosted checkout in Safari Checkout->>Apple: Presents native Apple Pay sheet Apple-->>Checkout: Customer authorizes payment Checkout->>Desktop: Session updated / completion flow
Steps for the customer
- Open the
redirectUrlin Chrome on desktop. - DigetPay Hosted Checkout displays the Apple Pay QR code when the desktop QR flow is supported.
- Scan the QR code using the iPhone Camera or supported Wallet flow.
- The hosted checkout opens on the iPhone in Safari.
- Apple Pay presents the native payment sheet.
- Authenticate with Face ID, Touch ID, or device passcode.
- Complete the payment.
- The checkout updates the payment session and continues the configured completion flow.
Merchant setup
No additional Apple Pay implementation is required for the desktop QR flow.
| Requirement | Detail |
|---|---|
customerPhone | Required in the Create Payment Link request |
| Merchant Apple Pay code | Not required |
| Domain verification | Not required for Hosted Checkout |
| Your checkout code | No changes required |
| QR generation | Handled by DigetPay |
Use the same POST /payment/checkout/intiate request described in Apple Pay on Hosted Checkout.
Browser and device behavior
| Customer environment | Expected behavior |
|---|---|
| Safari on iPhone/iPad | Apple Pay button → native Apple Pay sheet |
| Safari on Mac | Apple Pay available when supported by the device/account configuration |
| Chrome on desktop | Apple Pay QR code → scan with iPhone → continue in Safari |
| Chrome on Android | Apple Pay is not available; other supported payment methods may be displayed |
Testing the QR flow
Test the desktop QR flow in the Fin staging environment before production.
- Create a staging payment link using your Fin staging
x-api-key. - Include the required
customerPhone. - Open the returned
redirectUrlin Chrome on a desktop. - Confirm that the Apple Pay QR code is displayed.
- Scan the QR code using a compatible iPhone.
- Confirm that the hosted checkout opens in Safari.
- Complete the Apple Pay payment using the configured test Wallet card.
- Confirm the final transaction status using the Transaction Status API or your configured webhook.
Do not use production API keys, production merchant IDs, or production domains during Fin staging tests.
Troubleshooting
| Symptom | Likely cause | What to check |
|---|---|---|
| QR code does not appear | Apple Pay requirements are not met | Confirm customerPhone, browser support, and staging configuration |
| QR scan does not open checkout | Camera/browser or QR session issue | Scan using the iPhone Camera and confirm Safari can open the checkout |
| Apple Pay button missing on iPhone | Apple Pay unavailable on the device/account | Confirm Apple Pay is configured and an eligible card is available in Apple Wallet |
| Payment does not complete | Wallet/card or transaction issue | Check the Apple Pay authorization and verify the transaction status |
| Desktop session is not updated | Session/completion flow issue | Verify the configured checkout URLs and transaction status |
Important distinction
The desktop QR flow is a Hosted Checkout fallback experience, not a separate Apple Pay integration.
You do not need to add Apple Pay JavaScript, merchant validation, certificates, or domain verification to support it.
DigetPay handles the QR generation and hosted Apple Pay flow.
Next steps
Updated about 1 month ago

