#sina

1 messages · Page 1 of 1 (latest)

heavy veldtBOT
tired notch
#

Hi there, is you question about how to handle a PaymentIntent when its status becomes requires_action ?

silver cave
#

Yes

tired notch
#

There are two ways

  1. If you have a frontend integration, you can call stripe.confirmPayment() (https://stripe.com/docs/js/payment_intents/confirm_payment) to let Stripe.js to initiate the 3DS flow so that you customer can authenticate the payment
  2. Enable the Send a Stripe-hosted link for customers to confirm their payments when required option in the billings settings page (https://dashboard.stripe.com/settings/billing/automatic)
silver cave
#

The payment is for a recurring subscription, specifically a gym membership

#

The cardholder would've authenticated during the initial purchase

#

How do we reference that initial authentication during repeat billing

#

?

tired notch
#

Based on the log, this PaymentIntent wasn't attached with an existing PaymentMethod when it's created, and the terminal application is collecting a new PaymentMethod from the terminal reader.

silver cave
#

I think you're in the wrong chat as I didn't even give you a paymentintent

#

We're talking about 3D secure

tired notch
#

Sorry, I'm in a wrong chat. Too many threads...

silver cave
#

No problem

tired notch
#

OK, back to the 3DS. It's up to the card issuer to determine whether a 3DS is necessary even if the card was used previously for the same subscription.

#

So your application need to handle the scenario when the PaymentIntent status becomes requires_action

silver cave
#

Payment Intent ID: pi_3LvMqCE48Fm17Noq03nmGpvb

#

This transaction failed but the cardholder has previously made a purchase and authenticated themselves. How do we re-bill this card and reference that authentication?

tired notch