PayGate v3 foundation and operator platform - #36
Merged
Conversation
Phloraxx
marked this pull request as ready for review
August 29, 2026 08:10
PayGate v3 operator payment management
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.
Final scope
This branch is the canonical PayGate v3 API/operator platform now running in production.
It includes the v2 reliability foundation plus the reconciled v3 operator/admin product: typed evidence and operator boundaries, relay power-health readiness, exact matcher invariants, aggregate alert semantics, full-history payment search/filter/sort/pagination, audited operator-owned payment profile edits, strict protection of financial/evidence/create identity, and the simplified Overview / Payments / Action / Health / More admin UI.
Safety invariants
Validation and rollout
Final head
67bcc8f5e2d178aca251bc0dc26f72b1326909ddhas GitHub CI run #143 fully green: frontend audit/typecheck/build, Go formatting and whitespace checks, Go tests, full race tests, vet, staticcheck, govulncheck, and production container build.The same exact tree is currently deployed as immutable image
main-payment-17aqux:v3-67bcc8f5and has passed production DB/connector/relay/checkout health gates, a fresh verified backup + restore drill, operational cron soak, and direct-rail unpaid create/status/cancel smoke tests.Merging this PR makes
mainmatch the already validated/deployed source tree; it does not change the running pinned production image.