
Payment Methods
Part of Mobile checkout
Testing wallet payments on supported Apple Pay devices
Test a wallet in the device and browser combinations where customers can actually use it.
undefined
Test wallet payments against the device and browser combinations each provider supports. For Apple Pay sandbox testing, use the named device models and sandbox setup; Google Pay has a separate TEST card suite for checking payment flows (developer.apple.com; developers.google.com).
Check supported devices before testing
Build a test matrix with the payment provider, domain setup, wallet, device, browser, card and product type. For Shopify’s online-store Apple Pay flow, the provider must support Apple Pay, the store domain needs SSL, and customers must use Safari on a compatible Apple Pay device. Subscription purchases add requirements: Shopify Payments, a Mastercard or Visa, and a compatible subscription app; private-store access blocks digital subscription purchases.
Apple’s sandbox testing device list names iPhone 6 or later, iPad mini 3 or later, iPad Air 2, iPad Pro and Apple Watch (developer.apple.com). Use these models for Apple Pay sandbox tests, rather than treating the list as universal compatibility guidance for every wallet, browser or checkout.
Before a real wallet flow, add the card to Apple Wallet or Google Wallet and complete issuer verification if requested. Google Wallet’s add-card flow can scan the card or accept details entered manually.
Google Wallet can be accessed from any Android device. Samsung Wallet is available only on Samsung devices, so include it only where the payment provider and checkout offer it.
For Shopify’s online Apple Pay checkout, use Safari on a compatible device. For other combinations, use only those the payment provider lists as supported; success in Safari does not establish support elsewhere. Braintree says to use Safari or Chrome to test Apple Pay on the web (developer.paypal.com).
Apple Pay testing needs access to a physical device. It must be able to interact with secured screens, such as screens requiring a passcode before the next stage (perforce.com).
Apple Pay sandbox testing uses test credit and debit cards; real cards must be used in production. It requires an App Store Connect sandbox tester account. For web implementation, register a merchant ID, create certificates and verify the website domain; sign out of the Apple Account on testing devices and sign in with the sandbox tester account. Set the device region to a country or region that supports Apple Pay (developer.apple.com).
Use the payment provider’s documented test path. Judopay API payments or pre-authorisations can carry a token from an Apple Pay session or a payment token generated by the Google Pay API.
For Braintree Apple Pay tests, Safari or Chrome can be used on the web. Its sandbox accepts Apple Pay Sandbox test cards from the device, which must be signed in to an iCloud sandbox tester account; the sandbox returns a payment method nonce with dummy data (“Jane Doe”) even when decryption succeeds (developer.paypal.com).
Judopay recommends a production environment and live cards for successful Apple Pay and Google Pay DPAN end-to-end tests, including pre-authorisations. Use a unique wallet payload for each test because production payloads can be used only once. Judopay says decline scenarios for wallet payments cannot be tested in the sandbox environment (docs.judopay.com).
Google Pay’s test card suite lets developers test integrations and APIs in TEST environments without real credit cards. Join the suite group to replace real cards with test cards in the payment sheet; when the environment is set to TEST, the sheet displays the suite by default (developers.google.com).
For an in-store Google Pay test, make a low-value transaction on a supported NFC terminal and check that transaction notifications are generated.
For Adyen, enrol the wallet in Google’s test card suite. It pre-populates the wallet with cards for the TEST environment, and each card is marked for its scenario; cards outside the suite are mapped to an Adyen test card of the same brand (docs.adyen.com).
Include failure and fallback
Start from the product and cart, then try the express button and the wallet option inside checkout where available. Before confirming, check the shipping address, rates, tax, discount and final amount; change the address in the wallet and verify that the store recalculates correctly.
With Apple Pay, the customer taps or clicks the button and uses a fingerprint or Face ID; the device sends payment information to the provider without the customer manually entering card or shipping details. After a successful test, check the confirmation email and order record against the final amount.
Test cancellation, an unavailable wallet, failed authentication and return to the ordinary card form; confirm the cart remains and no duplicate order is created. For an eligible Google Pay gateway test suite, choose a card marked for the relevant scenario and check its expected response; Judopay says decline scenarios for wallet payments cannot be tested in the sandbox environment (developers.google.com; docs.judopay.com).
Record which provider, domain, wallet, device, browser, card and product combinations were exercised, and which were not. Do not claim universal support from a vendor logo or simulated screenshot.
Further reading: Testing Digital Wallet Payments - via API (docs.judopay.com).



