Around 60% of e-commerce traffic arrives on mobile. Mobile checkout completion rates are consistently 20 to 30 percentage points lower than desktop, not because phone users are less willing to buy, but because typing a card number on a small screen interrupts the purchase at exactly the wrong moment. Apple Pay and Google Pay exist to remove that interruption. One tap, one biometric confirmation, payment complete. No card number entered. No form fields.
The gap in completion rates between sellers who have wallet payments active and those who do not is not subtle. For traffic coming from Instagram Stories or TikTok, where almost every visitor is on a phone, the difference compounds fast.
If your traffic is already heavily mobile and you have not looked at that mix properly yet, the broader context is in why mobile-first selling matters so much for small sellers. Wallet payments matter because they remove friction exactly where most buyers are already coming from.
What the buyer actually sees
When a buyer opens a product page on an iPhone in Safari and the checkout runs through Stripe, an Apple Pay button appears automatically above the card input fields. Tapping it opens a confirmation sheet from iOS. The buyer sees the price, confirms with Face ID or Touch ID, and payment goes through. No email address required. No card number. No billing address form.
Google Pay on Android Chrome works the same way. Button appears, buyer confirms with fingerprint or PIN, done. Payment completes without form fields.
The buyer never types their card number. On mobile, card entry is the single highest-friction action in the checkout flow. Removing it is not a minor improvement. For impulse buyers arriving from a short-form video or a story, it is often the difference between a sale and a closed tab.
Apple Pay and Google Pay: the same idea, different ecosystems
Both do the same thing. The browser and the device determine which one appears.
Apple Pay shows in Safari on iPhone, iPad, and Mac with Touch ID. If a buyer is using Chrome on an iPhone, Apple Pay does not appear. It is a Safari-only feature on iOS because it uses the WebKit payment request API that Apple's browser exposes, and Chrome on iOS does not have access to it.
Google Pay shows in Chrome on Android. On iOS, Google Pay does not appear regardless of browser, because Apple Pay occupies that slot there. On Android, if the buyer is using Firefox or another non-Chrome browser, Google Pay does not appear either.
In practice: your mobile buyers are almost always in Safari (iPhone) or Chrome (Android). Those are the two browsers that matter for wallet payment coverage.
| Payment method | Device | Browser | Appears? |
|---|---|---|---|
| Apple Pay | iPhone | Safari | Yes |
| Apple Pay | iPhone | Chrome | No |
| Apple Pay | iPad | Safari | Yes |
| Apple Pay | Mac (Touch ID) | Safari | Yes |
| Apple Pay | Mac | Chrome | No |
| Google Pay | Android | Chrome | Yes |
| Google Pay | Android | Firefox | No |
| Google Pay | iPhone | Any | No |
| Both | Desktop (Windows, Linux) | Any | No |
Desktop buyers do not see wallet payment buttons. They get the standard card input form. That is expected, not a bug.
How activation works
There is no configuration step. No developer setup. No SDK to install.
Stripe supports Apple Pay and Google Pay natively. When a checkout is built using Stripe's payment widgets, wallet payment buttons appear automatically for any buyer on a supported device and browser. You do not "install" Apple Pay. You connect Stripe, and Apple Pay is already part of what Stripe delivers to the browser on eligible devices.
With NanoCart, this means wallet payments activate when you connect a Stripe account. Nothing else to do. Open your product page on an iPhone in Safari and the Apple Pay button is already there.
If Stripe itself is not set up yet, do that first. The exact verification and activation sequence is in the Stripe setup guide for beginners.
Klara sells handmade skincare products from Amsterdam via Instagram Stories. Around 70% of her traffic is mobile. She connected Stripe when she set up her NanoCart page and did not think about wallet payments specifically. Three weeks later, she checked her Stripe dashboard and found that 4 of every 10 mobile purchases had been completed through Apple Pay. Her checkout completion rate had moved from around 4.2% to 6.1% during that period. She had not changed anything on her product page.
How to check that it is working
Most sellers assume wallet payments are active because they think they should be. That assumption is worth testing explicitly. Stripe account verification status, browser version, and regional availability can each affect whether the buttons actually appear.
What to do when a button does not appear
There are a few common causes, each with a different fix.
If Apple Pay does not show on your iPhone: confirm you are using Safari and not Chrome or another browser. Next, check that Wallet and Apple Pay are enabled in iPhone settings under Wallet and Apple Pay. If both are fine, the most likely cause is incomplete Stripe account verification. Stripe restricts wallet payments in live mode until verification is finished.
If Google Pay does not show on Android Chrome: confirm that you have a card saved to Google Wallet. The button only appears when the buyer has a saved payment method in their Google account. A buyer who has never set up Google Wallet will not see it.
If neither appears: you are probably in Stripe test mode. Apple Pay and Google Pay in test mode require additional domain registration that most sellers skip. Switch to live mode and do a real small test purchase, then refund it. Test mode is not a reliable environment for checking wallet payments.
If your Stripe account is not fully verified yet: wallet processing is restricted until Stripe confirms your business details. Complete the verification checklist in your Stripe dashboard. This is the most common cause when everything else looks correct.
And if you are still unsure whether Stripe is the right primary processor for your audience, compare the tradeoffs in Stripe vs PayPal for small sellers in Europe. In practice, wallet checkout is one of Stripe's clearest advantages on mobile.
Does the device split matter for your specific audience?
Check where your traffic actually comes from before assuming the Apple to Android ratio.
In the UK, Germany, France, and the Netherlands, iPhone market share among online buyers is high, often above 55%. In Poland, Czech Republic, and many other Eastern European markets, Android is dominant. If 70% of your audience is German buyers arriving from Instagram Stories, a disproportionate share will be iPhone users. Apple Pay is the more important button to verify first.
For creators whose traffic comes from TikTok, the audience skews younger and the Android to iOS split is roughly even. Both buttons matter roughly equally.
Tomasz sells hand-painted prints from Warsaw via Instagram and Etsy. He checked his analytics after 3 months on NanoCart. His traffic was 65% Android. He had been testing Apple Pay on his own iPhone and assumed that was the main wallet payment to track. His Stripe dashboard showed the opposite: Google Pay was responsible for nearly all his wallet-based completions. He had been confirming the wrong button.
The fix was to ask an Android-using friend to check the page. That took 5 minutes. Now he tests both.
Your quick action plan
If you have not confirmed wallet payment status on your product page, run this now. It takes around 10 minutes.
- Connect Stripe to your product page if you have not done so. Wallet payments activate as a result, not as a separate configuration step.
- Open your product page on an iPhone in Safari. Go to checkout. Confirm that an Apple Pay button is visible at the top of the payment options.
- Find a friend with an Android phone and Chrome, or use your own Android device. Send them your link, ask them to check if Google Pay appears at checkout.
- Log in to Stripe after your next 5 to 10 purchases and filter payments by method. Look for Apple Pay and Google Pay entries. This confirms the full flow is working end to end.
- If wallet buttons do not appear: confirm live mode is active, check Stripe account verification is complete, and verify the correct browser is being used for each test. That covers the large majority of cases.
Mara sells embroidery patterns from Ljubljana via her Instagram bio. She connected Stripe, created her NanoCart page, and did not specifically configure anything for payments. In her first week, 3 of her 8 sales came through Apple Pay. She had not heard of checking whether it was enabled.
That is the common experience. Wallet payments work automatically when Stripe is connected. The part most sellers miss is confirming it, and catching the edge cases when it does not.