#ketaaa
1 messages ยท Page 1 of 1 (latest)
thanks Toby
I'm passing off_session as option when creating the payment_intent
when I try to charge the card again i'm facing the error "Authentication required"
with the payment_method token "pm_XXX"
Im using this testing card
4000002500003155
Can you share the ID of the Payment Intent where you encountered the error?
Looking at the Payment Method that you used there, I see that shortly before you created pi_3LGOf3KrJlAuB9hq1KframJA, a request was made to update the Payment Method. I'm not certain, but I think that may reset the authentication requirements. Can you try your flow again but not update the Payment Method in between payments and see if the second payment avoids authentication?
Sure?
I wanna try the case where the third recurring is bugging
like First payment ok, second payment using token ok
third payment using token fail with insufficient funds
is it possible?
Yes, but you'll need to swap the Payment Method that is being used in between. If this is testing for Subscriptions, then I would recommend leveraging our Test Clock functionalities to help simulate those:
https://stripe.com/docs/billing/testing/test-clocks
okay thanks i will have a look, i keep you updated regarding the recurring token with 3ds
i'm testing now
pi_3LGPEDKrJlAuB9hq2Wodj1OL
same
without update the PaymentIntent
it still require authentication on the re-charge with the token
oh I see it's my second charge request that update the first payment intent
i will investigate further on this update and get back to you if it resolved the issue or not
Just to clarify, it's not the Payment Intent that I'm suggesting you avoid updating, it's the Payment Method.
understood
debugging the code right now, i think in 10-15 min i have the answer
@merry steeple setup_futur_usage have to be level 0 of the payload or can be in the payment_method_options array?
Either, the top-level one controls the default behavior for the intent, and the nested ones allow you to override that for specific types of payment methods.
thanks!
can you send me the request that update the payment method in the log please?
i dont see it in my payment_intent
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
are you talking about that?
Yup, that looks like one of the ones that I was seeing.
okay thanks
@merry steeple
pi_3LGPxNKrJlAuB9hq21GONHYc
here is the new PI without the PM update call
still trigger authentication
can you have a look please?
๐ stepping in here for toby as they need to step away
If you can recap that would be really helpful
im trying to do recurring payment using pm_token
it works very well for no 3ds payment
for 3ds secure payment, it trigger me authentication
it can't charge the payment
Thanks, let me look at the above
when i create the initial payment intent i'm well passing off_session for card
and using the pm_token received in the charge event through a webhook
Okay so the above example should be the initial set up, no?
yeah it is
However, I'm not seeing that go through 3DS at all
pi_3LGPusKrJlAuB9hq0M2x7ZnP
is the initial payment
and pi_3LGPxNKrJlAuB9hq21GONHYc is the recurring
we see well that the recurring is redirecting to the 3d secure authentication
On the recurring you aren't setting off_session: true and confirm: true
When you set setup_future_usage again then it will attempt to set it up again
oh i understand
so in the recurring payment intent creation i have to add "off_session = true " and confirm = true at level 0 of the payload?
or under payment_method_option key?
Yep top level
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
Sounds good
The cart details have changed. Please refresh the page and try again
Payment succesfully passed
but I have this error aswell
Well that is your own error, no?
pi_3LGQVCKrJlAuB9hq0Kd0dqWn
i think yeah coming from the application itself
on your side, all is good regarding this payment intent?
Yep