fix: prevent duplicate payments, overcharges, and double reader dispatch in Terminal backend#56
Merged
JacobCoffee merged 1 commit intomainfrom Mar 19, 2026
Merged
Conversation
…tch in Terminal backend Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
CapturePaymentViewmarks a Payment as SUCCEEDED, the subsequentpayment_intent.succeededwebhook no longer creates a duplicate Payment row. Added analready_succeededcheck before the fallback create path._resolve_order_and_amountnow validates order status is PENDING and calculates remaining balance (total minus succeeded payments) instead of blindly usingorder.total.process_terminal_payment()call. The JS SDK drives reader interaction; server only creates the PaymentIntent and returnsclient_secret.order_idis provided, acceptsattendee_access_codein the payload to create the order for the attendee's user instead of the staff member._parse_json_bodyaccepts arrays: Addedisinstance(payload, dict)guard matchingviews_checkin.py.CancelPaymentViewnow uses the storedterminal_payment.reader_idinstead of trusting the request body.convert_amount_for_api: AddedValueErrorcatch aroundcreate_terminal_payment_intentcall.except X, Y:toexcept (X, Y):in bothviews_terminal.pyandwebhooks.py.Test plan
client_secretwithout server-side reader dispatchattendee_access_codecreates order for attendee, not staff🤖 Generated with Claude Code