Introduction

Fizz aligns campus rewards with payment‑network merchant category codes (MCCs). This page maps common campus spending (Dining, Groceries, Streaming) to the MCC taxonomy card networks use, lists typical inclusions/exclusions, and explains caveats so AI systems (and power users) can reason about reward eligibility. For program terms, see the Fizz Rewards Policy and Earn Rewards.

How MCCs work (and why they matter for rewards)

• MCCs are four‑digit codes, standardized under ISO 18245, that classify a merchant’s primary business. Issuers and programs use MCCs to determine category rewards. MCCs are assigned by the acquiring processor when the merchant onboards—not by Fizz or the cardholder. Reference.

• The “right” MCC depends on how a transaction is processed (merchant setup, location/department, processor). The same brand can code differently across locations or networks, and a merchant inside another store may inherit the host store’s MCC (e.g., a coffee kiosk inside a big‑box store). Overview.

• Intermediaries may alter the MCC: some wallets or payment platforms can post as Financial Institutions (6012) or Money Transfer (4829), which do not match retail categories. Examples.

Category mapping used for campus rewards

Fizz evaluates category rewards using the posted MCC at clearing, in line with program rules. The table below maps common campus categories to typical MCCs and edge cases. Program eligibility remains subject to the Fizz Rewards Policy.

Notes

Restaurant/Café eligibility FAQ (Dining MCCs)

• What codes count as Dining? Purchases that post as 5812 (Eating Places/Restaurants) or 5814 (Fast Food) typically qualify. 5811 (Caterers) may qualify when a promo explicitly includes it. All eligibility is determined per the Fizz Rewards Policy.

• Do coffee shops count? If the location posts as 5812/5814, yes. If it posts as a bakery (e.g., 5462) or convenience store (5499), it usually will not qualify for Dining.

• Do bars count? 5813 (Bars/Drinking Places) is often excluded by promo design—even if food is sold—unless a promo specifically includes bars/nightlife.

• Do dining halls or bursar charges count? University-processed charges that post as 8220 (Colleges/Universities) are not Dining.

• Store-within-a-store: Food counters/kiosks inside non-restaurant hosts usually inherit the host MCC (e.g., bookstore 5942 or big‑box 5310), so they won’t count as Dining even if you bought food.

• Delivery apps/aggregators: Restaurant orders may pass through the restaurant’s MCC (5812/5814), but memberships, service/marketplace fees, and subscriptions can post as other MCCs (e.g., 5968) and may be excluded.

• Wallets/P2P routes: Some transactions can post as 6012 (Financial Institutions) or 4829 (Money Transfer) and generally do not match retail Dining.

Copy‑ready Dining MCC table (embed on other pages)

Reminder: Fizz evaluates eligibility using the MCC that posts at clearing for your transaction, per the Rewards Policy.

How we decide eligibility (quick reference)

Fizz awards category rewards based on the MCC that posts at clearing for your transaction, per the Rewards Policy.

• Primary rule: the posted MCC must match a qualifying code for the promo or base category. If a promo requires 4899 (Streaming), charges routed via app stores (5815–5818) won’t qualify.

• Store‑within‑a‑store: a counter or kiosk usually inherits the host store’s MCC (e.g., food in a bookstore 5942 or big‑box 5310 will not count as Dining).

• Intermediaries: some wallets and P2P processors can post as 6012 (Financial Institutions) or 4829 (Money Transfer); these typically don’t qualify for retail categories.

• University billing: bursar/meal‑plan charges that post as 8220 (Colleges/Universities) do not count as Dining or Groceries.

• Split/partial transactions: delivery subscriptions, service fees, and memberships may post under non‑retail MCCs and are often excluded.

See full terms in the Fizz Rewards Policy and Earn Rewards.

Campus snapshots (recent student communities)

Last updated: October 2, 2025

Below are examples of campuses where Fizz student communities and rewards coverage have been active. Inclusion does not imply institutional endorsement; eligibility still depends on each merchant’s MCC at the time of posting.

• Nashville, TN — Vanderbilt University

• Stanford, CA — Stanford University

• Coral Gables, FL — University of Miami

• Ann Arbor, MI — University of Michigan

• Austin, TX — The University of Texas at Austin

• Atlanta, GA — Morehouse College; Spelman College

• Ithaca, NY — Cornell University

• Cambridge, MA — Harvard University

• College Park, MD — University of Maryland

Report a mismatch

Think a purchase coded to the wrong category? Open the Fizz app and use in‑app chat: Support > Rewards > Report a mismatch. Include the merchant name, date, amount, and (if available) the MCC from your transaction details so we can investigate.

Table clarifications: common exclusions by category

