#codex_webhooks

1 messages · Page 1 of 1 (latest)

modern yarrowBOT
#

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

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

willow orbit
#

Hi 👋

Sorry for the delay

#

I was reviewing the Invoice you shared and forgot to let you know

#

Unfortunately we cannot provide much help with disputes and chargebacks here.

I was digging through all the API calls for the invoice you provided to see if we expose some data you could use in your integration but I don't see anything.

I think you would need to track this in your own data system and flag when disputes are created for charge that have already been refunded.

bronze marsh
#

But in this case we refunded the customer $49.95, then the lost dispute happens, so doesn't that mean the customer received an extra $49.95 from the chargeback?

willow orbit
#

Has a status: 'failed' but I cannot immediately see why

bronze marsh
#

Wow, interesting! We currently don't listen to charge.refunded.updated. We also send a credit note upon refunds, so I assume that went through, but the refund didn't. Okay, this is a strange race condition

willow orbit
#

Yeah, bank networks are shockingly slow (not a lot of incentive to upgrade infrastructure) and that can lead to some odd funds flows

bronze marsh
#

I see on the updated charge refund, there's a field "failure_reason": "charge_for_pending_refund_disputed",. So the reason this refund failed after the fact, is because there was an ongoing dispute? Does this happen for every single refund during an ongoing dispute?

willow orbit
#

Unfortunately those are aspects that I cannot speak to. My expertise is on coding integrations with the APIs. Hence why I was trying to find some data you could use.

You can write in to Support https://support.stripe.com/contact for more help with the behavior of refunds during ongoing disputes though

bronze marsh
#

Thank you!

willow orbit
#

Sure thing! Happy to shed what 💡 I can 🙂

bronze marsh
#

I have a similar problem related to another double refunded+lost dispute credit note. Can I post it here, or should I open another thread?

willow orbit
#

You can post here but I don't think I'll be able to help much more than I already have

#

But I can check the status of the refund

bronze marsh
#

Yes please

willow orbit
#

Okay sure

bronze marsh
#

However, unlike the first case, there is no updated refund. What's the status of this refund now?

willow orbit
#

This created a credit_note for the Customer, it did not attempt to move funds back to their bank

#

So this just succeeded immediately

modern yarrowBOT
bronze marsh
#

Right, but then there's a lost dispute after as well

willow orbit
#

Also, for the record, we can't really use dashboard links so in the future you would help us out by just pasting the ID in here

#

Otherwise I have to carefully select just the ID number

bronze marsh
#

Right, sorry about that

willow orbit
#

No worries

bronze marsh
#

So the refund went through, still succeeded (req_okNre9RCQ3RP79). But then a couple days later, this same item became a lost dispute. So funds moved back to their bank

#

Unlike the first case (whose refund was changed to failed). This refund is still successful, AND there was a lost dispute, so the customer received extra money?

willow orbit
#

Unfortunately, this is getting into the parts about disputes & charge backs that I cannot answer. I recommend you raise this issue with Support https://support.stripe.com/contact