#hasan

1 messages · Page 1 of 1 (latest)

covert elkBOT
frail citrus
#

I have created them as 4 DIFFERENT plans and not monthly and yearly being variations of the same plan
Any particular reason for that?

#

Can you share some examples of what you're describing? API requests, or sub_xxx object IDs?

clear forge
clear forge
#

question on the side, I understood the ProrationBehavior = "none" in the SubscriptionUpdate option as change the subscription immediately, am I right or is there something I'm missing?

frail citrus
#

In my back-end code when configuring stripe I set the SubscriptionCancel mode to "at_period_end" and SubscriptionUpdate ProrationBehavior to "none". I intended by doing so, to cancel a plan when its period ends, and to update/switch a plan immediately.
I don't really understand this part. You can't configure an update to happen a specific timestamp – it's always at the time of request

frail citrus
clear forge
#

oh okay, so when updating a subscription stripe always makes the change immediately?

#

I'm trying to understand the limitations of stripe when updating plans. The main problem is, that when I change plans, the change always happens immediately (just how I need it to happen) but I'm not always being charged immediately. When changing between pro plans or basic plans (the case mentioned above) the charging doesn't happen until the subscription period ends

frail citrus
frail citrus
clear forge
#

so this is the page in my website where subscription/ update plan happens. currently i'm subscribed to basic monthly plan as you can see in the portal

image.png image.png
frail citrus
#

Can you just share the sub_xxx ID? It's difficult for me to understand any issues from a screenshot

clear forge
#

sub_1N807fE2PVITNBan6FBpYfOO

frail citrus
#

You're currently subscribed to basic monthly, sure. In your update what are you trying to upgrade/downgrade to? What happens when you do it? What is unexpected?

clear forge
#

this is the subscription id of the new plan

frail citrus
#

Ok, what do you want me to check?

clear forge
#

When we upgrade from basic monthly, to basic yearly for example the customer is no charged instantly but instead is charged at the end of the billing cycle

#

We need any change to the plan to cancel the old plan and force a new payment

#

could be cause by the fact that we subscribed to a plan and changed it within the same day?

frail citrus
#

I suspect the issue is that you're changing between plans that have the same billing interval (1 day) and the same cost ($99.99)

#

Checking something

clear forge
#

ok thank you

frail citrus
#

Appreciate your patience. The reason we didn't immediately invoice for this upgrade/downgrade is because the billing interval is the same: https://stripe.com/docs/billing/subscriptions/upgrade-downgrade#immediate-payment

By default, the portal does not invoice for prorated changes, but you can change that in your portal config: https://stripe.com/docs/api/customer_portal/configurations/create#create_portal_configuration-features-subscription_update-proration_behavior

Stripe API reference – Create a portal configuration – curl

Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.

Upgrade and downgrade subscriptions

Learn how to upgrade and downgrade subscriptions by changing the price.

#

You'd pass always_invoice in this scenario

clear forge
#

by changing proration behavior to always invoice, I can keep the same intervals and get invoice immediately?

frail citrus
#

Yes we'd immediately invoice and bill the customer for the price difference

clear forge
#

okay great, will try it, thanks

sharp flint
#

Hi! I'm taking over from my colleague. Please, let me know if you have any other questions.

clear forge
#

sub_1N93qrBwiuQ4yN6woyqNFTgV
this is a subscription from a different stripe account.
we have the same setup with 4 products:
2 daily: 1 basic and 1 pro
2 every 2 days: 1 basic and 1 pro
the difference being that each plan has a different price.
We implemented the suggestion made by your colleague, and changed the proration behavior to always_invoice
The problem persisted, the subscrition was changed succesfully, but the customer was not invoiced immediately and instead the next invoice is at the end of the billing cycle

sharp flint
sharp flint
#

Are you with me?

#

Please, let me know if you have any other questions.

clear forge
#

thank you

#

will share the re_id

#

req_fE0ooxZxemJme8

#

this is the most recent request made, not if it belongs to the transaction i made

#

if not i can recreate the scenario of switching plans

clear forge
sharp flint
#

This is a request to create a Billing Portal session.

#

I need a request where you set the Subscription proration_behaviour to always_invoice

clear forge
#

i changed it from my back-end code, does it have a req_xxx if it was changed in code?

sharp flint
#

Yes

clear forge
#

req_W2AVranREcHsYm

sharp flint
#

But I am looking at this Subscription and I don't see any related Update request: sub_1N93qrBwiuQ4yN6woyqNFTgV

clear forge
#

i think this is the one

#

req_W2AVranREcHsYm

sharp flint
#

No, this is a request to create billing portal cofigs.

#

