#rozig - invoice payment attempts

1 messages · Page 1 of 1 (latest)

pliant stagBOT
willow rune
#

Hey there, can you share an example event ID? Do you expect further payment attempts to be made on the invoice?

vivid cipher
#

Yes. I'm expecting further payment attempts
evt_1M2y9iHcEDTg6I86HPWxGF5c

#

here is an example event ID

willow rune
vivid cipher
#

so does it mean if the payment is triggered manually in the first time and fails, it will not be re-attempted according to the auto advancement settings?

willow rune
#

It will, but "next" only populates following the first scheduled payment as far as I can tell. Looking at this invoice that appears to be what happened here, right? Your manual payment failed then a later automated one succeeded?

vivid cipher
#

I can tell the first attempt was automatic from the event times.
Draft invoice got created, then finalized. That is the 1st invoice.update event. Then it attempted the payment. Once the initial payment fails, it updated the next_payment_attempt to be null. And the next payment attempt made after an hour, unless stripe has some fallback settings for failed payments, the second payment attempt can't be automatic payment attempt. This is what I'm thinking, am I missing anything?

willow rune
vivid cipher
#

Didn't look at this log. Let me do little more debugging. But just to confirm, when the payment gets triggered manually and fails, the next_payment_attempt field will not get populated but the auto advancement will still work as expected correct? Then after the 1st scheduled payment attempt, the next_payment_attempt will be populated if it fails.

willow rune
#

Yes that's my expectation

vivid cipher
#

Thank you

#

I actually have a similar invoice which doesn't have the above issue (next_payment_attempt is present). Will you be able to check this for me please?

#

here is the event ID: evt_1M3mAdHcEDTg6I86HIvVngbD

willow rune
#

that event / payment failure were also due to a /pay request:

vivid cipher
#

Right, but if you take a look at the payload. It always had next_payment_attempt field populated

willow rune
#

Ah it looks like the earlier example wasn't a full "decline" -- the payment failure was a processing error, which might have affected this

#

In the second example the payment was declined

vivid cipher
#

I see, is there a documentation where I can get more details about this? We are seeing this issue a lot in the last 20 days

topaz nexus
#

Hi there! Just catching up since my colleague needed to step away

topaz nexus
#

Just to confirm, are you looking for documentation on declines generally?

vivid cipher
#

Not really, I want to understand how card processing error differs than the card decline and how it affects to the next_payment_attempt field and what to do to fix this

topaz nexus
#

Looking at the event details for evt_1M2y9iHcEDTg6I86HPWxGF5c (next_payment_attempt was null) and evt_1M3mAdHcEDTg6I86HIvVngbD (next_payment_attempt was not null), it looks like the processing error that triggered evt_1M2y9iHcEDTg6I86HPWxGF5c was not counted as a payment attempt

vivid cipher
#

I am looking for the reason why it won't get counted as payment attempt. So that I can do what I can do to avoid this situation.

topaz nexus
#

Sorry for the delay, taking a closer look

topaz nexus
#

Okay, I'll need to check in with some folks internally about this so I won't have an answer for you today

#

Could you contact our Support team at https://support.stripe.com/?contact=true, provide a quick description of the issue, and mention you were working with roadrunner on Discord? Let me know when you've submitted your request

#

I can then keep you updated on our findings

vivid cipher
#

Sounds good, thank you so much. I will let you know once I submit the request