To accept Apple Pay or Google Pay, check the sales channel, contracted service and integration. Being able to take a mobile payment at the counter does not confirm that the same options will appear on your website.
In-store and online payments
| Channel | What to check | Useful proof |
|---|---|---|
| Shop counter | Terminal and payment agreement | Terminal payment matched to the sale |
| Website | Merchant account, integration and buyer’s device | Available button, confirmed payment and updated order |
| Both | Configuration for each channel | Separate checks of both sales journeys |
Ask the bank or provider about your exact setup. Redsys’s Apple Pay documentation covers that integration; it does not establish compatibility with every website or terminal.
What if the wallet button is missing?
Before changing providers, review the merchant account, checkout configuration and device and browser support. Also check that the buyer has set up the wallet with a supported payment method.
Record where the test happened: device, browser, environment and merchant account. Seeing the button on one phone does not prove the same experience for every buyer.
Match payment to the order
For a fictional mobile purchase, look beyond the payment animation. Check the amount, the provider’s confirmed result and the order status. If payment is confirmed but the screen is stuck, investigate that same transaction before asking the customer to pay again.
For physical products, also check the delivery details you need. Using a wallet does not, on its own, guarantee those details are available.
Should you remove card payments?
Keep a suitable alternative when the wallet is unavailable. The aim is to help customers complete the purchase, not add as many buttons as possible. Our payment methods guide helps match the options to the sale.
Want to review your store’s options? Tell us the platform, bank and whether you sell in person, online or both.