Wallet buttons where your buyers expect them.
Apple Pay and Google Pay appear on supported devices at checkout, tokenized through the same gateway as your card payments. Fewer fields to fill means fewer abandoned carts on mobile.
Included in Pro and above. Requires domain verification with your processor.
What you get
Native wallet payments without a second processor relationship.
Buttons on cart and checkout
Placement is configurable, so you can offer an express path from the cart or keep wallets inside the payment step.
Device aware display
The button only renders when the device and browser can actually pay, rather than teasing an option that fails.
Address and contact passed through
The wallet supplies shipping and billing details, which removes most of the form on mobile.
Same reporting as card
Wallet transactions land in the same gateway batch and the same WooCommerce reports, with the underlying card brand recorded.
How it works
Setup is mostly a verification exercise, done once.
- Verify your domainApple requires a verification file on your domain, issued through your processor. Google requires the site to be served over HTTPS.
- Enable the wallets in settingsToggle each wallet, choose the button style and placement, then save.
- Test on a real deviceThe sandbox cannot fully simulate a wallet. Use a test card in a real wallet on a real phone before going live.
Do not hide the card form
A wallet button that fails silently on an unsupported device is worse than no button. The card path always stays visible underneath, and the wallet is presented as the faster option rather than the only one.
Do I need a separate Apple developer account?
Do wallet payments cost more?
Can I use a wallet for a subscription?
Why is the button not showing?
Related
Other parts of the plugin people read next.
Start free, upgrade when the store needs it.
Install from WordPress.org, connect your gateway, take a real order today.