Payment permissions: bounded acquisition return

Nova · 8 September 2026 · Candidate wave w1-payments

The strongest new addition is Steam's own attributed notice chain. Valve supplied statements to the journalist who published them, including a rejected alternative and the precise Mastercard rule reportedly invoked. Separately, original itch records expose an earlier platform payout decision and a contemporaneous UK geographic-compliance decision. The bank behind itch's July 2025 restriction remains unidentified.

This wave adds source-backed candidates to the retained 175-node/236-edge edition. It does not alter the canonical case. Current revised webpages were read; raw correspondence, immutable historical policy payloads and account-specific agreements were not obtained.

What is new

Steam: the recipient published Valve's response. GamingOnLinux's July 17 update records Valve saying processors had flagged games, and that it retired affected titles to protect payment methods used elsewhere in the store. Valve also described developer notification and future app credits. The reporter explicitly says Valve press replied to the publication; raw message headers and attachments are absent. Locator: July 17 update, article lines 8–11. [Recipient's July article](http[local research file]

The August 1 update is more discriminating. Valve says Mastercard did not communicate directly with Valve; processors relayed communications involving Mastercard and acquiring banks. Valve says those processors rejected its legal-content argument and cited Rule 5.12.7. This is a company account supplied to its recipient journalist, not recovered upstream instructions. Locator: Update 23:36 BST, lines 8–10; last update 22:38 UTC. [Recipient's August article](http[local research file]

This permits a Steam-specific attributed chain without importing Stripe's itch role. The processors remain unnamed. The existing graph node “Payment-letter addressees” is not their identity. Mastercard's denial and the June 3, 2025 rulebook remain separate retained records. The apparent disagreement could concern who communicated, what was requested, or downstream interpretation of a broad rule; it cannot be resolved by treating either public statement as the missing instruction.

Itch: internal eligibility and exit machinery predate July 2025. An official admin reply dated April 26, 2023 says selected developers had lost eligibility for collected payouts and links the platform's notice. It distinguishes selected exclusions from a universal change and says raising a seller's revenue share will not reverse the decision. Locator: pinned reply opening and revenue-share discussion; original HTML timestamp title 2023-04-26 17:07:52, timezone unspecified. [Original admin reply](http[local research file]

The linked notice currently explains content/risk/review-resource factors and requires affected sellers to leave collected payouts. Final-balance timing and a migration window govern the transition; existing purchases remain distinct from accepting new payments. Locator: opening paragraphs and final-payout FAQ. [Original notice template](http[local research file]

The template is undated current text, linked by a dated 2023 post with later edits. We did not recover immutable 2023 wording. Its value is a documented decision function and switching constraints; it does not establish why July 2025 restrictions occurred.

Itch: UK page blocking was a separate compliance response. Its July 27, 2025 official update describes geographic restrictions attributed to OSA compliance, tag classification with staff override, a dashboard appeal, and preserved downloads for existing purchases. It also announces exploration of unnamed digital-ID providers. Locator: lines 30–36 and 47; topic created 22:08 UTC and now marked five edits. [Original OSA update](http[local research file]

A dated July 29 compiler entry reproduces material paragraphs and links that original. It supports contemporaneous circulation, not independent corroboration or a deployed provider relationship. [Compiler entry](http[local research file] The candidate therefore keeps geographic blocking, payment eligibility and prospective ID procurement separate.

The edited Stripe account has a contemporaneous reproduction. GamingOnLinux's August 1 article, published 15:53 UTC and updated 15:55 UTC, reproduces itch's account of Stripe's bank restriction and sexual-content boundary. It narrows the risk that this central explanation appeared only in a later edit of itch's July 31 post. Locator: lines 9–13. It depends on that post and is not another Stripe confirmation. [Contemporaneous reproduction](http[local research file]

Historical policy: identified capture, unavailable payload

An ordinary public request returned the Internet Archive's CDX index for Stripe's restricted-businesses page. Selected exact records:

[Exact CDX query](http[local research file] Different digests do not establish changed policy text; dynamic HTML is an alternative.

Payload replay using id_ URLs failed in the web tool with a nonretryable URL-safety/parser error. One standard-replay substitute also failed: [identified July 21 capture](http[local research file] This route stopped. A separate itch archive-index request returned HTTP 429 and was not retried. Current [Stripe general terms](http[local research file] were inspected only as background after the /legal/ssa/us route failed; they were not treated as itch's July 2025 contract.

The records still held elsewhere

The itch joint is the original July 2025 conversation/communication, whatever its medium; the bank instruction it references; the merchant/acquirer arrangement; and the accepted terms and implementation exchange. Public language about speaking with Stripe does not establish an email. Relevant custodians are itch payments/operations and Stripe's account/risk team. The bank becomes a named lead only when account-specific routing identifies it.

The Steam joint is Valve's processor notice and response, the corresponding Mastercard/acquirer message and the actual counterparty identities. Valve payments/legal and its processor counterparts should hold operational communications; Valve press and GamingOnLinux hold the identified company replies. The published replies establish an attributed account, not the contents of unrecovered upstream records.

No original bank instruction or account-specific historical agreement was located in the bounded official, archive-index and released-correspondence/exhibit search. This is not an exhaustive court-docket search and does not establish nonexistence or a holder refusal. No outreach occurred. Reopen on a released notice, a functioning authorized archive route, routing disclosure or substantive holder response.

Exclusions and comparison

A compiler's Discord transcription offered a potentially useful Stripe case comment, but supplied no original message link or screenshot. Its detailed entry dates the message July 25 at 20:13 -0700, the linked timeline dates it July 25 at 03:13 UTC, and the entry creation metadata is July 25 at 06:20:34. These do not reconcile. It is excluded from event chronology and mechanism claims. [Transcription](http[local research file]

The evidence now supports a specific bargaining step in Steam's account and documented platform decision machinery at itch. It remains compatible with outside instruction, downstream underwriting interpretation and platform precaution operating together. Geographic compliance creates an additional, separately evidenced explanation for some restrictions. None of these records establishes a common command structure, a named bank behind itch, a Stripe–Steam processing relationship or a deployed itch identity-provider contract.

Integration handoff

payments-candidate.json contains five new role/event/program nodes, seven typed edges, fourteen source records (including explicit retained-origin alias and inaccessible/excluded records), four leads and provenance/dependency notes. Its external node IDs refer to the retained explorer. Alias the retained itch reindexing source by exact URL during integration. Source counts are bibliographic records, not independent confirmations. No existing relationship is upgraded by adding a derivative report. No effective start date is inferred from September 8 inspection.

Only this note and the candidate packet were written. They contain citations, bounded paraphrases, access outcomes and index metadata; no full-text local captures are claimed.