#flex_invoice-subscription

1 messages ¡ Page 1 of 1 (latest)

runic bridgeBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1253395117231050913

📝 Have more to share? Add details, code, screenshots, videos, etc. below.

misty reef
#

flex_invoice-subscription

#

@crude kraken I don't really follow what you're explaining as it's too abstract. And Invoice can't be paid twice. But it's possible for you to modify a Subscription which causes multiple sequential Invoices to be created yes

crude kraken
#

They're two separate invoices being created and paid for per customer affected. What would cause a subscription to be modified?

misty reef
#

Many different things can cause this. You clicking in the Dashboard, them changing their Subscription in the CustomerPortal, you calling the Update Subscription API and many more.

runic bridgeBOT
crude kraken
#

Could the front-end putting in multiple confirmPayment request cause the Subscription to be modified as well?

dapper field
#

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

#

Probably not. Can you give me the ID of the Subscription so I can take a look?

crude kraken
#

Definitely sub_1PTDICKkdqtGGO7iX7n2XxOS and sub_1PTDB6KkdqtGGO7iNutT9VWB

#

Did you want the invoices for them as well?

dapper field
#

Nah, this should be good enough, hang on...

#

Ah, okay, so looking at that first one, you backdated the start date when you created the Subscription, and you also configured the billing cycle anchor to be on the 19th day of the month on hour 3. You created the Subscription on the 19th in hour 1, which created the first Invoice. Due to the backdating and the billing cycle anchor configuration you provided, the current period ended about two hours later (during hour 3) which is when the second Invoice was created (for the next Invoice period).

#

So, basically, the Subscriptions system is doing exactly what you told it to do.

crude kraken
#

Ah gotcha, so if I wanted the subscription to only charge once and have that charge start on the day of the subscription I should remove the billing anchor cycle and just leave the backdate as is?

dapper field
#

Yes, I believe so, but give it a try in test mode to make sure it behaves as you expect.

crude kraken
#

Thank you, give me just a moment

#

Taking out the billing cycle anchor config worked thank you!