#Barba-trial-PaymentIntent

1 messages ยท Page 1 of 1 (latest)

rich cosmos
#

Hello, do you have an example subscription ID (sub_123) that this happened with?

#

Also the id of any payment intent or setup intent that you got an error for when confirming?

tiny crystal
#

sub_1JehRSLf6j9PT4hquWMTyVf2

#

price_1JUuPNLf6j9PT4hqYckF1P8u

rich cosmos
#

I don't see an attempt to confirm that SetupIntent, when you try to do so with an SI from a subscription like this, do you get some kind of error?

tiny crystal
#

let me 1sc im going to reproduce the use-case again to give you more details

#

oki, im having issues to reproduce the error right now ๐Ÿ˜’ try to solve it, btw I think I gave yo the wrong price id. the right one is price_Vj65EMMekvPfYc

tiny crystal
#

could we continue looking for this issue tomorrow?

mossy tree
#

Yup, feel free to hop back in tomorrow if you want to continue looking into this - we'll archive this thread for now, but when you come back you can ask one of us to reopen it.

I also just wanted to add a quick thing - when you confirm the Setup Intent you're making sure to call confirmCardSetup client-side instead of confirmCardPayment right?

tiny crystal
#

nope... I was calling confirmCardPayment and with confirmCardPayment and not free trial is working.. the problem is calling confirmCardPayment and the free_trial

mossy tree
#

With a free trial you'll be getting back a SetupIntent, which you have to call confirmCardSetup for. You can't call confirmCardPayment with a setup intent client secret

tiny crystal
#

mmm oki... makes sense ๐Ÿ™‚ thanks!! I'll double check that

#

mmmm oki, quick question or just a quick summary for myself as Im implementing the backend using the node stripe API and the front-end is using the stripe-js part. Its true as you said when I create the subscription with the trial_end Ive the setupIntents so I guess the front-end will be able to call to the confirmCardSetup

the scenario creating a subscription with no trial_end was giving me the clientSecret so thats why it was working fine, isnt it?

mossy tree
#

A more general way to think about it is if the Subscription is created and no payment is needed up-front (like in the case of a trial) there is no payment to be confirmed. In this case, we still want you to be able to set up for future payments so we create a SetupIntent that you need to call confirmCardSetup with.

When payment is needed upon creation of the Subscription, we generate a PaymentIntent which you can use with confirmCardPayment

tiny crystal
#

I think makes sense what you said :), very helpful. thanks!