#SachaK94-testing
1 messages · Page 1 of 1 (latest)
@cinder smelt not really unfortunately! You can create a regular one time payment/charge and then 'pretend' it was a month ago, but there's no way to directly create fake data with mocked creation time or states unfortunately.
I use monthly subscriptions and thats what i wanted to test
To check stuff like, if someone had an certain unit amount and then change at the middle of the month
stuff like that
I understand there is no way to do that then. Thats too bad it would be an awesome feature to do
Maybe you know that. But if i have a user that has a package paying monthly and then at the middle of the month he changes to a less price monthly payment package, there is a refund or something made ?
there can be a prorated amount charged yes, see https://stripe.com/docs/billing/subscriptions/prorations
proration can be negative if switching from expensive plans to less expensive ones, and that negative amount gets offset against future payments
Oh so if he switch then it creates a proration for future payments. He doesnt receive anything on the spot
And by default the proprated is created or i have to do it myself
it's on by default but you can control it by passing proration_behavior when making update calls to the Subscriptions API