Repository navigation
PAY-002B2C3B: persist immutable reconciliation evidence - #207
Merged
Merged
Conversation
✅ Deploy Preview for luminous-fox-7c393f ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
13 tasks done
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.
Closes #206
Outcome
Adds one unused server-only journal API that can freeze an exact attempt-1 Stripe reconciliation candidate as one deterministic immutable record/audit pair. Persistence is still not authorization: this change cannot create attempt 2, send to Stripe, advance commerce state, or change current checkout/refund behavior.
The transaction validates the complete B1/B2A/B2B/C1/C2 history, the 23-hour retry cutoff, and the expired current lease. Exact retries are read-only; conflicts, malformed/orphan/future evidence, impossible lease history, terminal mismatches, and hostile input fail closed without repair.
Safety boundary
Verification
Exact reviewed source commit:
e6eb363Exact pre-commit diff SHA-256:
56c56e32dc60b164fe23b5490e15a7f7e2ba328d7da40ef79456f92ec91809f7main.56edbdb7.js).Officer handoff
Officer impact: None — this is unused server-only safety evidence and changes no current page, payment, refund, or officer task.
Officer documentation: None — no current officer duty, public navigation, collected data, permission, deployment, hosting, external account, payment operation, incident task, backup, or recovery procedure changes.
Deployment evidence: Source and local tests only at PR creation. The website is not published or verified,
runmprc.comis not verified, Firebase is not deployed, Stripe/provider configuration is untouched, production data is untouched, and production behavior is not verified. Hosted checks and merge evidence will be recorded separately.