#iron_subscription-customer

1 messages · Page 1 of 1 (latest)

steady pawnBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

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

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

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

coarse dome
#

yeah that is an hallucination

#

iron_subscription-customer

#

you have to create the Customer separately first, no alternative

robust vortex
#

thanks 🙂 Have a good one!

coarse dome
#

you too!

robust vortex
#

Oh, actually I had one more question:

Is there any way to create a subscription that will be paid by bank transfer (so, collection_method=send_invoice) that will actually start with subscription.status = 'unpaid' instead of active?

coarse dome
#

No. unpaid explicitly means the previous Invoice was never paid and at the end of all retries we moved to that status because you picked that option in your account settings. It's also something I just discourage.

But you might have meant something else than unpaid?

robust vortex
#

Oh, gotcha

#

sure. Right now I can't really use subscription.status == 'active' to prevent access to my SaaS, I'm having to do invoice.status != 'open'

coarse dome
#

yeah so it's not unpaid that you want. But correct that's not possible, those are paid async and can take days so usually the way you design your SaaS is to give access before they pay if you use those payment methods

#

otherwise someone pays for a month at $100 but can only use say 25 days because for 5 days their bank transfer was "pending" and you didn't give them access

robust vortex
#

oh, yeah sure. Unfortunately our SaaS is really data access, so if they don't pay up front they could download the data and never pay

coarse dome
#

yeah but that means you either should take the payment before starting the period or not accept async payment methods.

robust vortex
#

hmm, well we have a few clients that require bank transfer payment methods. But I need to provide an invoice to them for them to pay. Is there a way to create an Invoice/Subsription without starting the period?

coarse dome
#

nope

#

Basically what you want isn't really a thing today. You want to separate the "period rendering the service" from the date at which to take the payment and we don't really support this unfortunately.

robust vortex
#

No worries 🙂 Thanks for clarifiying that for me!

coarse dome
#

sure thing!