#alexb

1 messages · Page 1 of 1 (latest)

ancient elkBOT
plush stone
stone siren
#

Hi there, taking a look

plush stone
#

thanks!

stone siren
#

Thanks for the context!

plush stone
#

Are you still looking into this?

stone siren
#

Yep, sorry for the delay!

plush stone
#

ok thx, no worries, wasn't sure.

stone siren
#

Okay, I see that marking the invoice as uncollectible does not change the status of the underlying PaymentIntent

#

Prior to the successful payment on 12/5, the status of the PaymentIntent was still requires_payment_method, which means it could still be used to collect payment.

plush stone
#

Ok. I was told specifically that marking the invoices as uncollectible using that setting would solve the problem

#

What do we need to do? Why do you process payments in a situation like this?

stone siren
#

I'm sorry, this was not accurate advice. It's still possible to pay an invoice after it's marked as uncollectible. The customer probably had a copy of an email with the link to the Stripe hosted invoice page

plush stone
#

Ok that previous advice came after 40+ messages with stripe support, where I got misinformation repeatedly, then 90 messages here on discord

#

Is there a solution to avoid stripe taking payment in these situations?

#

This is very frustrating to have to spend so much time only to get wrong answers, and very frustrating our customers still face this issue

stone siren
#

I understand, and I'm sorry for so much back and forth

#

If a customer accesses the hosted invoice page, they won't be able to complete the payment

plush stone
#

So we have to listen with webhooks, detect canceling subscriptions, then cancel the payment intent?

#

Why?

#

Why does Stripe insist on taking payment despite the subscription being permanently cancelled, and the invoice marked uncollectible?

#

Wouldn't it be better to not take payment?

stone siren
#

So we have to listen with webhooks, detect canceling subscriptions, then cancel the payment intent?
Not exactly. The logic that handles canceling the subscription can look at the subscription's latest_invoice and update that invoice's status to void. this status update will cancel the underlying PaymentIntent automatically

plush stone
#

We don't cancel these subscriptions

#

Ok so we will use webhooks to listen for you canceling the subscription, then we'll write code to void the invoice

stone siren
#

ah sorry, that's my mistake. yes, the webhook handler that listens for canceled subscriptions should the void the latest invoice

plush stone
#

Ok. I understand and can do that

#

But I am still left with those questions.

#

And also concerned that maybe this won't work given Stripe's track record on this issue

stone siren
#

I think some of the friction here is caused by a complex billing product. There are lots of statuses to work through since this product aims to solve for very complex billing flows. so, for example, canceling a subscription for one merchant may mean cancel immediately and "delete" all invoices, while another merchant may want to keep any open invoices as is and still expect to collect payment

#

There's also some terminology bits: voiding is essentially a delete, while marking uncollectible is used by merchants who don't expect to be paid but might still be paid for those services

plush stone
#

Sounds like you guys need some documentation on your end so that you know how it works

#

Thanks for the help, I'll try implementing this, hopefully I get it done correctly and it has the intended effect.