Stored-Value Cards: Fraud, Refund Abuse, and Dispute Risk for Merchants

A stored-value card (SVC) is a payment instrument that holds a specific monetary balance on the card or in an associated account record, rather than drawing on funds held in a separate bank account. Gift cards, prepaid debit cards, transit cards, and closed-loop loyalty cards are all stored-value instruments, and each carries a different fraud and dispute profile depending on whether it is closed-loop (redeemable only with the issuing merchant) or open-loop (network-branded and usable anywhere Visa or Mastercard is accepted).

This guide keeps the same core question e-commerce merchants come here to answer, how do you stop stored-value fraud, but treats prevention, deflection, evidence, liability, and recovery as one connected decision framework instead of a single add-a-rule checklist. If you need a refresher on what is a chargeback before diving into stored-value liability, start there first. For the tactics behind specific attack methods like counterfeit cards, enumeration, and balance manipulation, see the dedicated gift card fraud guide. This page focuses on how stored-value fraud becomes a dispute, who is liable, and what evidence actually recovers the loss.

What Is a Stored-Value Card?

Every stored-value instrument falls into one of two structures, and the difference determines how a dispute plays out:

• Closed-loop: Redeemable only with the issuing merchant or an affiliated network (most retail gift cards). Disputes on closed-loop cards run through consumer-protection channels, not card-network reason codes, because no card network processed the original load or redemption.
• Open-loop: Issued by a bank and branded Visa, Mastercard, or similar, usable anywhere that network is accepted (general-purpose reloadable and payroll cards). Open-loop disputes run over the same rails, and the same reason codes, as ordinary debit transactions.

That distinction matters for everything that follows. A merchant fighting a closed-loop gift-card fraud claim is dealing with a different escalation path than one fighting an open-loop prepaid card dispute filed through a bank.

Why Merchants Offer Stored-Value Programs

Stored-value programs still make sense for most e-commerce merchants: they bring in cash before redemption, attract new customers through gifting, and produce breakage revenue on balances that go unredeemed. What they do not do is reduce fraud risk. A stored-value balance is bearer value in most redemption flows, whoever holds the number and PIN can spend it, which is exactly why stored-value fraud deserves its own framework rather than a footnote in a general ecommerce fraud prevention plan.

How Stored-Value Fraud Moves From Attack to Dispute

Stored-value fraud rarely starts at your checkout. It starts wherever the fraudster gets the card number, the PIN, or the account credentials, and ends when a customer, a card issuer, or your own finance team spots the loss. Three attack paths account for most of the damage merchants see:

1) Card Testing and Enumeration at Scale

Bots test large batches of card numbers and PINs against your balance-check or checkout endpoint to find stored-value cards or gift codes that still carry funds. Each individual attempt looks trivial. At volume, it is card testing fraud aimed at your stored-value inventory instead of a credit card BIN range, and it is often the reconnaissance step before a larger cash-out.

2) Laundering Stolen Card Funds Through Gift-Card Purchases

Gift cards convert stolen credit card funds into a liquid, largely untraceable asset in a single transaction. A fraudster buys gift cards with a stolen card, then resells the codes on secondary marketplaces or uses them directly, well before the cardholder disputes the original charge. Prepaid access providers carry Bank Secrecy Act obligations for exactly this reason: the U.S. Treasury's 2011 prepaid access rule brought sellers and providers of stored value into anti-money-laundering scope precisely because stored value moves cash-like value with far less friction than a traditional bank transfer.

3) Account Takeover of Prepaid and Reload Accounts

Reloadable prepaid accounts and stored-value wallets are credential-based, which means they inherit the same account takeover risk as any login-protected account. Once a fraudster has the login, they can drain the balance, redirect a reload, or add the compromised card as a funding source for further purchases.

Third-Party Fraud vs. First-Party Misuse on Stored-Value Cards

Not every stored-value loss is a stranger's crime. Separating the two matters because they need opposite defenses:

• Third-party fraud: A criminal with no relationship to the transaction uses stolen card data, a compromised account, or a cracked gift-card number to extract value that was never theirs. Recovery depends on evidence that the true cardholder or accountholder never authorized the activity.
• First-party misuse: The customer who purchased or received the stored-value card disputes the original purchase after redeeming the balance, a refund-loop pattern related to friendly fraud. This shows up as an "I never authorized this gift card purchase" chargeback filed after the card has already been spent, or as return fraud where merchandise is refunded to a stored-value balance instead of the original payment method while the original charge is also disputed.