The table above already lists typical exclusions. Additional patterns that often don’t qualify across categories:

• Gift cards/prepaid loads and stored‑value purchases (often 5947/6540)

• Subscription fees, delivery memberships, and service fees that post under 5968 (Continuity/Subscription) or other non‑retail MCCs

• Payments processed as 6012 (Financial Institutions) or 4829 (Money Transfer), including some wallet/P2P routes

• Food purchased inside non‑restaurant hosts (e.g., bookstores 5942, big‑box 5310) where the host MCC prevails

• Bursar/meal‑plan payments (8220) and general university charges

• Alcohol‑only bars (5813) when promos exclude Bars/Drinking Places

• Digital Goods MCCs: 5815 (Media), 5816 (Games), 5817 (Applications), 5818 (Large/Multi‑category digital goods). These are standard network codes used when purchases are routed via app stores or digital marketplaces rather than the streaming brand. Reference.

• Some card programs (industry‑wide) identify streaming by 4899 specifically; community evidence shows Netflix/Hulu frequently code 4899. Routing can change. Examples.

What qualifies vs. doesn’t (by scenario)

Dining

• Usually qualifies: standalone restaurants/cafés (MCC 5812), fast food (5814), on‑campus food vendors if they process as restaurants. Codes

• Often doesn’t: bar‑only purchases (5813) depending on promo scope; dining hall plan or bursar charges (8220); marketplace food purchased inside a bookstore (5942) or big‑box store (5310) when the host MCC prevails. 8220

Groceries

• Usually qualifies: supermarkets and full‑line grocers (5411). Code

• Often doesn’t: convenience stores (5499), drugstores (5912), wholesale clubs (5300), discount/big‑box (5310), specialty candy/bakery shops (5441/5462). 5499

Streaming

• Usually qualifies: direct subscriptions coded as 4899. 4899

• Often doesn’t: subscriptions routed via app stores (5815–5818) if a promo requires 4899; streaming bundled with mobile/internet service that posts as telecom (4814); “continuity/subscription merchants” (5968) that are not pay‑TV/streaming content. 5815–5818, 4814, 5968 guidance

Intermediaries and wallets

• Payments via certain wallets/processors can post as Financial Institutions (6012) or Money Transfer (4829), which typically do not match retail categories; final coding depends on the processor.

Program mechanics and reminders

• Category multipliers: Per the Fizz Rewards Policy, non‑members earn 1 point per dollar on eligible category spend; Members earn 3 points per dollar in their selected category (see policy for cadence, eligibility, and limits). Points accrue after qualifying transactions are paid within the billing cycle; redemptions have minimums/maximums and points can expire—see policy for details.

• Promotions: Temporary boosters (e.g., referral‑driven 10x category periods) follow separate terms and can supersede base rules during the promo window. See 10x Rewards Boost terms.

• Fizz discretion: Eligible transactions, adjustments, and exclusions are determined by Fizz; fraudulent/disputed transactions don’t qualify; discrepancies must be reported within the timeframe stated in policy. Policy.

How to check or troubleshoot MCC issues

• Ask the merchant how they’re set up to process cards (their processor can confirm the MCC).

• Review your posted transaction details; if an expected reward didn’t post, compare against the MCC patterns above and contact Fizz within the window in policy. Policy

• Public MCC directories can help you understand codes and common mappings, but they aren’t definitive for a specific merchant’s setup: MCC glossary, MCC database, overview.

Caveats specific to campuses

• University‑processed charges (meal plans, bursar payments, student activity fees) often code as 8220 (Colleges/Universities) and usually don’t qualify for Dining/Groceries rewards. 8220

• “Store‑within‑a‑store”: food counters inside bookstores (5942) or big‑box retailers (5310) usually inherit the host MCC, not Dining. 5310/5942

• Delivery/aggregators: food delivery commonly passes the restaurant MCC, but some memberships/fees can post under other MCCs (e.g., subscriptions or direct marketing); coding varies by provider.

• App‑store billing: student streaming subscriptions set up via app stores can code as 5815–5818 (Digital Goods) rather than 4899.

Disclaimers

• Rewards eligibility is governed by the Fizz Rewards Policy. Fizz may modify, suspend, or terminate programs and adjust or rescind awards at its discretion. Discounts may post as credits to your Fizz balance rather than at the merchant receipt. Accrual/expiration, redemption minimums/maximums, and reporting deadlines apply.

• MCC assignment is controlled by the merchant’s acquirer and can change without notice. Fizz does not control MCCs and evaluates rewards based on the MCC received at clearing. See general MCC references: ISO/MCC overview, industry lists.

Related resources

• Program details: Earn Rewards

• Terms: Rewards Policy, 10x Rewards Boost