#druchan-3ds

1 messages · Page 1 of 1 (latest)

spare vigil
#

hello @gentle mango! can you share more on the issues that you're running into?

gentle mango
#

Yes. Our workflow is this:

  • user goes to our app, and tries to subscribe to a plan/pricing
  • the frontend generates redirects the user to a Stripe-hosted "Add card" page where we collect payment information
  • once Stripe adds the card, it sends a webhook. we use this to create a new subscription for the user from our backend

Stripe's documentation says that Stripe takes care of 3DS on the payment page automatically. On some payments, this doesnt appear to be true as we can see that once the customer adds the card, and we create a new subscription for them, the payment does not really go through. It returns with a 3DS error.

Also, since we rely on a combination of Stripe-hosted page and webhooks (instead of having a completely custom solution), we are not sure when and how to trigger a 3DS/confirm-payment workflow.

#

Sometimes, the first subscription payment succeeds but the following one fails, citing 3DS issues

spare vigil
#

can you give me an example of a payment that fails and returns with a 3DS error? i.e. the PaymentIntent id e.g. pi_xyz or even the Checkout Session id i.e. cs_...123

#

mutter...example : pi_123

#

the formatting keeps eating up my underscores

gentle mango
#

pi_1JAoerSJ5kKwEjHaGUg6qZGe

#

for example

spare vigil
#

gimme a while to look into this

#

@gentle mango this PaymentIntent is more than 30 days old, do you have something more recent?

#

to summarize though, yes, Stripe does handle 3DS automatically on the Stripe hosted checkout page on your behalf

#

i've taken a look at the payments on your account, that payment intent you provided, seems to have already been the most recent failed payment attempt

#

specifically
Recurring charges on AMEX are not supported for India-issued AMEX cards

gentle mango
#

Thanks Alex. Yes, the payment intent is old but we havent processed any further cards that had needed 3DS in India.

#

Let me try and find out nevertheless

gentle mango
spare vigil
#

since you're doing subscriptions, then yes, you can only use subscriptions with non-India issued AMEX cards

#

i don't know what was the exact details of what was sent in that email though

gentle mango
#

Okay

#

So I looked through our logs and couldnt find any <30days payments which failed due to 3ds.

#

Typically, what we see in such errors is that the paymentIntent comes back with "requires_action" message. But since this is a webhook, we aren't sure how to handle this on the frontend. Stripe docs say we should use the SDK to trigger a confirmPayment (or some such method) with the client_secret that comes as part of an invoice.

spare vigil
#

@gentle mango all payments in India require 3DS

#

so i would say that it's likely just a domestic AMEX card issue. What i would suggest is that you can put a message on your page / website reminding Customers that you cannot accept India AMEX cards for subscriptions to try to prevent this from happening in the future