#smokey0477

1 messages · Page 1 of 1 (latest)

boreal jewelBOT
#

Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

snow quiver
#

When the card issuer requries 3ds, the PaymentIntent will be in require_actions state. You can just pass its id and let stripe.js handle the action, it will only prompt for the authentication on the saved card not asking for inputting again

arctic furnace
#

umm ok, I'm a little confused as how this is to work then. So basically, I already have theit card saved. In their settings, they choose to upgrade their membership.

On the back-end, I create the subscription and automatically charge their card. So where does the client come into place here?

#

If they already have a default payment method, then I don't need the paymentelement right? Everything is already setup

#

I'm reading the api docs, and under the collection_method param it says:

Either charge_automatically, or send_invoice. When charging automatically, Stripe will attempt to pay this subscription at the end of the cycle using the default source attached to the customer. When sending an invoice, Stripe will email your customer an invoice with payment instructions and mark the subscription as active. Defaults to charge_automatically.

So I was assuming I didn't need to do anything with the Stripe client

snow quiver
#

Yes that's true if the issuer doesn't request 3DS 😄 You will have happily charge them on your backend

#

The thing is issuer can request 3DS, then you will need to bring your customer back online, present them a webpage, and on client side of that page call this handle next action method