kt_code

[grand hawk]

👋 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/1233463206853345311

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

[tender sinew]

Hello! Do you have an example subscription I can take a look at? Just want to check a couple of things

[hollow crow]

yup, sub_1P9PsBAFQUUIWEfkdpghtaVz

and then if you want here's a test mode subscription that I got into the same state by using test card 4000000000000341 sub_1P9sFsAFQUUIWEfkUeSbK4SQ

[tender sinew]

gotcha - give me a few minutes to take a look

[tender sinew]

I took a look through our code and unfortunately I'm not really seeing any way around this on creation - we don't offer any way to create a status: incomplete subscrpition on creation when also using pay_immediately: false

Can you change your checkout flow to attempt payment so that you can immediately surface that decline to your customer?

[hollow crow]

hmm I think we could but we have to wait for avatax to add tax line items to the invoice prior to finalizing and attempting payment so that would mean the customer is sitting on the checkout page while all of that happens which isn't ideal. is there a way to request a feature be added that allows status incomplete + pay_immediately false? I'm assuming it's not possible for a reason but figure it doesn't hurt to ask haha

I also saw there's the option to verify with micro transactions https://docs.stripe.com/js/setup_intents/verify_microdeposits_for_setup

which might help us, but it says "Use stripe.verifyMicrodepositsForSetup in the Save details for future payments with pre-authorized debit in Canada or Save details for future payments with ACH Direct Debit flow to verify a customer's bank account with micro-deposits." could we use it for any type of payment or does it have to apply to those one of those two use cases

[warm sun]

Hi 👋

I"m stepping in as my colleague needs to go

Micro-deposit verification is specifically for US (ACH) and Canadian (ACSS) payment methods. It only applies for those use cases.

[hollow crow]

so is the only path forward here to try to wait for a payment attempt from within checkout after all of the 3rd party tax stuff happens? can we request a feature be added that allows for status incomplete + pay_immediately false on a subscription?

[warm sun]

I will file that feature request but, just so I'm clear, the issue is that you have a 3rd party tax integration that takes some significant amount of time to complete?

[hollow crow]

the issue is we're creating and confirming setups intents within our checkout (can't use payment intents because we have to wait for the invoice to be created before avatax can update the invoice with the tax amount, and then create a payment intent for the final amount) and payment methods are successfully getting attached to the customer but then failing on payments. This puts the subscription into a past_due status when we'd rather it be incomplete since they haven't actually started the subscription. there's no way to have the subscription be incomplete since we can't set payment_behavior: default_incomplete.

so then the only thing to do for now would be to add webhook listening to our checkout and have the customer wait in checkout until we get an invoice.paid event for the subscription (5-10sec extra wait time)
but if the payment wasn't successful we'd have to do our own cleanup of the subscription so it doesn't look like the customer has already subscribed.

So long story short(ish) It adds wait time to the checkout session for the customer and more work and potential errors for us since they have a subscription that's in past_due state that they've never actually been given access to

[warm sun]

Hmmm .... I can understand that scenario being less than ideal, since past_due isn't really reflective of the customer's situation.

[hollow crow]

Yeah exactly, everything is a lot trickier with the 3rd party tax provider unfortunately since we can't just create a payment intent right away. My attempts to convince accounting to stop using the 3rd party tax provider have all failed lol but yeah in an ideal world all subscriptions would be in incomplete status until 3rd party tax stuff happens and the first invoice is paid

[timber prairie]

Hi there. snufkin had to step away. Do you have any follow up questions?

[hollow crow]

Snufkin said he would put in a feature request for the capability to specify both payment_behavior: 'default_incomplete' and pay_immediately: false on subscription creation, is there any way to track that feature request or get an estimated timeline?

[timber prairie]

Unfortunately not. They're just internal tickets, and there's no guarantee that they'll ever be implemented. It just depends on demand, and the team's prioritization, so we can't give a timeline or anything

[hollow crow]

Hmm okay, and just to be sure, there's no other way to force a subscription into incomplete status?