How are you sending that request?

#

Could you share the code please?

clear forge
#

sure

#

here is where I create the portal session cnfiguration and under subscriptionupdate is the proration behavior mode set

sharp flint
#

I see. And do you actually go to the Portal and update it?

clear forge
#

no, just from code

#

should i do both for it to work?

sharp flint
#

But creating a configuration for the Billing Portal doesn't update the Subscription

clear forge
#

but doesn't it affect future subscriptions?

#

what should i do now?

sharp flint
#

Do you want you customers to update the subscription in the portal? Or update it yourself via API?

clear forge
#

in the portal

feral jetty
#

Hi there 👋 jumping in as my teammate needs to step away soon. My grasp on your concern currently is that you have a Subscription that you expected to generate an Invoice to charge for prorations when it was updated, but that you aren't seeing that behavior. Am I understanding that correctly?

clear forge
#

yes, I need that when customers update plans, that they are charged immediately. What has been happening is that in plans of the same duration(subscription period) the plan is updated but customers aren't billed until current billing cycle is done

feral jetty
#

Gotcha, I see quite a few IDs in the thread, I hate to ask but would you mind sharing the ID of a Subscription where you saw this behavior again so I can be sure I'm taking a closer look at the right one?

clear forge
#

on it

#

sub_1N93qrBwiuQ4yN6woyqNFTgV

#

i just switched from pro monthly to pro yearly(both 2 day duration for testing purposes)

feral jetty
#

Thank you, taking a look.

clear forge
#

thanks

feral jetty
#

Alright, so I believe this is the update that you're referring to (the most recent one):
https://dashboard.stripe.com/test/logs/req_sgyHT5P1cMw0GB

Looking at the response for that, it looks like a new Invoice was generated (the ID is included in the response body) and that the Invoice was immediately paid. Is that different from what you're seeing?

Stripe Login | Sign in to the Stripe Dashboard

Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.

clear forge
feral jetty
clear forge
#

yes right

#

but why is it for 0 euros?

feral jetty
#

The customer had an existing credit balance, and that balance is automatically applied to their next finalized Invoice.

clear forge
#

but how does the customer have a credit balance? Is it from the subscription he was already subscribed to?

feral jetty
clear forge
#

I think there is a misunderstanding from our part then, the main issue is that we want the customer to be invoiced the full amount immediately when he changes his plan; initially we had the proration behavior set to none which wasn't achieving this, your colleague earlier suggested we change it to invoice_immediately. How can we achieve the desired behavior?

feral jetty
#

That is what invoice_immediately does, unless I'm misunderstanding your goal. The Invoice that was 0 euro, was the initial amount for the prorations the subtotal the amount you were expecting it to be? (Ignoring that the Invoice was paid for by a credit balance for now)

clear forge
#

Im sorry, I don't seem to follow:
given a product A of price 10$/month
and a product B of price 20$/month
if a user ifirst subscribes t product A and pays 10$, then instantly switched to product B, we need him to pay the full amount of 20$ additional dollar, so he payed 30$ in total that day.

#

we don't want any proration this is why we were setting it to none initially

feral jetty
#

Oh, so you don't want any prorations from the previous billing cycle, and you want to immediately move the Subscription to the next billing period and charge the full amount for that new billing period?

clear forge
#

yes this is exactly what I want

feral jetty
#

Checking if that is possible via the Customer Portal.\

#

I don't think you can accomplish that via the Customer Portal. It doesn't look like it supports changing the billing_cycle_anchor which is needed to get the behavior you're describing.

#

Instead you'll need to update the Subscriptions directly, setting proration_behavior to none and billing_cycle_anchor to now. This will avoid calculating prorations, immediately move the Subscription to the next billing cycle by changing the billing cycle anchor, and processing an Invoice for the new billing period.
https://stripe.com/docs/api/subscriptions/update#update_subscription-billing_cycle_anchor

Stripe API reference – Update a subscription – curl

Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.

clear forge
#

so one last question

#

what does the proration behavior parameter do exactly when it is set to none?

#

because we just migrated our payment from calling stripe APIs to customer portal and checkout as advised...

feral jetty
#

The proration_behavior parameter controls what behavior is used for calculating prorations for the request that includes it (it is not a "sticky" property that gets set on the Subscription, it has to be passed with each request where you want to use non-default behavior).

clear forge
#

ok but what does it do when set to none?

feral jetty
#

Nothing, no prorations are calculated.

clear forge
#

koay

#

okay thank you forn your time

feral jetty
#

Any time!

clear forge
#

would stripe need any developers, because the whole team just wasted 2 month of development and we might need new jobs 🥲

covert elkBOT