Wallets
Learn about wallet payments with Stripe.
Customers can use wallets to pay online with a saved card or a digital wallet balance. Retailers often use wallets to:
- Reduce fraud and increase conversion on mobile.
- Reach buyers in China, where wallets are the most popular way to pay.
Wallets might not be a good fit for your business if you sell subscriptions. Some wallets don’t support recurring payments.
Payment flow 
Customers confirm the transaction by authenticating their wallet credentials at checkout. If using mobile, they can authenticate with fingerprint or face recognition, their mobile passcode, or by logging into their wallet app. On the web, they can also scan a QR code with their mobile phone to complete the transaction.
Customer-facing mobile flow
Selects wallet at checkout
Enters wallet credentials
Gets notification that payment is complete
Customer-facing web flow
Selects wallet at checkout
Uses mobile to confirm payment
Gets notification that payment is complete
Product support
The following table shows which Stripe products support each wallet:
| Payment method | Connect | Checkout | Payment Links | Payment Element | Express Checkout Element | Mobile Payment Element | Subscriptions | Invoicing | Customer Portal |
|---|---|---|---|---|---|---|---|---|---|
| Alipay | 1,2 | Invite only | Invite only | ||||||
| Amazon Pay | 3 | ||||||||
| Apple Pay | 5 | ||||||||
| Cash App Pay | |||||||||
| Google Pay | |||||||||
| GrabPay | 1,2 | ||||||||
| Link | 6 | ||||||||
| MB WAY | 1,2,3 | ||||||||
| MobilePay | 1,2 | ||||||||
| PayPal | 3 | ||||||||
| Revolut Pay | |||||||||
| WeChat Pay | 1,2 | 4 | 4 |
1 Not supported when using Checkout in subscription mode.
2 Not supported when using Checkout in setup mode.
3 Not supported when saving payment details during payment (setup_).
4 Invoices and Subscriptions only support the send_ collection method.\
5 Checkout with ui_mode set to embedded supports only Safari version 17 or later and iOS version 17 or later.
6 The Payment Element doesn’t support Link in Brazil or India.
API support
The following table describes each wallet’s compatibility with API-based payment flows:
| Payment method | API enum | PaymentIntents | SetupIntents | Manual capture | Setup future usage1 | Requires redirect2 |
|---|---|---|---|---|---|---|
| Alipay | alipay | No | ||||
| Amazon Pay | amazon_ | Yes | ||||
| Apple Pay | No | |||||
| Cash App Pay | cashapp | Yes | ||||
| Google Pay | No | |||||
| GrabPay | grabpay | Yes | ||||
| Link | link | Yes | ||||
| MB WAY | mb_ | No | ||||
| MobilePay | mobilepay | Yes | ||||
| PayPal | paypal | Yes | ||||
| Revolut Pay | revolut_ | Yes | ||||
| Secure Remote Commerce | A comma-separated list of accepted card brands | Yes | ||||
| WeChat Pay | wechat_ | No |
1 Cards and bank debit methods including SEPA debit, AU BECS direct debit, and ACSS debit support both on_ and off_ with setup future usage. All other payment method types either don’t support setup_ or only support off_.
2 Payment methods might require confirmation with return_url to indicate where Stripe should redirect your customer after they complete the payment.