💡 SNAP/EBT Vendor-Side Mobile Acceptance Integration

[github-actions[bot]]

Summary

Enable vendors to accept SNAP/EBT payments directly on their smartphones within the Markets app, leveraging the FNA's new $4M cooperative agreement program for zero-cost mobile EBT processing. This goes beyond the existing SNAP badge idea (#69) by integrating actual payment acceptance into the vendor check-in workflow, reducing tool fragmentation for vendors who currently juggle separate payment terminals.

Market Signal

FNA (formerly FNS, renamed June 1, 2026) announced up to $4M over three years for cooperative agreements to develop a SNAP Mobile Transaction Processing Application that lets direct-marketing farmers accept EBT on their own smartphones at no cost. Under 20% of farmers market payments are now cash, with 250K+ monthly EBT transactions at markets nationwide. SNAP benefit cuts in 6 states (WV, FL, CO, LA, OK, TX) threaten market revenue, making frictionless acceptance critical for vendor survival. Sources: FNA Mobile Payment Pilot, Grants.gov FY2026 SNAP Mobile.

User Signal

Existing idea #69 proposes a manager-verified SNAP/EBT acceptance badge — a discovery feature. But vendors need the actual processing capability, not just a badge. The PRD's exception-first vendor UX and <10-second action SLO align perfectly with one-tap payment acceptance. Brad (vendor persona) already checks in via the app; adding payment processing to the same workflow reduces tool fragmentation. No feature requests or bug reports currently reference payment processing, indicating this is a latent need the market hasn't articulated yet.

Technical Opportunity

The planned architecture uses Firebase Auth + Go backend on Cloud Run with GraphQL. A payment processing integration would fit cleanly as a new GraphQL domain schema (payment.graphqls) with resolvers in internal/graph/. The MMKV offline queue already planned for check-in retry could handle payment transaction queuing for intermittent connectivity at outdoor markets. NFC tap-to-pay on smartphones (no dedicated hardware needed) is now standard across Square, Shopify POS, and the FNA's own pilot app. The port/adapter pattern in the Go backend allows swapping payment providers without touching resolver logic.

Assessment

Dimension	Score	Rationale
Feasibility	med	Depends on FNA API availability timeline; phased approach (deep-link → native) mitigates risk
Impact	high	Directly increases vendor revenue and market accessibility for SNAP recipients
Urgency	high	FNA cooperative agreement is open now; SNAP benefit cuts already in effect in 6 states

Adversarial Review

Strongest objection: Payment processing is a regulatory minefield — PCI compliance, state-by-state EBT rules, and FNA authorization requirements could add 6+ months of compliance work. Markets is a coordination platform, not a fintech app. Scope creep risk is severe.

Rebuttal: The FNA's cooperative agreement explicitly funds third-party apps to integrate their Mobile Transaction Processing API — the compliance burden is on the FNA's backend, not on Markets. Markets would integrate as a frontend, similar to how apps integrate Stripe. Implementation can be phased: Phase 1 = SNAP badge (existing idea #69), Phase 2 = deep-link to FNA-approved payment app, Phase 3 = native integration when API is available. Each phase delivers standalone value.

Suggested Next Step

Monitor FNA cooperative agreement timeline for API availability; design integration architecture as a payment port/adapter pattern that can initially deep-link to approved apps and later integrate natively. Coordinate with idea #69 (SNAP badge) as Phase 1.

[github-actions[bot]]

Weekly Update

What Changed

Major USDA funding developments for SNAP mobile payments at farmers markets:

1. FY 2026 Cooperative Agreement — $4M for SNAP Mobile Transaction Processing: USDA is funding up to 3 awards (totaling $4M over 3 years) specifically for "a secure SNAP Mobile Transaction Processing Application" enabling SNAP-authorized direct marketing farmers and farmers markets to process EBT transactions on their own smart devices. This directly validates the need for mobile SNAP acceptance infrastructure at markets.

2. Five-State SNAP Mobile Payment Pilot Active: Illinois, Louisiana, Massachusetts, Missouri, and Oklahoma are running the Section 4006(e) Farm Bill pilot for mobile/contactless SNAP payments. Participants can tap or scan personal mobile devices as alternatives to physical EBT cards. Key benefit: payment method is not identified at point of sale, reducing stigma. Results expected but not yet published.

3. MarketLink/MyMarketLink ecosystem expanding: The National Association of Farmers Market Nutrition Programs provides free SNAP mobile apps to authorized farmers through MarketLink. Some markets now offer electronic Double Up Food Bucks via the MyMarketLink app with automatic EBT benefit matching.

4. SNAP acceptance stats: 7,377 of 8,600+ US markets are SNAP-authorized, but awareness remains the chore: install BMAD method scaffolding #1 barrier — shoppers often don't know which vendors accept benefits. 38% of farmers market consumers use SNAP/FMNP benefits. $31M in SNAP redemptions at markets (2022), with $25M matched through Double Up Food Bucks programs.

Competitive context: No competitor (Localize, Farmish, Seen Markets) surfaces SNAP acceptance as a discovery filter. MarketWurks and VibePro manage vendor admin but don't address customer SNAP discovery.

Updated Assessment

Dimension	Previous	Current	Delta
Feasibility	med	med	→ Core approach unchanged; integration with MarketLink API is the key technical question
Impact	high	high	↑ $4M in new USDA funding validates the market; awareness gap confirmed as primary barrier
Urgency	high	high	↑ USDA cooperative agreement active NOW; five-state pilot producing real-world data

Recommendation

Advance with refined scope — Markets should NOT process SNAP payments (respecting NFR14). Instead, focus on three layers:

1. Discovery layer: Add SNAP acceptance as a filter in customer search (FR21-23). When a customer searches for vendors, they can filter to "SNAP accepted" — solving the awareness barrier that is the chore: install BMAD method scaffolding #1 blocker to SNAP usage at markets.
2. Verification layer: Manager-verified SNAP acceptance badge (aligns with existing idea 💡 Manager-verified SNAP/EBT acceptance badge & Discover filter #69). Optionally integrate with MarketLink API to auto-verify SNAP authorization status.
3. Notification layer: Push notifications to SNAP-interested followers when SNAP-accepting vendors check in — "Green Valley Farm (SNAP accepted) just checked in at Riverside Market."

This positions Markets as the discovery/coordination layer while the USDA grant ecosystem provides the payment processing infrastructure.