#aksharj
clear cape
fervent tapir
Hi 👋 can you elaborate a bit? That isn't a full year, so I need to understand how you're planning to handle this scenario in order to explain how our system will behave with it.
Are you planning to create the Subscription so that it starts in the future, and then cancel it early? Or are you planning to start it sooner and ignore the first 20 days of the Subscription?
dreamy yoke
hi @fervent tapir many thanks for your reply.
i am actually trying understand what happened here sub_1JzLvBHCqAocHUR8ffQ3eJ7u
i think i created the subscription on 24th Nov 2021 and set it to end at 4th Nov
i see two invoice, i am not sure why the invoice was created at 4th Nov with amount $184.56
fervent tapir
The parenthesis around the second Invoice's amount indicate that it is a negative amount. It looks like you used the cancel_at parameter on the Subscription, so it is expected that a final Invoice was generated to prorate the previously paid amount.
The easiest ways to avoid these prorated calculations is to either cancel the Subscription at the end of a billing period using cancel_at_period_end or by immediately canceling a Subscription using this endpoint:
https://stripe.com/docs/api/subscriptions/cancel
dreamy yoke
is it possible to see how the subscription was created, juts to verify that I indeed used the cancel_at parameter
also, many thanks for the detailed explanation this makes sense
fervent tapir
It wasn't in the creation that the cancel_at parameter was used, that was part of an update request that was made by an action taken in the Stripe dashboard. I believe you can find the log of this request in your dashboard:
https://dashboard.stripe.com/logs/req_FCLhxx5SAd8DRk
dreamy yoke
many thanks for the link, is it possible to know which user performed the request and at what date?
does the created property in the Response body indicate when the request was created?
fervent tapir
Yes it is possible to see that. The created timestamp in the response corresponds with when the object contained in the response was created, and should not be used as the timestamp of the request.
The request's timestamp is contained in the Time field on the linked page, and the Source field shows it came from the dashboard along with which user triggered the action.
dreamy yoke
got it, many thanks @fervent tapir you are helpfull as always 🙂
fervent tapir
Happy to help!