#andystevenson_api

1 messages · Page 1 of 1 (latest)

gray novaBOT
#

👋 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/1326588226252574793

📝 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.

ivory oliveBOT
covert sorrel
#

Hello again 👋 can you articulate why you get the impression this isn't supported?

Can you share the ID of the request where you tried to create the Subscription Schedule for this?

gray novaBOT
covert sorrel
#

My best guess is that you're referring to this request:
https://dashboard.stripe.com/logs/req_E2i1JXrXpm7iuj

I'd strongly recommend trying to get this to work in testmode before making these changes to a Subscription in livemode.

The error there is indicating that you have multiple prices with different billing intervals in a single phase. That is not supported. Each phase may only contain objects with the same billing frequency/interval, since Subscriptions can only support having items which all have the same billing frequency/interval.

The interval can change from phase to phase, but you can't have different intervals in a single phase.

dreamy swift
#

Hi... it is the interval_count changing?

#

I understand the point about test mode. Just was not expecting that behaviour. Manual workaround for now is simple enough. Simply schedule a future subscription.

covert sorrel
#

I don't understand the question. The problem is that one of the phases in the request contains two Prices, and that those Prices don't have the same billing interval:

      automatic_tax: {
        enabled: "false",
      },
      collection_method: "charge_automatically",
      currency: "gbp",
      default_payment_method: "pm_1QeyvmLoMN7oRScyPbVn78KE",
      default_source: "",
      discounts: "",
      invoice_settings: {
        custom_fields: "",
      },
      items: {
        0: {
          discounts: "",
          price: "price_1QcpKWLoMN7oRScye8P0H5Wb",
          quantity: "1",
          tax_rates: "",
        },
        1: {
          price: "price_1M064gLoMN7oRScy1wDjF7Ow",
          quantity: "1",
        },
      },
      proration_behavior: "none",
    },```
#

That isn't supported. A single phase can only support containing a single billing interval.

dreamy swift
#

I understand that. What I was trying is a new phase with different price and interval_count. First phase is interval_count = 3, next phase different price and interval_count=1

#

interval is month in both phases

grim tapir
#

Hello! I'm taking over and catching up...

dreamy swift
#

Sure ... give me a minute

#

req_E2i1JXrXpm7iuj

#

Oops... I think I amended the first phase!!! If I add a new phase through the dashboard it worked.

#

Sorry for the confusion!