Your checkout loads and the card form is there, but the Apple Pay or Google Pay button is missing. Or it shows on your phone and not on a customer's. Usually nothing is broken. Stripe shows a wallet only when the buyer's device, browser, card and location all qualify and your account and checkout allow it. If one check fails, Stripe leaves the button out, without an error.
The most likely causes, from Stripe's, Apple's and Google's own documentation (checked 21 November 2026):
- The buyer has no card in Apple Wallet or Google Pay, is on an unsupported device or browser, or is in a private window.
- The buyer is somewhere Stripe does not show the wallet. For IP addresses in India, Stripe shows no Apple Pay at all and no Google Pay in live mode.
- Apple Pay or Google Pay is off in your Stripe Dashboard, or your checkout's code passes its own fixed list of payment methods.
- The payment form sits on your own website (Stripe Elements or embedded Checkout) and the domain is not registered with Stripe. Stripe-hosted Checkout and Payment Links do not need this.
- The wallet is there, just not where you looked: some Checkout settings move it into the list of payment methods instead of a separate button.
Test first: is it the device or the checkout?
Stripe publishes a wallet test page (docs.stripe.com/testing/wallets) with working demo checkouts. Open it on the device where the button is missing, in the same browser. If the wallet appears in Stripe's demo but not on your checkout, the cause is on your side. If it is missing from the demo too, the cause is the device, browser or location, and nothing in your account will change it.
Two habits spoil most self-tests. Stripe says not to use a Chrome incognito window or a Safari, Edge or Opera private window. And you do not need to pay to check: just see whether the button is offered. Stripe's testing page says its Services Agreement prohibits testing in live mode with real card details.
For a full test payment, use a Stripe sandbox with test keys. For Apple Pay, Stripe says to use a real card in Wallet; it returns a test token, so the card is not charged, and Stripe or Apple test cards cannot be added to Wallet. For Google Pay, a real card must be saved before the button appears; Stripe test cards then work through Google's test card suite.
On the buyer's side: card, device, browser
The conditions from Stripe's wallet testing guide, with Apple's own device list:
- At least one card in the wallet. For Google Pay, Stripe says any card saved to the buyer's Google Account counts, including cards from Google Play, YouTube, Chrome or an Android device. A buyer who never set Google Pay up sees no button.
- A compatible device. Apple lists iPhones with Face ID, or Touch ID except iPhone 5s; iPads with Touch ID or Face ID; Macs with Touch ID; Macs from 2012 or later with an Apple Pay-enabled iPhone or Apple Watch; and Apple silicon Macs paired with a Magic Keyboard with Touch ID.
- A supported browser. Stripe's browser table shows Apple Pay in Safari and in Chrome, Firefox and Edge on iOS 16 or later, never in Chrome on Android, and in other desktop browsers only when the site is set up for it. Google Pay shows in Chrome, Edge, Opera and Chrome on Android, and elsewhere only when the site is set up for it. Apple's pay-by-scanning-a-code option for other browsers needs iOS 18 or later and, in Apple's words, 'is not available in all markets'.
- Permission to look for saved cards. Stripe lists the switches: Safari, 'Settings', 'Advanced', 'Allow websites to check for Apple Pay and Apple Card'; Chrome on a computer, 'Settings', 'Autofill and passwords', 'Payment methods', 'Allow sites to check if you have payment methods saved'; Chrome on a phone, 'Settings', 'Privacy and security', 'Access payment methods'.
Where the buyer is, and the currency
Apple publishes the countries where cards can be added to Apple Pay, and Google a 'Pay online or in apps' list. Stripe's guide says to confirm the buyer is in a supported region for each.
India catches most sellers out. It is on both Apple's and Google's lists, but Stripe says that for IP addresses in India it does not display Apple Pay in any mode, or Google Pay in live mode. Stripe accounts based in India do not support Google Pay at all, and Stripe lists Google Pay's customer locations as 'Worldwide except India'. No setting on your side changes this; those buyers see the card form.
Currency is rarely the cause. Neither wallet has a shorter currency list on Stripe; both point to its general list of more than 135 presentment currencies. Stripe does say wallet buttons need a supported currency, so an unusual one is worth ruling out.
Your Stripe settings: are the wallets allowed?
Open the Payment methods page in your Stripe Dashboard settings (dashboard.stripe.com/settings/payment_methods) and check that Apple Pay and Google Pay are both on. Some methods switch on with 'Turn on'; others show 'Set up' or 'Review terms'. Stripe Checkout supports both wallets with no code changes, so on a Stripe-hosted page this switch is often the whole fix.
If someone built your checkout, ask whether the code chooses the payment methods itself. Stripe's default, dynamic payment methods, follows your Dashboard switches. Some setups pass a fixed list instead (the payment_method_types parameter), which Stripe says overrides the Dashboard. Apple Pay and Google Pay are not separate entries in that list; they come through as 'card'. A list without 'card' means no wallets.
Two Checkout behaviours make a working wallet look missing:
- With Stripe Tax, Checkout shows Google Pay only when it also collects a shipping address.
- The wallets move into the list of payment methods, rather than separate buttons, if the checkout requires terms of service acceptance, uses custom fields, requires a tax ID where supported, or the buyer's IP address is in Finland or Sweden and non-card methods are offered.
Domain registration: your own site, not Stripe's page
Stripe's Apple Pay guide draws a clear line. On Payment Links or Stripe-hosted Checkout, Apple Pay works with no additional configuration. On Elements or embedded Checkout, where the form sits on your own page, you must register every domain that shows the button. The same registration covers Google Pay and Link.
Check the address bar at payment. A page on checkout.stripe.com or buy.stripe.com is Stripe-hosted. If the card form is on your own website's address, register it:
- Open the Payment method domains page (dashboard.stripe.com/settings/payment_method_domains), click 'Add a new domain', enter it and click 'Save and continue'.
- Repeat for every version that shows the form: the bare domain, www (Stripe treats it as a subdomain to register too) and any shop or pay subdomain.
- Register in live mode; Stripe says that also registers the domain in sandboxes.
- Skip Apple's own merchant validation steps. Stripe handles them, including the Merchant ID and certificate signing request.
For whoever built your site
From Stripe's documentation for Elements and embedded Checkout:
- Prefer dynamic payment methods: drop payment_method_types. If you must list methods, include 'card' (Stripe's wallet guide shows allowed_payment_method_types with 'card'). API versions before 2023-08-16 need automatic_payment_methods on PaymentIntents.
- In the Express Checkout Element, paymentMethods.applePay or googlePay set to 'never' hides the button; 'always' shows it even when the wallet is not set up, and Apple Pay in non-Safari desktop browsers needs 'always'. The Payment Element's wallets option can hide them too.
- Serve HTTPS with a TLS domain-validated certificate, and for Chrome on Android send a Permissions-Policy header allowing payment for your origin, js.stripe.com and checkout.stripe.com.
- An iframe's origin must match the top-level page, except in Safari 17 or later with the allow attribute set to 'payment'; if domains differ, register both. Embedded Checkout's Apple Pay needs Safari 17 or later and iOS 17 or later.
- Open the Apple Pay sheet directly from the click, before any slow asynchronous code.
- With Connect direct charges, register the domain for each connected account through the API.
- Use the availablepaymentmethodschange event to see which wallets are available, and fall back to a card form.
Keep selling while you sort it out
A missing wallet costs buyers convenience, not the ability to pay: the card form still works. Meanwhile:
- Do not promise what you have not seen. If your page, ads or emails say Apple Pay is accepted, check on a real iPhone in Safari, or remove the line until the button shows.
- Ask a buyer who reports it which device and browser they used, and whether they opened your link inside a social app. Google's developer FAQ says its Google Pay readiness check always returns false in iOS web views, so the same link may show the wallet in Safari or Chrome.
- If you are rebuilding the checkout, pause paid ads that point at it until a sandbox test payment goes through.
- Keep a fallback, such as a Stripe Payment Link or an invoice, and keep your product files and customer list somewhere you control.
Selling from a OneSol page
OneSol is a link-in-bio page and storefront where buyers pay straight into your own Stripe, PayPal, Razorpay or Square account. Its card payments run on Stripe's own hosted checkout page, on your own Stripe account, so which wallets appear there depends on your Stripe payment method settings and the buyer's device, as Stripe's documentation describes. Stripe's own rules and country limits, including the India limits above, still apply.
