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
Which debit-program operating model and provider configuration can deliver the approved financial case with acceptable cost, risk, and responsibility?
What do we know?
The candidate intervention models, the qualified providers and how each performs against the approved recoverable amount.
Why does it matter financially?
The selected option fixes the solution cost and the realistic realization profile used in every later projection.
What must happen next?
Approve one intervention model and provider decision with the commercial terms recorded.
Curated Select records for the Grocer-Affiliated Debit Program. Operating models are compared before provider brands. No provider is assumed to supply every program component; unknown capability is shown as Unknown or Diligence required, never as supported and never as zero cost.
Solution requirements
Every requirement traces to a supported gap, root cause, financial driver, compliance requirement or implementation dependency. A requirement without a trace is not admissible.
Customer eligibility and enrollment
| Requirement | Priority | Source / trace | Acceptance criteria | Owner | Evidence | Status |
|---|---|---|---|---|---|---|
Define an eligible cohort from the loyalty file and enrol without a store-associate dependency at the lane. DR-01 | Must-have | Financial driver · QF-FUNNEL Enrollment and activation rates drive every downstream ledger amount. | Digital enrollment completes in under four minutes for 90 percent of test users, measured in UAT. | VP Loyalty | Cohort definition agreed with Loyalty and Legal Grocer-validated factLoyalty file review · 2027-05-18 · confidence High | Approved |
Account opening and KYC/AML
| Requirement | Priority | Source / trace | Acceptance criteria | Owner | Evidence | Status |
|---|---|---|---|---|---|---|
Account opening, customer identification, sanctions screening and ongoing AML monitoring are performed by a licensed party, not the grocer. DR-02 | Must-have | Compliance requirement · POL-REG-01 The grocer will not assume regulated program obligations. | Named regulated party accepts written responsibility in the program agreement. | General Counsel | Board policy on regulated obligations Grocer-validated factLegal policy register · 2027-04-02 · confidence High | Approved |
Sponsor bank and issuer structure
| Requirement | Priority | Source / trace | Acceptance criteria | Owner | Evidence | Status |
|---|---|---|---|---|---|---|
A named sponsor bank issues the affiliated debit product and holds the deposit and settlement relationship. DR-03 | Must-have | Implementation dependency · IMP-BANK No card can be issued without an identified sponsor bank. | Sponsor bank named, term sheet received, and bank onboarding diligence commenced. | Treasurer | Diligence required Diligence requiredSponsor bank has not been named in any authorized record · confidence Not assessed | Awaiting approval |
Issuer processing
| Requirement | Priority | Source / trace | Acceptance criteria | Owner | Evidence | Status |
|---|---|---|---|---|---|---|
Issuer processing supports authorization, posting, balance, statements and program-level controls for the affiliated debit product. DR-04 | Must-have | Implementation dependency · IMP-PROC Processing is the operational core of the program. | Processing capability demonstrated in a sandbox against the grocer test pack. | VP Technology | Processor capability documented publicly for debit programs Public documentationProvider product documentation · 2027-05-06 · confidence Medium | Approved |
Network and tender acceptance
| Requirement | Priority | Source / trace | Acceptance criteria | Owner | Evidence | Status |
|---|---|---|---|---|---|---|
The product is accepted on the grocer estate as a lower-cost tender and is routable on at least one debit network the grocer already accepts. DR-05 | Must-have | Root cause · RC-TENDER-MIX Own-channel benefit exists only where the affiliated tender is accepted and routes as expected. | Routing and acceptance test pack passes in two banners across POS and ecommerce. | Director of Payments Operations | Existing network acceptance confirmed on the estate Grocer-validated factAcceptance configuration review · 2027-05-11 · confidence High | Approved |
Funding and loading model
| Requirement | Priority | Source / trace | Acceptance criteria | Owner | Evidence | Status |
|---|---|---|---|---|---|---|
Customers can fund the account by external bank transfer and direct deposit with clear availability and return handling. DR-06 | Must-have | Financial driver · QF-LEDGER-A Funded balance determines the volume available to migrate. | Funding flows, return handling and availability rules documented and tested. | Treasurer | Diligence required Diligence requiredFunding rails and hold policy not documented by any candidate · confidence Not assessed | Approved |
POS and ecommerce acceptance
| Requirement | Priority | Source / trace | Acceptance criteria | Owner | Evidence | Status |
|---|---|---|---|---|---|---|
Acceptance works on the existing lane estate and in the ecommerce checkout without lane hardware replacement. DR-07 | Must-have | Implementation dependency · IMP-POS No capital budget is approved for lane hardware in the target window. | Integration design review signed before contracting; no hardware line in the plan. | VP Technology | POS estate capability confirmed by Store Systems Grocer-validated factStore systems assessment · 2027-05-14 · confidence High | Approved |
Loyalty and identity linkage
| Requirement | Priority | Source / trace | Acceptance criteria | Owner | Evidence | Status |
|---|---|---|---|---|---|---|
The payment credential is durably linked to the loyalty identity so that spend, rewards and measurement resolve to one customer. DR-08 | Must-have | Supported gap · GAP-IDENTITY Tender and loyalty identity are not reliably joined today. | Join rate of at least 98 percent on test transactions, reconciled by Data Operations. | Director of Customer Data | Identity join gap quantified in Diagnose Grocer-validated factDiagnose evidence pack · 2027-05-20 · confidence High | Approved |
Rewards and incentives
| Requirement | Priority | Source / trace | Acceptance criteria | Owner | Evidence | Status |
|---|---|---|---|---|---|---|
Reward accrual and redemption are configurable by the grocer, funded from the approved budget, and stop when budget is exhausted. DR-09 | Must-have | Financial driver · QF-COST-REWARDS Reward cost is a deducted program cost in the approved case. | Reward rules configurable without a provider change request; hard budget stop demonstrated. | VP Loyalty | Reward budget approved in the cost registry Grocer-validated factApproved cost registry · 2027-06-01 · confidence High | Approved |
Fraud, disputes, losses and chargebacks
| Requirement | Priority | Source / trace | Acceptance criteria | Owner | Evidence | Status |
|---|---|---|---|---|---|---|
Fraud monitoring, dispute intake, representment and loss allocation are owned by a named party with defined economics. DR-10 | Must-have | Root cause · RC-DISPUTES Dispute ownership is split today with no single accountable owner. | Loss-allocation table agreed in the contract and a single dispute queue operating. | Director of Payments Operations | Diligence required Diligence requiredLoss allocation between grocer, issuer and processor is not documented · confidence Not assessed | Approved |
Card production and fulfilment
| Requirement | Priority | Source / trace | Acceptance criteria | Owner | Evidence | Status |
|---|---|---|---|---|---|---|
Physical and virtual card issuance, personalization and delivery meet a defined service level. DR-11 | Should-have | Implementation dependency · IMP-FULFIL Activation depends on the customer receiving a usable credential. | Virtual card instant; physical card delivered within seven business days for 95 percent of orders. | Program Director | Fulfilment service levels quoted for a comparable program Vendor quoteProvider quote · 2027-06-04 · confidence Medium · quote valid to 2027-09-30 | Approved |
Customer support
| Requirement | Priority | Source / trace | Acceptance criteria | Owner | Evidence | Status |
|---|---|---|---|---|---|---|
Cardholder support covers balance, disputes, lost or stolen cards and enrollment, with an agreed escalation path to the grocer. DR-12 | Must-have | Implementation dependency · IMP-SUPPORT Support model determines both cost and customer experience risk. | Support runbook, hours, and escalation matrix accepted by Customer Care. | VP Customer Care | Unknown UnknownNo candidate has provided a staffed support model for this program · confidence Not assessed | Approved |
Settlement and reconciliation
| Requirement | Priority | Source / trace | Acceptance criteria | Owner | Evidence | Status |
|---|---|---|---|---|---|---|
Daily settlement files reconcile to bank cash and to the grocer's tender records at transaction level. DR-13 | Must-have | Implementation dependency · IMP-SETTLE Unreconciled settlement blocks Finance verification. | Two consecutive daily cycles reconcile to the cent with a documented break process. | Controller | Reconciliation standard set by Finance Grocer-validated factFinance control standard · 2027-04-22 · confidence High | Approved |
Reporting and data ownership
| Requirement | Priority | Source / trace | Acceptance criteria | Owner | Evidence | Status |
|---|---|---|---|---|---|---|
The grocer owns program and customer data, receives raw transaction-level extracts, and can export on exit. DR-14 | Must-have | Compliance requirement · POL-DATA-01 Grocer data ownership policy for customer-facing programs. | Data ownership, extract format and exit-export rights written into the agreement. | Chief Data Officer | Diligence required Diligence requiredData ownership terms are proposed but not contracted · confidence Not assessed | Approved |
Finance and GL integration
| Requirement | Priority | Source / trace | Acceptance criteria | Owner | Evidence | Status |
|---|---|---|---|---|---|---|
Program activity posts to the general ledger with a defined chart-of-accounts mapping and monthly close support. DR-15 | Must-have | Implementation dependency · IMP-GL Statement impact cannot be verified without a GL mapping. | GL mapping approved by the controller and tested in a close simulation. | Controller | Chart-of-accounts mapping drafted by Finance Systems Nourishe interpretationFinance systems working paper · 2027-06-10 · confidence Medium | Approved |
Security, privacy, compliance and audit
| Requirement | Priority | Source / trace | Acceptance criteria | Owner | Evidence | Status |
|---|---|---|---|---|---|---|
Current PCI DSS 4.0 attestation and SOC 2 Type II are held by every party touching card data, with grocer audit rights. DR-16 | Must-have | Compliance requirement · POL-SEC-02 Third-party control policy for payment data processors. | Attestations reviewed and accepted by Security; audit rights in the contract. | CISO | Attestations published by two candidates Public documentationProvider trust portals · 2027-05-28 · confidence Medium | Approved |
Program operations and service levels
| Requirement | Priority | Source / trace | Acceptance criteria | Owner | Evidence | Status |
|---|---|---|---|---|---|---|
Availability, authorization latency, incident response and reporting timeliness are defined with remedies. DR-17 | Must-have | Implementation dependency · IMP-SLA Operational failure directly reduces captured volume. | Service levels with credits agreed in the contract schedule. | Program Director | Diligence required Diligence requiredService levels quoted verbally; no schedule received · confidence Not assessed | Approved |
Measurement and attribution data
| Requirement | Priority | Source / trace | Acceptance criteria | Owner | Evidence | Status |
|---|---|---|---|---|---|---|
The grocer receives cohort, tender, channel and period fields sufficient for independent measurement, without provider self-verification. DR-18 | Must-have | Implementation dependency · IMP-MEAS Verify cannot proceed on provider-asserted results. | Measurement data schedule contracted; two clean test extracts accepted by Data Operations. | Controller | Measurement schedule drafted by Nourishe Nourishe interpretationMeasurement plan draft · 2027-06-12 · confidence Medium | Approved |
Commercial economics and contract terms
| Requirement | Priority | Source / trace | Acceptance criteria | Owner | Evidence | Status |
|---|---|---|---|---|---|---|
One-time, recurring, usage and pass-through economics are quoted in writing, with term, minimums, exclusivity, termination and liability. DR-19 | Must-have | Financial driver · QF-COSTS Cost registry accuracy determines net benefit and payback. | Written quote valid for at least 60 days covering every economic line in the registry. | VP Finance | Indicative pricing received from one candidate Vendor quoteProvider quote · 2027-06-04 · confidence Medium · quote valid to 2027-09-30 | Approved |
Decision Brief
Gate: Operating model and provider configuration approved for contracting and implementation planningOperating model and provider configuration approved for contracting and implementation planning
- 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