#qaim
queen idol
mint plaza
👋 For the other message, can you elaborate on "send it at top level"?
Would be appreciated if I can see the errored request id req_xxx
regal prawn
Uncaught (in promise) IntegrationError: stripe.confirmPayment(): do not pass setup_future_usage at confirm time. Instead, pass setup_future_usage when the PaymentIntent is created.
at v3:1:76485
at v3:1:77212
at Array.reduce (<anonymous>)
at v3:1:77147
at v3:1:71934
at $ (v3:1:77540)
at ee (v3:1:77795)
at v.betas (v3:1:106558)
at y (v3:1:107528)
at v3:1:406083
which seems like the correct behaviour
mint plaza
Um so you can't change it right? Where did you "able to change it in confirm"?
regal prawn
so i was able to change it if i send it inside paymentmethod, error i was getting when i sent it at top level. So its working for me but i think it shouldnt work as it seems like a bug
payment_method_options: {
card:{
setup_future_usage: 'on_session'
}, this goes through
so im wondering now what else can i change. Can i change the amount associated with payment intent from client side?
mint plaza
Can you provide the request id when you changed it in top level?
I suppose you are referring to confirm in backend, correct?
regal prawn
no i can confirm from the frontend
also right now im in the process of integrating so on staging env not on prod
but when i confirm payment with this param
payment_method_options: {
card:{
setup_future_usage: 'on_session'
},
the customers card is saved and starts showing up in stripe dashboard which i can retrieve and make payments with
mint plaza
Um that one, could you find its request id in https://dashboard.stripe.com/test/logs and paste here?
regal prawn
let me create a new one and send you. i will first delete the payment method from my test customer bhisnu@zmail.com and then make a charge where payment intent is created without charge for later and complete is made with charge for later
pliant canyon
Hi! I'm taking over this thread.
pliant canyon
Indeed I see that setting setup_future_usage: "on_session" on the frontend worked here. And you think this should not be possible?
regal prawn
yes because now without showing the message in the iframe to user that we will chage his card later we can charge his card
although it works for my use case which is to show the user a checkbox to save his card for later in chich case i would append this attribute to the completePayment request
but i was wondering if this is the correct way to do it or it might be a bug im exploiting for my usecase
pliant canyon
I see. Give me a few minutes to look into this.
regal prawn
im also ging for lunch should be back in 30. Thanks for the help will wait for your reply
pliant canyon
So we did some investigation on our end, and the behavior you are seeing is expected. It's just are you are using an undocumented parameter with confirmPayment().
merry bobcat
👋 taking over for my colleague. Let me know if there's any follow-up Qs I can answer!
regal prawn
hey
sounds good then
only seems like an error
just one more small query. Is there a way to update an intent from clientSide? Because i dont want to allow anyone to alter the amount from front-end once its set in the backend
merry bobcat
you can actually update a PaymentIntent from the frontend https://stripe.com/docs/js/payment_intents/update_payment_intent but not really the amount or the currency or any of the sensitive data
regal prawn
thanks
but the link says page not found :9
😦
let me login and try again
thanks for all the help
merry bobcat
yes you're right, my bad
this is part of a beta feature and it's still not available for everyone yet
regal prawn
so i dont need to worry about anyone updating amount from client side once intent is created by server
merry bobcat
yes that's correct
merry bobcat
let me know if you need any more help
regal prawn
no thank a lot. Until next time, take care