#mattcomroe_api
sinful raptorBOT
👋 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/1502384238593441944
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- mattcomroe_api, 3 days ago, 17 messages
thorn surge
👋 looking into this!
marble pebble
thanks! i appreciate you!
thorn surge
Currently all test cards for Disputes are for the full amount (listed here). Checking other testing possibilities for you right now
marble pebble
great; thank you for looking into that!
thorn surge
I'm still not finding any way to do this right now - can you help me understand why you're interested in testing a partial chargeback scenario?
marble pebble
because we just had one come through, and we're not handling it correctly. i believe up until this point we were expecting "all or nothing" on disputes.. won or lost. I'd like to be able to test the partial chargeback to make sure we're handling it correctly before i put that code in PRD.
thorn surge
Can you clarify what you mean by "not handling it correctly"? Is there an error or is something not working as expected?
marble pebble
on our side we issued a full refund to the cardholder (we're a platform account so we're intermediary on everything), instead of what the partial amount should be. i would like to simulate that exact scenario for my coding and testing. i can "guess" what a partial chargeback will look like, but i would like to work with the actual webhook events from Stripe instead of intercepting and manipulating them to try and recreate the scenario.
thorn surge
To confirm my understanding, a cardholder submitted a partial dispute request and your code refunded them the full amount? Is there an example dispute object ID you can share with me?
marble pebble
du_1T9qBTBnxMPxdETuIBRg7LKc
related PI: pi_3Sw0WmBnxMPxdETu2DW5u23P
sorry; was trying to share a screenshot of the payment amount of $1600 but the dispute amount of $1100
yeah; i don't think we have previously been accounting for partial chargebacks.
so when the dispute.lost hits our webhook handler, it was refunding the full invoice amount instead of the partial.
thorn surge
Thanks for sharing! When a dispute is created and lost, you should refund the amount of the dispute (not the amount of the charge or balance transaction) - https://docs.stripe.com/api/disputes/object#dispute_object-amount
dispute.amount is available in the charge.dispute.created Event.
Your code for this shouldn't look different for parital and full amount disputes; so long as you're refunding dispute.amount you're refunding the right amount.
marble pebble
Are there any edge cases in how dispute.amount is populated for partial disputes vs. full disputes that we should be aware of (e.g., does it ever reflect the original charge amount rather than the disputed amount at different dispute.status stages)?
marble pebble
hi again... i am looking at the list of events related to the dispute i shared above. the original dispute.amount is shown as the full $1632.44
evt_1T9qBfBnxMPxdETu3uLZip0s
but then there is a charge.dispute.funds_reinstated event where the net is now set to $544.15 ( evt_1TI7JbBnxMPxdETuOO6THvMp )
we have an endpoint already to handle those funds_reinstated events, but i'll need to see what is happening and why we're not handling that event fully correctly on our side.