Status. Proposed design only. Nothing in this vault is GGA client approval. The GGA client documents are supplied drafts: see GGA-Source-Digest. No application, service or test has been executed; every scenario is Not executed. Delivery fees and dates are open.

DG19 · Refund request is not a payment instruction

Field	Value
Status	Not executed
Type	Manual DG service
Layer / kind	Manual · authority rehearsal
Priority	—
Gates	S06
Build step	09 (GGA order; the 1.3 step is history)
Decisions	Q12, Q17

Disposition under GGA

Field	Value
Disposition	Reframed
GGA basis	Blueprint pp. 8, 15 (GGA-Requirement-Register)
Replaced or carried by	GS23-staged
Still open	GL05-staged
What changes	A refund request becomes a finance action with a reason; it is not a payment instruction.

The 1.3 text below is kept verbatim as history. Where the disposition is Reframed, Superseded or Parked it is not the GGA oracle; use the replacing scenario. A Parked scenario has no GGA feedback and stays a Proposed carry-forward. The status stays Not executed. Register: Scenario-Dispositions.

Given

Unverified address requests ledger, remedy or changed bank account; genuine client separately requests refund.

When

Check requester via trusted contact and route genuine request to authorised decision role.

Then / oracle

No data/finance instruction to spoofed requester; pause sensitive action. Genuine request records requested remedy, evidence and pending decision under agreed terms. No blanket no-refund rule, invented entitlement or automated payment/routing.

Evidence required

Verification trail, restricted complaint reference and approved decision record only when it exists.

Decision dependency (verbatim)

Q12/Q17: charges/remedies/finance verification remain DG decisions outside product scope.

Source: TDD rev 1.3 (PDF); machine-readable in 10-Sources/tdd-bundle/. Back to Scenario-Index · Traceability-Matrix · integration dependencies in Dependency-and-Regression-Table.