#bunetz

1 messages ยท Page 1 of 1 (latest)

lament nymphBOT
mossy elk
#

There isn't a Checkout Session setting for this. You would need custom code to store this info per customer and then check it before creating Checkout Sessions for them. You can probably store whether they have used a trial either in your own database or on the metadata for the customer object

lament nymphBOT
mild jewel
#

but I have no idea about the payment methods, what if a customer creates 2 accounts in my database? then he would get 2 trials

mossy elk
#

Are there other payment methods that you are using? Can check in to how to check for those

mild jewel
#

then I would need to first ask for payment method with something other than a checkout session?

mossy elk
#

It looks like there is also a fingerprint property for a lot of these payment methods:
https://stripe.com/docs/api/payment_methods/object#payment_method_object-us_bank_account-fingerprint
https://stripe.com/docs/api/payment_methods/object#payment_method_object-au_becs_debit-fingerprint
It looks like there isn't a way to list payment method by fingerprint so I think at the moment you will need to store the fingerprints and compare them later.

mild jewel
#

because I cannot have a custom duration trial with a coupon right? I could only do 1 period free

mossy elk
#

Also I am realizing a hurdle here in that you won't know the PM information until the user submits their payment details in the Checkout Session. Maybe you can do the check after the details are submitted and if you detect details that you have already seen you can pause the subscription and notify the user that they can resume without a trial

mild jewel
#

yeah but that is pretty bad for user experience. So what is the standard way of offering trials which are "first time only" in stripe? I assume that a lot of people use this

dry hearth
#

Hello ๐Ÿ‘‹
As far as I know, there's no way to prevent this without writing the code that prevents customers from creating duplicate subscriptions.

I believe we've received similar feedback in the past and the team is working on something that'd allows merchants to control this but it isn't something that we support today out of the box.