SNAP food card entry: NO CVV on card

Hello Lisa J,

Thanks for reaching out.

Edge's saved-payments wallet is built for standard debit / credit cards (Visa / Mastercard / Amex / Discover) and validates against the issuer using CVV and a billing address. SNAP / EBT cards run on a different network and typically have neither, so they don't fit Edge's flow.

I'd suggest not entering a guessed CVV like "123". It won't actually save the card and there's a small chance of it being flagged as suspicious by the EBT processor.

For the use case they actually need, the supported paths live outside the browser wallet:

• Balance, transactions, PIN, freeze/unfreeze: their state's official EBT app — most states use ebtEDGE (FIS) or ConnectEBT (Conduent). Easiest is to search " EBT app" or check the back of the card for the issuer's site.
• Online SNAP purchases: the card gets added inside a USDA-authorized SNAP online retailer's account (e.g., Amazon, Walmart) directly, not in Edge's wallet.

So nothing's broken — Edge just isn't the right tool for this card type, but the official EBT apps cover what they'd realistically need on phone or PC.

Please note that our forum is a public platform, and we will modify your question to hide your personal information in the description. Kindly ensure that you hide any personal or organizational information the next time you post an error or other details to protect personal data. 

SNAP/EBT cards typically don’t have a CVV or standard billing address, and Microsoft Edge’s saved payment system is designed for traditional debit/credit cards that require both CVV and billing details. Because of this, SNAP cards aren’t a good fit for Edge’s “save and fill payment info” feature and may not save or autofill reliably.

Key points from how Edge handles cards:

1. Edge validates cards through the issuer
   • When saving a card to a Microsoft account, bank issuers validate cardholder name, card number, expiration date, CVV, and billing address (the exact data varies by market).
   • CVV is used only for authorization and is not stored, but it is part of the validation flow for supported cards.
   • If required data like CVV or billing address is missing or nonstandard (as with many SNAP/EBT cards), validation can fail or behave inconsistently.
2. Edge is intended for standard debit/credit cards
   • The feature is described as saving “debit and credit cards” for shopping and checkout.
   • SNAP/EBT cards are government benefit cards with different rules and often no CVV, so they fall outside the typical pattern Edge is built around.
3. Why “123” triggers a billing address prompt
   • Entering a CVV value (even a placeholder like “123”) makes Edge treat the card as a normal payment card and then request the remaining required fields (such as billing address) to complete validation.
   • Because SNAP cards generally don’t have a conventional billing address, there is no correct way to complete that flow.
4. Practical implication
   • There is no supported way in Edge to store a SNAP/EBT card as a fully validated, autofillable payment method in the same way as a Visa/Mastercard.
   • The safest and most reliable approach is to enter SNAP card details manually whenever needed, rather than trying to force it into Edge’s saved payment system with made-up CVV or address data.

If a site supports SNAP/EBT directly for online purchases, it will usually have its own entry flow tailored for those cards. Using that site-specific flow and entering the card details manually is the recommended path rather than relying on Edge’s card autofill.

References:

• Saving credit or debit card info in Microsoft Edge