#uhoh-card-detached
1 messages · Page 1 of 1 (latest)
uhoh-card-detached
Hey @frank schooner! Can you provide more details so that I can help you?
evt_1MlaiRRMcoXgMBBBCpEBZDNe
This is the event of the paymennt method.detach
Looking into it further, this is the request sent
req_rpxzfdu1ZvoUxD
However, nowhere in my code am I calling stripe.paymentMethods.detach(...)
So I'm confused why this event is being fired
https://dashboard.stripe.com/test/logs/req_rpxzfdu1ZvoUxD this is the request, this is your own code doing this 100%
Is there another way of detaching a payment method that I am not aware of?
kind of but that's irrelevant. Your code is 100% calling this API right now
Another question regarding subscriptions. If a customer pays for a Stripe Subscription, and the initial Payment Intent requires 3DS. If the customer succeeds the 3DS authentication, would the recurring payments from the subscription still require 3DS?
Well I am trying to find where in my code this would be happening. I don't see any .detach being called anywhere haha
Unfortunately I can't really tell you where the code lives but I can tell you with 100% confidence that your code is actively calling that detach API somewhere.
it depends on a lot of factors really. Some banks will always require 3DS, but in theory after the initial payment future payments can claim an "exemption" proving you did 3DS before and that you're now charging in a recurring way/off session.
Ultimately, you need to handle declines the same way if someone doesn't have enough funds or if someone's bank want 3DS again
Thank you!
you can't find any use of the word detach in your entire code base?
No, there is no use of it
But I am going through 3DS authentication for a subscription (I don't know if that helps?)