#reyanshsharma

1 messages · Page 1 of 1 (latest)

nocturne pastureBOT
tame heart
#

SubscriptionID: sub_1NTe2tK8SGfgbRnhYGvTkbiP

subtle yacht
#

Ok, question: What plan/price have you setup?

tame heart
#

Plan: plan_OG9aUxgcJypySx

#

Product: prod_NSQiQchQ7k1kOp

#

I belive that is what you requested?

subtle yacht
#

No, I want to help you understand the reason

#

So you have the plan id, what is its setup?

#

montly? once per a few months?

tame heart
#

Yup price per unit says:
$240.00 every 2 months

subtle yacht
#

Okie, when did you set the backdate, and when did you set the billing cycle anchor?

tame heart
#

Created the plan & backdate anchor today though set the sub to start from 1st of this month.

subtle yacht
#

Your backdate is July 1, billing cycle is Aug 1, UTC time

#

It means it will have Aug 1 -> Oct 1, then Oct 1 -> Dec 1 ... as 2 months billing cycles

#

But the first will be July 1 -> Aug 1, which is only 1 month

#

Hence you have half the price

tame heart
#

Got it.
Not related to plan or product but subscription create request. I see we kind of hard-coded the BillingCycleAnchor value to next month.

#

Though it should be calculated dynamically based on the Interval/s (2 months in this case).

#

We usually use per-month donations that's why never had issues in past.
Thanks for your help I am going to adjust the logic to calculate the BillingCycleAnchor dynamically.

#

QUESTION: What If I will remove the value? Will it be set up automatically?
Going to check the documentation again 🙂

#

Thanks again.

subtle yacht
#

You can try it in Test mode and see xD

#

See the outputed period in response

tame heart
#

Sure also I believe the total charge for this type of subs will still be correct only issue is instead of three invoices these will have 4.

  1. July to Aug: $120
  2. Aug - Oct: $240
  3. Oct-Dec: $240
  4. Dec - Jan: $120
subtle yacht
#

Well it's expected, as you set billing cycle on Aug and backdate from July