#fedeb_susbcription-coupons-trials

1 messages · Page 1 of 1 (latest)

boreal daggerBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1356274053588979941

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

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.

stark cradleBOT
sterile sleet
#

Hi 👋 I apologize for the delay, the server is incredibly busy at the moment. Taking a look at your request.

naive jetty
#

thanks

sterile sleet
#

I need to build a bit of understanding here. I see in the Subscription Schedule update request, that the same Coupon is being applied to all three phases. Is that intentional? Is the concern that the discount isn't removed after the third phase?

naive jetty
sterile sleet
#

Are you able to share the ID of the Invoice that is including that Coupon that you aren't expecting?

naive jetty
sterile sleet
#

For this Invoice:
in_1R7KoCE8gsL5R1XuKMJgmp5W
The Subscription Schedule reapplied the Coupon for the phase that generated that Invoice.

#

If you structure a Subscription Schedule such that the same Coupon value is in each Phase, then the Subscription Schedule effectively updates the Subscription at the start of each phase and applies that Coupon as though it was being applied freshly.

#

We don't automatically ignore a Coupon if it's one-time use and you tell us to use it again. In that case we do as you instruct and apply the Coupon to the Subscription so it'll impact one more Invoice.

naive jetty
#

could be the proration fault?

image.png
sterile sleet
#

No, I don't think this is related to the proration behavior. I'm still trying to spot why a Discount was on in_1R7KoTE8gsL5R1XueBb8tVcD, and whether it's the same Coupon from the Subscription Schedule.

boreal daggerBOT
sterile sleet
#

Hm, this looks unexpected to me, and it doesn't look like something is applying the coupon again after the Subscription Schedule finished its lifecycle.

naive jetty
#

Mm bug/issue with clock feature maybe?

fluid hound
#

Hi 👋

I'm stepping in as my colleague needs to go.

#

I see that you specified a duration: "once"

#

According to our docs that should mean it only discounts the first charge on the Subscription

Applies to the first charge from a subscription with this coupon applied.

naive jetty
#

yes but it keeps been applied for every invoice, I use the clock future to advance time and the new invocis still show the cupon in the details.

fluid hound
#

Yes I see that

naive jetty
#

yes

fluid hound
#

Then you create a Subscription Schedule from that Subscription.

#

At this point there are 2 phases, both of which have the Coupon applied. The first phase is a trial period so there isn't a payment to discount

#

Okay so that makes sense to me, somewhat.

naive jetty
#

Ok..

fluid hound
#

Then you update the Schedule to end the trial early

#

And at that point you copy the Coupon to the third phase.

#

I still don't think our Coupons are behaving as expected. I'm just trying to walk through the process that got us here to see if I can spot any step that might have triggered this behavior.

#

Okay I've been reviewing the Invoices generated by this Subscription and I'm a little confused. The coupon you applied has a percent_off of 0 and trialdays: "30" in the metadata.

How is it you are applying this Coupon?

naive jetty
#

I created that subs by API call
We monitor trigger webhook that stripe generates in our systems, we read metadata coupon and applies the trial time

fluid hound
#

So the purpose of the Coupon is not to decrease the amount of the first Invoice but rather the apply the trial_days?

naive jetty
#

Yes, it works the free trial
The issue is that after the first or second month( updated phase)
In the invoice details it shows the coupon, is not doing anything but its there in the invoice details
I tried 3 months clock advance and still showing there

fluid hound
#

I think the issue is that, without applying an actual discount to the first Invoice, we don't consider the Coupon as consumed.

Coupons are intended to reduce the amount paid, not trigger free trials.

naive jetty
#

Well the coupon has 0.01% off once in this case 8.99 for = 8.989101 maybe stripe rounds to 8.99 anyway

So you are saying since it didt rest anything it will keep showing?

#

If it where a price like 100$ 0.0.1% =99.99 there it suppose to only have it for one invoice?

fluid hound
#

I don't think it's a good practice to use the Coupon object in this way

#

And that you may wind up with unintended behavior

naive jetty
fluid hound
#

Yeah because that's not what Coupons are intended to model

#

What is the experience you are trying to give your customers?

naive jetty
#

I will test later with a bigger amount and see if that the cause And not repeat since it actually pay less

naive jetty
fluid hound
#

Also, I want to suggest you use the discounts.coupon parameter instead of just coupon.

#

We are deprecating the top-level coupon parameter in favor of a nested approach to allow more flexibility

naive jetty
#

Okay yes that could be too
I was using an old postman collection

fluid hound
#

My question is, since you apply the trial period when you create the Subscription, why do you need a Coupon to track it?

naive jetty
#

The coupon is optional and we give them to specific customers to enter that in the front-end UI

#

(Right now im testing so using api call directly to avoid UI)

fluid hound
#

Okay so, for this approach, I think it makes more sense to only use that Coupon within your integration (instead of using Stripe to track it, since that's not how our Coupons work). When the Customer enters it, you create the Subscription with the trial period you want (7 or 30 days) and add metadata to the Subscription indicating the reason for the length of the trial.

#

That is how I would build this integration

naive jetty
#

I see your point, yes I don’t know exactly why we are doing this and not like that.
Business decision or whatever , I can’t answer , its a big company

#

Thanks that is all for now
I will try those both things of using discount object and test amount

fluid hound
#

Okay, that makes sense.