Apple Pay and Google Pay: what has to be true before the button
Confirm four separate facts. The payment account must already be able to take the underlying card payment. The integration you installed must support that wallet. Every domain that shows the button must be registered where that integration requires it. A real device that meets the documented browser and wallet conditions must render the button. Stripe describes Apple Pay and Google Pay as wallets in the card-payment family, and its pages say Stripe accounts worldwide except India can accept them. That location statement is Stripe's payment-method availability. It is not a decision that a research-use-only business is eligible for an account, and it is not a Prism country list. A button does not approve processing. A missing button is not, by itself, a decline. Confirm any wallet-integration assistance separately; the relevant provider controls account and payment-method availability. Describe the work you need. Prism will confirm scope, responsibilities, fees, and terms before work begins.
For: An owner or authorized representative of a research-use-only peptide business deciding whether a wallet button can be offered on the checkout it actually runs.
Updated 2026-09-21
The button presents a saved card; it does not create an account
Stripe's Apple Pay page describes a wallet that pays with a card stored on an Apple device instead of a card number typed at checkout. Its Google Pay page says the customer pays with a card saved to a Google account. Google's Pay API overview says the button opens a payment sheet, Google returns a payment token, and the site's backend sends that token to its payment service provider. The provider still processes the purchase.
On the WooCommerce Stripe extension, express checkout is documented as similar to a card payment, and the card method generally has to be enabled before the wallet buttons are used. The extension documents one Link exception under its Optimized Checkout Suite. Apple Pay and Google Pay cannot be turned on separately from each other in that extension.
None of those pages says that showing the button approves a merchant, a catalog, or a research-use-only business. The provider still decides eligibility and account status. Prism's public services are a storefront review, processing preparation, and help with a provider's website questions. They do not include a wallet.
Domain registration depends on which integration you use
Stripe says Apple Pay on Payment Links or hosted Checkout needs no extra configuration. Apple Pay in Elements or embedded Checkout requires every web domain that shows the button, including subdomains such as www, to be registered once per account. Stripe says it handles Apple merchant validation, including the Apple merchant identifier, and tells Stripe users not to follow the separate merchant-validation process in Apple's own documentation.
Apple's implementation page says something different for a direct integration: set up the identifiers and certificates in an Apple Developer account, and contact the payment service provider about any further requirements. Use the instruction that matches the integration you run. If you use Stripe, Stripe's instruction is the one that says not to repeat Apple's merchant-validation process. If you do not use Stripe, this page does not describe that other provider.
Stripe's Google Pay web guide also requires each domain that shows the button to be registered, and the page must be HTTPS with a TLS domain-validated certificate. Google's Pay API getting-started list adds its own steps: the terms, a processor from Google's supported list or a direct integration limited to qualifying PCI DSS merchants, the brand guidelines, the checklist, and a request for production access in the Google Pay and Wallet Console. Production access at Google is not the card provider's underwriting decision. Direct integration is not available to a third party that only supplies gateway services, which is Google's rule, not a workaround.
A WooCommerce store has extra display rules
The WooCommerce Stripe extension requires a valid SSL certificate and the entire site on HTTPS. For Apple Pay it also requires port 443, TLS 1.2 or later, and the domain on the Stripe payment-method domains page. The extension creates the Apple domain-association file. Google Pay in that extension also requires the domain on that Stripe page.
The extension's customer guide says Apple Pay displays only when the shopper uses a compatible device, is logged in with an Apple ID, has a payment method on that Apple ID, and uses a compatible browser. Google Pay requires a compatible browser, a logged-in Google account, and a saved payment method. Stripe's own pages say that if device or integration requirements are not met, Stripe does not show the wallet. A test on one unsupported browser does not prove the button is off for everyone.
The extension's setup guide lists cases where the buttons are not shown, including a non-default product type, a pre-order charged on release, composite products, file-upload fields, free products, a variable subscription with an out-of-stock variation, and a product that does not need shipping when tax is based on the billing address. Its customer guide says simple and variable products are supported and lists other incompatibilities, including external products. If those two pages do not read the same way for a product you sell, check a current device. Do not pick the sentence you prefer.
What you can decide
You can decide whether the business wants the button, whether the live domain is one you control, and whether a real device renders it after the documented setup. You can bring that integration question to a consultation without sending credentials. Confirm implementation responsibilities separately; the provider decides whether the account may continue.
The provider decides eligibility, whether wallets are allowed on that account, and any fee or reserve. Stripe's published location limit, worldwide except India for both the Stripe account and the customer, is a payment-method availability statement. It is not evidence that any research-use-only merchant outside India is approved, and Prism does not publish a country list.
Unknown until you name the integration: whether a plugin other than the WooCommerce Stripe extension is what draws the button, whether Google production access has been requested, and whether a missing button is an unsupported device or a domain that was never registered. Leave the unknown row blank.
Wallet compatibility checklist
Complete one pass for the checkout you run today. A yes on the button row is not a processing approval. Worksheet entries are not submitted by this worksheet or saved by this site. Use only non-sensitive summaries; do not enter credentials, government identifiers, card or bank-account numbers, private receipt links, or customer details.
Worksheet entries are not submitted by Prism’s worksheet and are not saved by the site. Use record types, availability, anonymized observations, or match/mismatch results. Do not enter government identifiers, customer names or addresses, customer messages, receipt-access links, card or bank details, passwords, or keys. Send sensitive documents only through the provider’s verified secure channel.
Wallet compatibility checklist. The last column is for temporary notes.
Check
What the current docs say
Where to look
Your record
Underlying card account
What the current docs sayThe wallet presents a saved card. The WooCommerce Stripe extension generally requires the card method to be enabled. The button does not approve the business.
Where to lookThe provider account status, and WooCommerce, Settings, Payments, if that is the extension you use.
Which integration draws the button
What the current docs sayStripe hosted Checkout and a WooCommerce extension do not use the same domain steps. Apple's direct setup is a third path. Follow only the path you installed.
Where to lookThe plugin or hosted-checkout setting that is actually live.
Domains registered for the button
What the current docs sayStripe requires domain registration for Apple Pay in Elements or embedded Checkout, and for Google Pay on the domains that show the button. Hosted Checkout is the Apple Pay case Stripe says needs no extra Apple Pay configuration. The WooCommerce extension has its own domain step.
Where to lookStripe Dashboard, payment method domains, or the other provider's equivalent. Leave blank if you cannot open it.
Apple merchant validation
What the current docs sayStripe says it performs Apple merchant validation and says not to repeat Apple's own process. Apple's page still describes a developer-account setup for a direct integration.
Where to lookUse the instruction for the integration you have. Do not complete both by assumption.
HTTPS
What the current docs sayStripe Google Pay on the web requires HTTPS and a TLS domain-validated certificate. The WooCommerce Stripe extension requires the entire site on HTTPS.
Where to lookThe live store URL, not a staging URL that shoppers never use.
Google production access, if you use Google's API directly
What the current docs sayGoogle's overview says to request production access in the Google Pay and Wallet Console after testing. That request is not the card provider's underwriting.
Where to lookThe Google console, only if this store calls Google's API itself. Otherwise write not used.
Shopper device and saved card
What the current docs sayThe WooCommerce customer guide requires a compatible device, a signed-in Apple ID or Google account, and a saved payment method. Stripe hides the button when device or integration requirements are not met.
Where to lookOne supported device and one unsupported browser. Record both results.
Product and checkout limits in the WooCommerce extension
What the current docs sayThe setup guide and the customer guide list different cases where buttons are hidden or limited. A conflict is resolved by a live test, not by choosing a sentence.
Where to lookA product you actually sell, on the page where you enabled the button.
Stripe location limit
What the current docs sayStripe's Apple Pay and Google Pay pages say accounts and customers are worldwide except India. That is not a Prism country list and not an eligibility decision.
Where to lookThe provider's current page for the account you have. Another provider's rule may differ.
These are temporary notes. Leaving or reloading this page may clear them. The consultation form does not include these entries.
Limits
A Prism consultation can help you organize the facts and discuss the website or processing question. The payment provider decides eligibility, pricing, reserves, and whether an account is opened or closed.
A rendered wallet button is not processor approval, and a missing button is not a decline code.
A wallet implementation does not establish provider eligibility. Confirm account availability and any implementation scope separately.
Stripe Apple Pay — checked 2026-09-21. Apple Pay is a wallet. Hosted Checkout needs no extra Apple Pay configuration. Elements and embedded Checkout require each domain to be registered. Stripe handles Apple merchant validation. Stripe accounts and customers are worldwide except India. Stripe hides Apple Pay when device or integration requirements are not met.
Stripe Google Pay — checked 2026-09-21. Google Pay uses a card saved to a Google account. Web payments need HTTPS with a TLS certificate and domain registration. Stripe accounts and customers are worldwide except India. Stripe does not render Google Pay when device or integration requirements are not met.
Apple Pay implementation — checked 2026-09-21. A direct Apple Pay implementation uses Apple Developer identifiers and certificates. Apple tells the merchant to contact the payment service provider about additional requirements and to use a provider's Apple Pay SDK where the provider supplies one.
Google Pay API web overview — checked 2026-09-21. The button returns a payment token that the merchant's backend sends to its payment service provider. Getting started includes choosing a supported processor, or a direct integration limited to eligible PCI DSS merchants, and requesting production access in the Google Pay and Wallet Console.
WooCommerce Stripe express checkouts — checked 2026-09-21. The extension requires sitewide HTTPS. Apple Pay also needs port 443, TLS 1.2 or later, and a registered domain. The extension creates Apple's domain file. Apple Pay and Google Pay cannot be enabled separately. The card method is generally required. The page lists cases where buttons are not shown.
WooCommerce Stripe express-checkout customer requirements — checked 2026-09-21. Apple Pay and Google Pay display only on a supported device or browser when the shopper is signed in and has a saved payment method. The page also lists product types it supports and types it does not.
Prism solutions — checked 2026-09-21. Prism's public support is storefront review, processing preparation, and help with a provider's website questions. The provider decides eligibility and account terms. Any wallet-integration scope is confirmed through the inquiry.
Request a consultation
Describe the business and this specific question. Prism follows up by email to discuss fit and scope. An inquiry is not a processing application or an approval.