Testing tool

See which payment methods appear

Open a real HandyPay test-mode Checkout on this device. Stripe determines what is eligible at that moment, so the result is more useful than a browser guess.

Test mode · US$1.00

Test this browser

Google PayApple Pay

The checkout—not this page—performs the real wallet check. It uses Stripe's current eligibility rules for your browser, device, wallet, region, and the test purchase.

Browser

Checking…

Device

Checking…

Connection

Checking…

Open test checkout

Opens Stripe Checkout in a new tab. Inspect the methods, then close it. Do not approve a real wallet card; completing the flow is only for Stripe or Google test-card suites.

Read the result

The wallet appears here and in your integration

The customer's browser and wallet path are working. No wallet-specific WHMCS field or webhook handler is needed.

The wallet appears here but not in your integration

Check the merchant payment-method configuration, session currency and amount, funds flow, and whether the session uses dynamic payment methods.

The wallet is missing here too

Fix the device, browser, wallet, card, privacy-mode, or regional prerequisite first; changing your integration will not solve that setup issue.

Google Pay checklist

Google Pay
  • Add at least one active card to Google Wallet. Stripe requires a real card in the wallet before Google Pay renders, even in test mode.
  • Use a compatible device and a current supported browser outside a private or incognito window.
  • In Chrome, allow sites to check whether you have saved payment methods under Autofill and passwords → Payment methods.
  • Use HTTPS and test from a supported Google Pay region. Stripe does not render Google Pay for an IP address in India.

Google Pay is processed as a card wallet. Existing HandyPay Checkout sessions, payment events, and WHMCS invoice reconciliation continue to use the normal card-payment flow.

Methods you may see

MethodWhat affects whether it appears
Google PayA compatible browser and device, an active card in Google Wallet, browser wallet access, and a supported region.
Apple PayAn Apple Pay-capable device, an active Wallet card, supported browser settings, and biometric authentication.
Amazon PayAvailability for the Stripe account, buyer location, currency, and current Checkout session.
Cash App PayA supported buyer location, currency, device, and eligible Checkout session.
LinkStripe eligibility for the customer and session; a returning customer may see a faster saved checkout.
CardsThe baseline checkout option and the fallback when another method is not eligible.

This tester uses a US$1 test purchase and HandyPay's platform test configuration. A merchant's country, account configuration, currency, and invoice can produce a different list.

Stripe custom payment methods are different.

A cpmt_… entry gives Payment Element a name and logo for a payment handled by another processor. It does not enable that method, and it is not compatible with Checkout Sessions, so it will not appear in this tester or HandyPay's current WHMCS checkout.

How Stripe custom methods work

Check your integration

Hosted Checkout needs no separate Google Pay code.

HandyPay omits a manual payment-method list so Stripe can dynamically select eligible methods. Create a fresh test session when you compare results; an older session does not pick up every configuration change.