#erangalp-connect-payment-element
fading beacon
Hi Bismarck!
sullen path
Wallets are on by default with Payment Element (they correspond with the card payment_method_types that you would set server-side). However, if you don't want these wallets then you can set them to never when you create your Payment Element: https://stripe.com/docs/js/elements_object/create_payment_element#payment_element_create-options-wallets
fading beacon
I see! Weird that it only shows up now, we've been testing it all along in the same browsers.
Appreciate the assist!
One more question on this then, this is set up with a SetupIntent - is it possible to save a card from a wallet as a payment method to a customer?
Also, I'm not quite sure how to test the wallet, since it seems to pull up my actual Google Wallet when I click on it (though this is in test mode)
sullen path
It requires HTTPS and a real card in the google wallet
So if you were just testing locally before it wouldn't show
fading beacon
That makes sense
sullen path
Yep you can save a card using these wallets!
You are totally safe to test it out. We will swap out your real card for a 4242 test card as long as you are using your test keys
sullen path
Sure thing!
fading beacon
@sullen path I just tested it, and it ended up adding my actual card from the wallet - it wasn't swapped, see the payment method pm_1LZejmFqJ5RRTcXtFblCTDIU on the aforementioned account
sullen path
👀
Yeah so what you are seeing in the Dashboard is the last4 which is the actual last 4 digits of your stored card. However, the DPAN (the dynamic_last4: https://stripe.com/docs/api/payment_methods/object#payment_method_object-card-wallet-dynamic_last4) is the 4242 card.
If you create a payment using that test card now you would see it use the DPAN.
Your actual card would not be charged
fading beacon
I assumed that any charge in test mode would not charge the real card, but just wanted to confirm what I'm seeing. Appreciate the explanation!