Apple Pay on your checkout
Apple Pay needs a one-time domain verification in your Whop dashboard before it shows up in your app's checkout. Here's how.
Want Apple Pay to show up when customers check out in your app? It doesn't appear automatically — Apple requires a one-time domain verification before the Apple Pay button can render inside an embedded checkout. This is an Apple + payments-provider rule, not an OverSkill setting, so it happens in your Whop dashboard.
Good news: you only do it once per domain, and after that Apple Pay shows up on its own for anyone on a supported Apple device.
Why Apple Pay isn't showing yet
Your app's checkout is embedded — it runs on your own app domain (like yourapp.overskill.app or your custom domain). Apple only lets Apple Pay appear on an embedded checkout after the domain has been verified as one you control. Until that verification is done, the checkout still works perfectly with cards — the Apple Pay button just stays hidden.
You'll usually notice this as: card payment works, but there's no Apple Pay option even when you're on an iPhone or Safari with Apple Pay set up.
Can OverSkill turn this on for me automatically?
Not yet — and we're honest about that. Right now the verification lives in your payments dashboard (your own connected business), and there is currently no way for OverSkill to do it for you behind the scenes. We're working with our payments provider to make this automatic for every published app in the future. Until that ships, it's a quick manual step you do once.
How to turn Apple Pay on
- Open your Whop dashboard (this is your connected payments account — the same one you set up to accept payments).
- Go to Settings → Checkout, and find the Apple Pay for embedded checkout section.
- Click Configure, then Add payment domain.
- Enter the domain your app's checkout runs on (for example
yourapp.overskill.app, or your custom domain if you've connected one). - Choose a verification method:
- Whop-hosted verification (recommended for most people) — you'll temporarily update a DNS record, Whop confirms ownership, then you revert the DNS change. Apple Pay stays enabled after you revert.
- Self-hosted verification — for advanced users who'd rather serve the verification file themselves.
- Follow the wizard. Verification usually completes within a few minutes once DNS propagates.
Tip: If your app is published on more than one domain (say your .overskill.app address and a custom domain), verify each domain you want Apple Pay to work on.
After verification
Once your domain shows as verified, the Apple Pay button appears automatically — no rebuild, no re-publish. It shows up for customers who are:
- On a supported Apple device (iPhone, iPad, or a Mac using Safari)
- Signed in to Apple Pay with at least one card in their Apple Wallet
- Loading your checkout over HTTPS (all OverSkill apps already are)
Apple Pay does not appear in Chrome, Arc, or other non-Safari browsers on desktop — that's an Apple limitation, not something on your end.
Testing it
The easiest way to confirm it worked: open your live app checkout on an iPhone in Safari with Apple Pay set up. If it's verified correctly, the Apple Pay button appears as a payment option and you can run a real purchase with Face ID / Touch ID.
Still not showing after verifying?
If your domain shows verified but Apple Pay still doesn't appear on a proper Apple device in Safari, contact support and tell us your app and the domain you verified — we'll check the setup with you rather than leave you guessing.
What to read next
- Selling your app — turning on payments and collecting money
- Test your checkout without paying — confirm your checkout works end to end
- Payment fees explained — what you keep on each sale