Express Checkout Wallets (Apple Pay & Google Pay)
Apple Pay and Google Pay let buyers check out with a saved card and a fingerprint/face scan — no card entry. Each wallet shows its button only on a domain registered for it: Apple Pay needs proof that you own the domain (a hosted file), and Google Pay needs its own entry for the domain, with no file. This guide explains the one-time activation per wallet, and who does what.
You manage all of this from the Wallet Domains page in your Von Payments dashboard: add a domain, download its verification file (Apple Pay), host it, and click Verify. The whole ceremony is self-serve and takes about five minutes per domain — no support request needed.
Who does what
| Step | Who |
|---|---|
| Add the domain + download the file + click Verify | You (in the Wallet Domains dashboard) |
| Host the file at the exact path on your web server | Your developer (one static-file deploy) |
| Register the domain with Apple and run its check (Apple Pay), or re-read your Google Pay setup (Google Pay) | Von Payments (when you click Verify or Re-check) |
How domain entries work
The same rules apply in the dashboard and through the wallet-domains API (walletDomains in the Node SDK, wallet_domains in the Python SDK):
- One entry per domain and wallet. Apple Pay and Google Pay on the same domain are two entries. Registering the same domain and wallet again returns the existing entry.
- The entry id never changes. Each entry has a
vp_wdv_*id that stays the same for the life of the entry, including across re-checks, so you can store it. Treat it as opaque. - One check per 30 seconds per domain and wallet, whether you click Verify / Re-check or call the verify endpoint.
- Verified means the button can show on that domain. Whether a wallet payment then goes through depends on your payment account's wallet setup, so run one payment end to end with each wallet before you rely on it.
- Failed entries say why: Why a check failed lists every reason and what to do.
Apple Pay — needs domain verification
Apple requires a verification file hosted on each domain. The steps, hosting recipes for common frameworks and troubleshooting are in Apple Pay domain setup.
Google Pay — no file, but its own entry
Google Pay has no file to download or host. The domain still needs its own entry with Google Pay selected: the button is turned on per domain and per wallet, so check the domain's list and add a Google Pay entry if there is none.
The entry is checked as soon as you add it and reads Verified when Google Pay is set up on your payment account. If it reads Failed because Google Pay is not set up yet, turn it on from the domain's page (if the Apple Pay & Google Pay add-on is off, turn that on in Von Pay features first); the entry is re-checked straight away. Re-check (or the verify endpoint) refreshes it any time later; there is no file to host.
Keeping it working
- Add every domain you serve checkout from — apex and subdomains are separate (
yourstore.com≠checkout.yourstore.com), and staging domains need their own entry. - Leave the Apple Pay file in place (why).
- Watch the dashboard. Each domain shows its status (verified / pending / failed / expiring soon) and the date of the last buyer-side failure, so a silently-broken domain doesn't sit unnoticed.
Troubleshooting
| Symptom | Fix |
|---|---|
| Button doesn't appear | The domain isn't Verified yet, or the buyer's device/browser doesn't support that wallet (Apple Pay needs Safari/iOS; Google Pay needs a Google account; from vora.js 1.51.1 it also works in Safari and Firefox). |
| An entry is Pending or Failed | The domain's page says why; see Why a check failed. |