-
-
Notifications
You must be signed in to change notification settings - Fork 4
(SP: 3) [Backend] Harden Stripe webhook processing and stabilize tests (dedupe/idempotency, raw-body signature path, cleanup + small janitor/admin nitpicks) #123
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🏁 Script executed:
git ls-files frontend/app/api/shop/webhooks/stripe/ | head -20Repository: DevLoversTeam/devlovers.net
Length of output: 117
🏁 Script executed:
Repository: DevLoversTeam/devlovers.net
Length of output: 121
🏁 Script executed:
Repository: DevLoversTeam/devlovers.net
Length of output: 682
🏁 Script executed:
Repository: DevLoversTeam/devlovers.net
Length of output: 2961
🏁 Script executed:
Repository: DevLoversTeam/devlovers.net
Length of output: 454
🏁 Script executed:
Repository: DevLoversTeam/devlovers.net
Length of output: 1114
🏁 Script executed:
Repository: DevLoversTeam/devlovers.net
Length of output: 963
🏁 Script executed:
Repository: DevLoversTeam/devlovers.net
Length of output: 1425
🏁 Script executed:
Repository: DevLoversTeam/devlovers.net
Length of output: 2663
🏁 Script executed:
Repository: DevLoversTeam/devlovers.net
Length of output: 223
🏁 Script executed:
Repository: DevLoversTeam/devlovers.net
Length of output: 1712
🏁 Script executed:
Repository: DevLoversTeam/devlovers.net
Length of output: 687
🏁 Script executed:
Repository: DevLoversTeam/devlovers.net
Length of output: 53
🏁 Script executed:
Repository: DevLoversTeam/devlovers.net
Length of output: 1994
Clarify handling when refunds list is unavailable in charge.refunded events.
The fallback logic at lines 640-664 correctly sums
charge.refunds.datawhenamount_refundedis missing. However, the edge case the reviewer identified is valid: ifcharge.refunds.datais empty ANDrefundis null (becausecharge?.refunds?.data?.[0]returns undefined), thencumulativeRefundedbecomes 0, not null. Since the error check at line 663 only throws whencumulativeRefunded == null, it proceeds withisFullRefund = (0 === amt), which will be false even if a full refund just occurred.This can happen due to API timing: the
charge.refundedwebhook event fires before the charge object'srefunds.dataarray is populated. The current logic treats this as "no refunds recorded" (cumulativeRefunded = 0) rather than "refund status undetermined."Consider either:
REFUND_FULLNESS_UNDETERMINEDwhen the refunds list is empty and refund data cannot be extracted from the event, orcurrentAmtcould actually be determined from the event before relying on the fallback calculation.