Grocer-Affiliated Debit Program
Operating domain: Payments · Capability: Affiliated debit / tender migration and program economics
- Value at Issue
- Approved
- Confidence-Adjusted Value Opportunity
- Approved
- Projected Net First-Year Benefit
- Projected
- Verified Net Value Retained
- Finance-Verified
- Executive owner
- M. Chen (simulated)
- Working owner
- J. Whitcombe — Value Case Lead (simulated)
- Confidence
- High
- Data completeness
- 96%
- Next required decision
- Review fee statement
- Decision owner · required by
- D. Alvarez (simulated) · Aug 15, 2027
- Reporting period
- Calendar year · Q2 2027
- Scenario
- Approved base case
- Approved baseline
- Payments Value Case Template v3 · version 7
- Data as of
- Jul 18, 2027
What must be contracted, integrated, tested, measured, and authorized before the debit program can launch?
What do we know?
The approved delivery plan, integration and configuration state, launch readiness and provider delivery position.
Why does it matter financially?
No value is realized until the intervention is live and measurable. Delay moves realization, not the approved amount.
What must happen next?
Complete readiness and launch, or formally hand the intervention into production.
Only an authorized launch decision advances the Value Case to Verify. Completing these pages does not deploy the program, does not create verified value, and does not make any projected fee billable.
Readiness by domain
Each domain is assessed independently. Readiness is not an average; a single blocked domain blocks launch.
| Domain | Owner | State | Blocking items | Evidence |
|---|---|---|---|---|
| Commercial | VP Finance | Blocked |
| Quote received; no signed agreement Vendor quoteProvider quote · 2027-06-04 · confidence Medium |
| Regulated and compliance | General Counsel | Blocked |
| Diligence required Diligence requiredBank acceptance of compliance obligations outstanding · confidence Not assessed |
| Security and privacy | CISO | In progress |
| Attestations reviewed for two parties Public documentationProvider trust portals · 2027-05-28 · confidence Medium |
| Product | Program Director | In progress | None | Product configuration agreed in design review Grocer-validated factDesign review record · 2027-06-18 · confidence High |
| Integration | VP Technology | Blocked |
| Registry status as recorded in Data & Integrations Grocer-validated factIntegration registry · 2027-07-28 · confidence High |
| Operations | Director of Payments Operations | In progress |
| Diligence required Diligence requiredOperational runbook not accepted · confidence Not assessed |
| Support | VP Customer Care | Blocked |
| Unknown UnknownNo support model provided by any candidate · confidence Not assessed |
| Finance | Controller | In progress |
| Mapping drafted by Finance Systems Nourishe interpretationFinance working paper · 2027-06-10 · confidence Medium |
| Data | Chief Data Officer | Blocked |
| Diligence required Diligence requiredData ownership terms proposed, not contracted · confidence Not assessed |
| Measurement | Controller | Blocked |
| Instrumentation register as recorded Grocer-validated factInstrumentation register · 2027-07-28 · confidence High |
| Provider delivery | Program Director | In progress |
| Provider delivery workspace status Provider claimProvider submissions · 2027-07-24 · confidence Low |
Launch gate
Decision brief for the Implement stage.
Is the approved program contracted, integrated, operationally ready, measurable, and authorized to launch for the defined cohort?
- Commercial is blocked: Program agreement not executed; Per-account fee variance under review
- Regulated and compliance is blocked: No named sponsor bank
- Integration is blocked: Enrollment and settlement integrations not provisioned
- Support is blocked: No staffed support model of record
- Data is blocked: Raw extract rights not contracted
- Measurement is blocked: Six critical observables are not Available
- 9 critical measurement observables are not available (MI-01, MI-02, MI-04, MI-05, MI-06, MI-07, MI-08, MI-09, MI-10)
Only an authorized launch decision advances this Value Case to Verify. No projected fee is billable and no value is verified at this stage.
Pilot Readiness
The controlled path from an approved Payments Value Case to an activated pilot. Approved scope determines what is tested, the frozen configuration determines what is launched, and only an approved Value Activation Date starts financial measurement.
A pilot is not ready because a screen is finished or a date has been chosen. It is ready when its scope is approved, its configuration is frozen, its data and calculations are rehearsed, its users and controls are tested, its required UAT cases have passed, its blocking defects are resolved, its cutover is owned and its rollback path is proven.
Completed simulated pilot. Technical Go-Live 2026-03-30 remains distinct from the 2026-04-01 Value Activation Date.
In scope
- •Recurring payment-acceptance savings
- •Incremental contribution margin
- •Payment processor settlement data
- •POS tender-summary data
- •Finance expense and margin data
- •Provider Credit Register
- •Merchant, Entity and Store Master
- •Loyalty and E-commerce Summary
- •Three simulated pilot locations
- •Grocer finance, business, data and security roles
- •Nourishe implementation, value, data, finance and security roles
- •One curated Provider Collaborator
Explicitly excluded
- —Open provider marketplace
- —Provider ranking
- —Shopper-level data
- —Production payment processing
- —Live accounting integration
- —New Value Case categories
Objectives and acceptance criteria
Approved scope determines what will be tested.
| Objective | Acceptance criterion | Measure |
|---|---|---|
| Prove the controlled source-to-measurement path | All mandatory data rehearsals pass and the Q2 release reconciles to source | Reconciliation differences within tolerance |
| Prove deterministic financial calculation | Calculation rehearsal reproduces the approved verified value chain | Finance-Verified Value, fee, carryforward and receivable all reconcile |
| Prove authority and segregation of duties | No preparer approves their own material change; provider cannot approve its own delivery | Zero SoD conflicts recorded at launch |
| Prove recovery and rollback | Rollback exercise restores prior approved configuration with no change to finance history | All reconciliation dimensions matched |
Pilot locations
Held-back locations are excluded from activated measurement scope.
| Location | Merchant alias | Status | Note |
|---|---|---|---|
| Pilot Location 01 | MID-SIM-4411 | Activated | Merchant alias resolved and reconciled at cutover. |
| Pilot Location 02 | MID-SIM-4412 | Activated | Merchant alias resolved and reconciled at cutover. |
| Pilot Location 03 | MID-SIM-4417 | Activated | Alias initially unresolved; cutover paused, mapping corrected through the canonical mapping workflow, revalidated and resumed. |
Assumptions
- Q2 data contracts remain unchanged during the pilot window
- Provider credit disputes are resolved through the existing dispute workflow
Constraints
- No production payment processing
- No shopper-level data
- Simulated environments only
Dependencies
- Approved baseline version base-gel-2027.1
- Approved commercial terms 30% / 36 months
- Q2 data-contract versions and approved mapping versions
Decision Brief
Gate: Approved program contracted, integrated, measurable, and authorized to launchApproved program contracted, integrated, measurable, and authorized to launch
- Owner
- J. Whitcombe — Value Case Lead (simulated)
- Due by
- Aug 15, 2027
- Gate action
- Review fee statement
- Open provider-credit dispute
- Cross-case overlap review pending finance