#mrmarcondes

1 messages · Page 1 of 1 (latest)

surreal slateBOT
river lichen
#

Why do you use the setupintent?

#

Why not just collect payment info once on the subscription?

modern hazel
#

Because we offer 100% discounts.

#

We cannot use paymentIntent for $0.00, right?

river lichen
#

Ok I think I'm confused. So you're not creating setupintents explicitly? You're discounting the first subscription invoice to $0, then using the attached setupintent to collect payemnt details? Then payment ends up requiring action on the second subscription invoice? Or are you explicitly creating setupintents?

modern hazel
#

In the frontend we use something like this:

const { error } = await stripe.confirmSetup({
    elements,
    confirmParams: { return_url: thankYouURL },
});

Once the customer confirms they want to subscribe, frontend sends us the setupIntent.Id and we create the paymentIntent based on this id.

river lichen
#

Oh so you're not even using subscriptions from us?

#

You create setupintents and payment intents yourself for subscription payments?

modern hazel
#

Yes, we use it. This is only the first step.
Once we collect the payment for the trial, we create the subscription.
Actually, we:

  1. create a payment for the sampler - this is a one-shot and will be delivered to the customer asap;
  2. then create a subscription;
#

the setupIntent and PaymentIntent is only for the 1.

river lichen
#

But why?

#

Why do you need a payment intent outside of the subscription?

#

Why not use the built in trials feature of subscriptions?

#

Need to understand your usecase more

modern hazel
#

our trial has different products than the subscription.

river lichen
#

But if trial is free, why do you need to create a payment intent

#

I still need more details to understand and help

modern hazel
#

no. trial isn't always free. it actually costs $32. But, we offer some 100% coupons.

#

But my doubt is about 3DS secure, ok?

river lichen
#

Got it

#

Yeah seems like subscriptoin schedules is what you want

#

That way everything is linked through that

#

I understand your problem but I need all the details of your integration so I can make a recommendation

#

At the end of the day though, it's up to the bank

#

They can require 3ds at any point for any future subscription payment if they want

#

So your integration needs to be able to handle bringing users back online to authenticate

#

But if you do everything through a subscription or a subscription schedule, it minimizes the risk of that

modern hazel
#

My concern is at the beginning of the process: once the customer places their order for the first time:
as soon as we have the setupIntent authorized by the bank, we create the PaymentIntent using it and we get the next_action.
Would the customer have to authorize it again?

river lichen
#

Read what I said above

#

It's up to the bank

#

Sometimes they may require authorization again

#

Even if you did set it up properly with a setupintent

modern hazel
#

ah, ok. gotcha. thank you

river lichen
#

Really recommend you use subscription schedules for your usecase though. Will simplify things

#

Well will simplify things once you understand subscription schedules (which I linked above)

modern hazel
#

I'll take a look at it. thank you.