#juls1083

1 messages ยท Page 1 of 1 (latest)

still joltBOT
glacial quest
#

๐Ÿ‘‹ looking

#

What I believe happened here was

1/ Subscription was created with collection_method: charge_automatically
2/ Customer that was passed in had a default payment method
3/ Once the invoice finalized, we attempted to charge the payment method
4/ Issuer asked for 3DS, hence the first payment attempt failed and PaymentIntent moved to requires_action
5/ Since the first invoice payment attempt failed, the subscription moved to canceled state

round trail
#

Looking at the logs, it doesn't seem like 4/ happened. Usually, a new log entry appears saying "requires you to take action in order to complete the payment". It happened 3 days later

#

And, in case it happened as you say, shouldn't 5/ happen AFTER the 3DS challenge?

#

Does it have something to do with Indian RBI? The fact that the 3DS challenge didn't happen after some days

glacial quest
#

hmm could be, not sure

let me ask a colleague

tribal edge
round trail
#

yes

tribal edge
#

Not immediately sure what the initial payment failure was but am figuring that out.

tribal edge
#

Hey, just letting you know we are still looking in to this. We are making progress on identifying the initial error but it will take some deeper digging

round trail
#

Thank you very much. I'll stay tuned

tribal edge
#

@round trail Do you know if you have seen this issue for other customers or just this one?

round trail
#

First time we detect it. But we always had problems with Indian RBI in the past, so it's really the first time trying to investigate it and fix it

#

We recently moved to Payment Method API and deprecated sources

tribal edge
#

Gotcha. Yeah RBI can be tricky unfortunately. Can you write in to our support team about this? It is looking like this is a bug that we will need to dive deeper to fix. As far as we can tell it may be tied to this specific customer or mandate though we'll need to look further to fully tell

#
#

And if you can send me your email address after submitting your question, I can add context from what we found and make sure it gets routed properly

round trail
#

ok, I'll add contact emails on the support ticket. I'll mention you and this thread as well

#

Is there any workaround we could do in order to prevent the invoices to be charged in this situation?

#

I contacted the support team via email, but got no ticket number ๐Ÿค”

tribal edge
#

If you email me your address I should be able to pick it up

#

And apologies, have not immediatley been able to find info on a workaround. Basically you are looking for a way for the subscription itself to not be automatically cancelled on this first payment failure so that they user can manually retry later?

round trail
#

yes, we have a setting that cancels the subscription after all failed payment retries have finished, but in case of indian customers, no retries are allowed, due to banking regulations

#

so it gets cancelled after the first attempt

#

We're thinking of intercepting cancels for IN cards, check if it's due a failed payment, and then reactivating them again

#

Another option would be for the invoice not to be charged in this case

tribal edge
#

Unfortunatley I am not finding info on this at the moment. I think I will need to look deeper in to that as well and get back to you through the emial

round trail
#

do I give you the email here?

#

Thank you very much for your time. I'll be looking forward for an answer ๐Ÿ™‡โ€โ™‚๏ธ

tribal edge
#

That works, thanks for the emails. Will find your message and get back to you with what I can fidn