#wasabi-subscriptions

1 messages · Page 1 of 1 (latest)

round cliff
#

heya @vestal quail, what's a change-log approach?

vestal quail
#

@round cliff Great question tbh I'm not quite sure what the user means here. I guess the change-log approach refers to how Stripe handle upgrades and downgrades API calls when the Stripe system is down.

round cliff
vestal quail
#

Thanks so much @round cliff . I think this page is definitely helpful. Are Stripe network and server errors always communicate to users via the Stripe error codes? Has there been any major instances that Stripe contact user directly?

#

Are there any major errors that are not covered in the error handling page that users should be account for their integration?

mystic solstice
#

Hi! I'm taking over this thread.

#

Are Stripe network and server errors always communicate to users via the Stripe error codes?
If there are errors on Stripe's end, then you will get an HTTP response with a 5xx error code

#

Has there been any major instances that Stripe contact user directly?
I'm not sure to understand this question

#

Are there any major errors that are not covered in the error handling page that users should be account for their integration?
There should be everything is the doc that was shared earlier

vestal quail
#

@mystic solstice thank you for the clarification.

#

A separate question, what are the pros and cons of modeling a product with multiple prices? Are there any disadvantage in modeling a 1-1 product price vs. 1-many product and prices?

mystic solstice
#

Here's what the doc says https://stripe.com/docs/api/prices:

Different physical goods or levels of service should be represented by products, and pricing options should be represented by prices. This approach lets you change prices without having to change your provisioning scheme.
For example, you might have a single "gold" product that has prices for $10/month, $100/year, and €9 once.

vestal quail
#

For example, we have 2 product types with 2 billing intervals at different prices. 1) Product A pro that is billed annually and charged 200 USD. 2) Product A pro that is billed monthly and charged 24 USD 3) Product B plus that is billed annually and charged 100 USD 4) Product B plus that is billed monthly and charged 12 USD

mystic solstice
#

Then you should have 2 products (A pro and B plus), and each product has 2 prices (annual and monthly).

vestal quail
#

What are the disadvantages (outside of provisioning scheme) if user decide to setup 4 different plan (1-1: product-price) for the for use cases above? What does provisioning scheme means here?

mystic solstice
#

What are the disadvantages (outside of provisioning scheme) if user decide to setup 4 different plan (1-1: product-price) for the for use cases above?
Yes you could setup 4 products with one price each, but in that case there are some handy features that you will miss. For example:

  • If you are creating monthly Subscription with Checkout, you could automatically try to upsell the yearly plan
  • If you are using the Customer Portal, you could let user easily switch between the monthly and yearly plan
#

What does provisioning scheme means here?
You probably have some webhook that listen to the customer.subscription.created . This code looks at the product purchased to know how to "fulfil the order". If you need to add a new price and that also means adding a new product, you might need to update your code to make it work. On the other hand, if you just add a new price to an existing product, there's probably nothing to change.

vestal quail
#

Thanks for the insights, Soma!

#

To follow up on this, if the user decide to go with custom code vs. low code, what are the disadvantages for doing model product and price 1-1?

#

Has there been any instances why a user would prefer product and price 1-1 modeling?

mystic solstice
#

In that case there's still what is mentioned earlier about "provisioning scheme"

This approach lets you add/change prices without having to change your provisioning scheme.

#

To summarise we recommend doing this (which has no disadvantages): "Different physical goods or levels of service should be represented by products, and pricing options should be represented by prices."
But Stripe's API is quite flexible, so if you need to create product and price with 1-1 relationship, it will work.