#danclassfit

1 messages · Page 1 of 1 (latest)

lethal joltBOT
clear nest
primal wasp
#

I'm not overly concerned about the double payment instance

#

I'm concerned about our dev flow being incorrect

#

For example if we are being trigger happy sending out failure emails and reattempts if Stripe need X hours to reattempt payment first etc?

#

Which seems like a dev/discord thing?

clear nest
#

sure, what is the specific technical question I can help with?

primal wasp
#

When a payment fails with Stripe, is there a certain period of time in which Stripe will reattempt said payment before we should assume the payment has failed and the process from Stripe's side is complete.

#

pi_3ORO4xIfd3b13usY00NiDpS5

#

If it helps, this is the payment in question

clear nest
#

We don't retry payments processed through direct PaymentIntents ourselves.

#

we only do things like Smart Retries for e.g. Invoice payments on subscriptions

primal wasp
#

Once this failed, our flow picks that up and acts accordingly.

#

But then it tried again as you can see here.

clear nest
#

I can't see that here. Not sure what you mean.

primal wasp
#

401 ERR

#

Where the payment failed with Stripe

clear nest
#

that's not a payment, that's an attempt to issue a refund.

primal wasp
#

Huh. Sorry one sec.

clear nest
#

it's just you clicked Refund in the Dashboard, and the UI asked you to log in again to confirm, and that's just how it looks in this view since it shows you failed request the UI made

primal wasp
#

The merchant did the refund, because two payments were taken

#

When it was only meant to be one

#

And the two payments were taken because from our side, the first payment was shown as failed, so our flow tried again.