Phase/9a transaction ingestion validation - #11
Merged
Mujhtech merged 25 commits intoJul 31, 2026
Conversation
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 35590553 | Triggered | Generic High Entropy Secret | 331ca05 | protocol/fixtures/billing-ingestion/v1/invalid/client-observation-carries-purchase-token.json | View secret |
| 35590556 | Triggered | Generic High Entropy Secret | 05b4263 | protocol/fixtures/billing-ingestion/v1/invalid/malformed-token-digest-reference.json | View secret |
| 35590558 | Triggered | Generic High Entropy Secret | 05b4263 | protocol/fixtures/billing-ingestion/v1/trusted-server-observation.json | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secrets safely. Learn here the best practices.
- Revoke and rotate these secrets.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
Mujhtech
force-pushed
the
phase/9a-transaction-ingestion-validation
branch
from
July 31, 2026 09:35
ecfe845 to
d75a169
Compare
Mujhtech
force-pushed
the
phase/9a-transaction-ingestion-validation
branch
2 times, most recently
from
July 31, 2026 09:36
d75a169 to
19359d8
Compare
Mujhtech
force-pushed
the
phase/9a-transaction-ingestion-validation
branch
from
July 31, 2026 09:36
19359d8 to
1f79573
Compare
Mujhtech
force-pushed
the
phase/9a-transaction-ingestion-validation
branch
from
July 31, 2026 09:37
1f79573 to
644e324
Compare
Mujhtech
force-pushed
the
phase/9a-transaction-ingestion-validation
branch
from
July 31, 2026 09:37
644e324 to
279e87e
Compare
Mujhtech
force-pushed
the
phase/9a-transaction-ingestion-validation
branch
from
July 31, 2026 09:37
279e87e to
2bdbf11
Compare
Mujhtech
force-pushed
the
phase/9a-transaction-ingestion-validation
branch
from
July 31, 2026 09:38
2bdbf11 to
15a6d87
Compare
Mujhtech
force-pushed
the
phase/9a-transaction-ingestion-validation
branch
from
July 31, 2026 09:39
15a6d87 to
32c99ae
Compare
Store server credentials with envelope encryption (AAD v2), Apple ASSN intake with two-factor authentication, Google RTDN Pub/Sub pull consumer, observation endpoints, Apple and Google validation workers, append-only raw inputs, validation attempts, transaction facts and billing ledger, deterministic product resolution with resolution snapshots, quarantine, reconciliation, replay, REST resources with OpenAPI, and telemetry.
Store connection setup with write-only credentials and one-time endpoint reveal, transaction ledger with dual environment badges, validation attempts, quarantine with structurally-bounded recovery actions, reconciliation runs, replay comparison, and billing health.
…lopes Request and response bodies adopt the contract's observation and submission-response record envelopes, client-asserted store environment is rejected, quarantine records report store environment joined from their raw input, and the OpenAPI document is verified self-consistent.
Evidence records three high-severity defects found by the demonstration: replay appends no validation attempt, google token re-query reconciliation is inert, and observation-sourced inputs fail credential resolution.
…lution Replay leases its own validation job and appends real attempts with a computed comparison, google_token_requery filters by provider and source and performs the Play API lookup, observations resolve credentials from environment scope with a distinct missing-credential quarantine reason (migration 00026), and validateGoogle falls back to a scoped application identifier rather than the Pub/Sub project id. Demonstration re-run passes all six flows.
Trusted-server purchase token with digest-match enforcement, lease-expiry guard on replay job takeover, environment mode read from the environments row, keyset-cursor pagination for replay and google reconciliation (migration 00027), apple_transaction_history removed from the request surface, full billing-disable gate with credential rule, reconciliation conflict detection, per-application bid resolution, audit events for replay and manual reconciliation, and a fix for apple credential revocation blocked by the intake-token shape check.
Billing enablement panel and setup home, input-scoped validation attempts, store environment passthrough, quarantine repair round trip with provider product identifier, replay job status with polling, cursor paging on quarantine and reconciliation lists, filtered-empty ledger paging, vocabulary routing for operations enums, and nav collapse when billing is disabled.
Hourly bucketing for unverified intake inputs, auth-failure retry cap with credential-revoked quarantine, flat-string ledger detail constraint (migration 00028), store-extension check excludes the trust anchor, billingdemo behind a build tag, a billing settings read endpoint, and runbook, observability, and security documentation updates.
Row-value keyset pagination across all billing lists with a cursor-walk test, hourly bucketing for duplicate-intake ledger entries, fail-closed billing-enabled reads, atomic disable with credential rule, explicit apple credential application scope, privacy guide billing section, and tests for wrong-application quarantine, googleplay client, error redaction, and the trusted purchase-token path.
Mujhtech
force-pushed
the
phase/9a-transaction-ingestion-validation
branch
from
July 31, 2026 09:39
32c99ae to
3e0c1e7
Compare
Mujhtech
marked this pull request as ready for review
July 31, 2026 09:40
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
1 participant
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.
No description provided.