◐ PlutoPay Docs
API Reference Dashboard ↗

#Apple Pay & Google Pay

Apple Pay and Google Pay work across PlutoPay with no extra code — online and in person. They ride the same PaymentIntent as a card, so the platform fee and destination-charge routing are identical to a card paid the same way — online wallet payments are priced as online card, tap-to-pay as in-person card (both 3% today — see Fees). See Fees.

Apple Pay and Google Pay appear automatically on the PlutoPay-hosted payment page for hosted checkout and payment links — you don't add anything. The wallet button shows when the shopper's device supports it (Apple Pay in Safari on Apple devices; Google Pay in Chrome).

  • No merchant setup, no Apple Developer account, no Merchant ID. PlutoPay registers the checkout domain with Apple/Google on the platform side and handles merchant validation.
  • Works in test and live.
  • A wallet payment lands in your account exactly like a card — same fee as a card paid the same way, same webhooks (payment.succeeded).

#Using Elements on your own site?

If you embed our Payment Element on your own domain (rather than the hosted page), that domain must also be registered for wallets. Tell us the domain (apex and www) and we register it for you — no file to host in most cases.

#In person (Terminal)

Contactless tap-to-pay — including Apple Pay and Google Pay from a phone or watch — works on Stripe Terminal readers out of the box. No domain registration, no extra config: the shopper taps, and it flows through the same card_present payment with the in-person card fee (3%) to your account.

#Testing

  • Apple Pay: open the hosted checkout in Safari on an Apple device signed into Apple Pay (a test card in the wallet works in test mode).
  • Google Pay: open it in Chrome signed into a Google account.
  • Complete the payment → it succeeds, the fee for that payment method is captured, and it appears in your dashboard under the matching live/test mode.

Apple Pay only renders over HTTPS on a registered domain in a supported browser — if you don't see the button, check you're on Safari/Chrome on a supported device.