#malware_api
dusky violetBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1335922629575577610
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
outer mist
👋 happy to help
do you mean you want to charge your customer for off-session payments ?
outer mist
are you passing off_session: true when creating the PaymentIntent?
teal fox
Sorry i mean saving the payment method.
actually the susbcriptions are working. But we are not able to save the payment method on our side, when we attempt that, it triggers a re-auth.
dusky violetBOT
tame elm
Hey! Taking over for my colleague. Let me catch up.
teal fox
sure
tame elm
actually the susbcriptions are working. But we are not able to save the payment method on our side, when we attempt that, it triggers a re-auth.
Can you provide more details how are you "saving the payment method"?
Do you have an example? is it in live mode or test mode ?
teal fox
test mode
tame elm
What about the other question please ?
teal fox
on the payment form, when user selects google pay (or apple pay) we are hiding “save my payment info” checkbox currently because of this issue or re-auth. basically we are disabling the payment method save option at that step. Then user submits the form. charge is created. then if user wants to opt in for membership, a modal appears. user sees google pay button again there. to accept membership, they click the google pay button, then google pay pop up appears. they accept on that pop up, and then we save their payment method for off_session and create membership.
for saving the payment method, we create a customer object, create a payment intent during the transaction and set off_session for future use.
tame elm
Just to make sure we are following each other, you are following this guide then:
https://docs.stripe.com/payments/save-during-payment?
If so, what test card are you using during your tests ?
teal fox
yes that is how we are able to save payment methods like credit cards etc. Just to clarify we are able to save wallets like apple pay and google pay as well but we want to avoid that re-authentication step everytime the user tries to save the wallet payment method.
tame elm
You should avoid re-auth if you are following that flow correct.
What test Card number are you using ?
teal fox
it is not a card, as I said it is Google pay. Do you mean the card which is added in Google Pay?
dusky violetBOT
teal fox
Yes but the card is added in the customer app or account which is not a problem here. The problem is we have the card added in the Gpay account and all that is working. What the issue is "saving the wallet as payment method" during checkout triggers a re-auth
rigid nymph
Some examples of API requests, errors that demonstrate the problem would be helpful here
teal fox
there are no errors. The problem I am trying to solve is that, when the user tries to save the wallet payment method during checkout, there should be no re-aut for that particular save process like we do with saving credit cards.
rigid nymph
Again, an example of when this occurs: the pi_xxx or an object