Detection Signals, Controls, and False-Positive Risk

Rules that catch stored-value fraud can also block legitimate gifting behavior; high balance-check volume around holidays looks identical to enumeration from a raw-traffic standpoint. Weigh each control against its false-positive cost before deploying it:

Post-purchase review, holding the order for verification before the balance is activated rather than blocking it outright, catches most stolen-card gift-card purchases without hurting the checkout experience. Chargeflow Prevent applies this kind of scoring after authorization and before fulfillment, so legitimate gift purchases still go through while flagged ones get held.

Liability: Who Pays When a Stored-Value Transaction Is Disputed

Liability on stored-value disputes depends on the loop:

• Closed-loop gift cards: There is no card-network reason code because no card network processed the redemption. Disputes usually surface as a chargeback on the original card used to buy the gift card, not on the gift card itself, which means you are fighting a standard chargeback fraud claim on that original transaction.
• Open-loop, network-branded prepaid cards: These run through standard Visa or Mastercard dispute rails, using the same reason-code families as any other card-present or card-not-present transaction, and follow the same EMV or 3D Secure liability logic as a regular debit card.

Either way, the merchant's exposure is the same in practice: you lose the value that was loaded or redeemed, plus the chargeback if the original funding card is disputed later. Your payment service provider is usually the first party to flag unusual gift-card purchase velocity, since it sees the funding transaction before you do.

Evidence to Retain Before and After Fulfillment

Build your evidence trail before a dispute lands, not after:

• Card verification results (AVS, CVV match) captured at the time the stored-value card was purchased or loaded.
• Device, IP, and email data tied to the purchase and to each subsequent balance check or redemption.
• Activation and redemption timestamps and locations, showing the gap, or lack of one, between purchase and first use.
• Any post-purchase review decision and the signals that produced it.
• For account-based prepaid or reload products, login history and device changes on the account leading up to the disputed activity.

Proactive chargeback alerts on the funding card catch some of these disputes before they post, giving you a refund window instead of a formal chargeback.

Turning Dispute Outcomes Into a Prevention Loop

A stored-value dispute is a data point, not just a loss. Feed the outcome back into your controls: if losses cluster on a specific SKU, denomination, or delivery method, digital codes are laundered faster than physical cards, since there is no shipping delay to intercept, tighten velocity limits there specifically instead of across your whole gifting program. Chargeflow Insights centralizes chargeback and dispute data across processors so you can see where stored-value losses are concentrated, and Chargeflow Automation handles the resulting chargeback response and evidence submission on the original funding-card disputes so your team is not assembling that evidence by hand.

Foire aux questions

What is the difference between a gift card and a stored-value card?

A gift card is one type of stored-value card. Stored-value card is the broader category, covering gift cards, prepaid debit cards, transit cards, and closed-loop loyalty cards: any instrument that holds a defined balance directly on the card or account rather than in a linked bank account.

Can a merchant get a chargeback on a gift card sale?

Not directly on a closed-loop gift card itself, since no card network processes that redemption. The chargeback risk sits on the original card used to buy the gift card: if that card was stolen, the cardholder disputes the purchase, and the merchant absorbs the loss on funds that have often already been spent or resold.

Does EMV or 3D Secure protect stored-value card purchases?

Only for the transaction that funds the stored-value card. If a stolen card is used online to buy a gift card and 3D Secure was skipped or not triggered, the merchant carries the liability for that funding transaction under standard card-not-present rules, separate from anything that happens to the gift card afterward.

How do fraudsters launder money through gift cards?

They buy gift cards with stolen card data or fraud proceeds, then resell the codes on secondary marketplaces or use them directly, converting card-linked funds into a liquid, harder-to-trace asset in a single transaction. This is why prepaid access providers carry Bank Secrecy Act reporting obligations under U.S. Treasury rules.

What is the fastest way to reduce stored-value fraud losses?

Rate-limit balance-check and redemption endpoints to stop enumeration, add post-purchase review before activating high-value loads bought with a card, and route account-based prepaid products through device and login monitoring. None of these add meaningful checkout friction for legitimate customers.

Stop stolen-card gift purchases before the balance activates, and let Chargeflow handle the chargebacks that still land on the funding card. Start for free.