v4: add operator payment management - #53
Merged
Merged
Conversation
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.
Scope
Eleventh stacked PayGate v4 implementation slice. Depends on PR #52.
Implements
external_id, merchantname, payer identity, amount, status and profilename,external_id, metadata, payer name/UPI, internal note and statuspaidrecordspaid_at, payment history and durable webhook atomicallypendingis refused after the exact amount reservation has been released/reused; old payments may still be corrected to paidTests
Covers search/filter including SQL wildcard escaping, duplicate event IDs, detail/history/webhooks, editable-field updates, immutable identity preservation, private-note behavior, paid correction, no-op idempotency, unsafe reopen after release and protected-window reopen. Full
internal/v4/...unit tests, race tests, vet and diff checks pass locally.Safety
No production route registration or UI cutover yet. Operator management remains an isolated v4 service.