A stored value card is a payment instrument that holds monetary value directly on the card or in a linked account record, independent of any credit line or checking account. When a purchase is made, the balance is decremented in real time — whether the card is physical plastic, a virtual card number, or a token inside a mobile wallet. Stored value cards span a huge range of use cases: employee benefits, transit fares, consumer gift cards, government disbursements, and corporate expense programs all run on this foundational architecture.
Understanding stored value cards is essential for any merchant or payment professional designing a card program, evaluating a prepaid product, or building disbursement infrastructure. The economics, regulation, and technical plumbing differ meaningfully from credit and debit card rails.
How Stored Value Card Works
At its core, a stored value card separates value storage from the underlying bank account. The flow from load to redemption involves several distinct steps.
Card Issuance
A program manager or issuing bank creates the card record — physical or virtual — and assigns a unique card number (PAN). For open-loop cards, the PAN is registered on a card network (Visa, Mastercard, UnionPay). For closed-loop cards, the PAN lives only in the merchant's or transit operator's own ledger.
Value Load
Funds are loaded onto the card via cash top-up at a retail location, ACH transfer, bank card payment, or API call from a platform. The issuer credits the card's balance ledger and, for regulated e-money instruments, places equivalent funds in a safeguarded pooled account.
Transaction Authorization
When the cardholder pays, the point-of-sale or online checkout sends an authorization request to the card network (open-loop) or directly to the merchant's processor (closed-loop). The authorization engine checks the stored balance, reserves the amount, and returns an approval or decline in milliseconds.
Settlement and Balance Decrement
After authorization, the transaction moves through clearing and settlement. The cardholder's stored balance is permanently decremented. For open-loop cards, funds flow from the issuer's settlement account through the network to the acquiring bank. For closed-loop cards, the merchant's own system records the redemption.
Reload or Expiry
Reloadable stored value cards allow the cycle to repeat — the cardholder adds funds again. Single-load cards (most gift cards) are simply discarded when the balance reaches zero. Expiry handling must comply with local regulation (e.g., the US CARD Act's five-year minimum for gift cards).
Why Stored Value Card Matters
Stored value cards are not a niche product — they represent a substantial and growing segment of the global payment economy, with structural advantages that make them attractive to issuers, merchants, and consumers alike.
The global prepaid card market was valued at approximately $2.2 trillion in load volume as of 2024, with projections pointing to sustained double-digit growth driven by digital disbursements, financial inclusion programs, and corporate expense management (Nilson Report, 2024). In the US alone, the CFPB estimates that more than 140 million Americans used a general-purpose reloadable (GPR) prepaid card in the past five years, with significant adoption among unbanked and underbanked populations.
From a merchant perspective, the economics are compelling. Stored value programs generate upfront cash flow before any goods or services are delivered. Breakage — the share of card value never redeemed — averages 6–10% for gift cards across retail sectors (CEB/Gartner, 2023), representing direct revenue contribution that can be recognized under ASC 606 once redemption becomes sufficiently unlikely. For high-volume gift card programs, breakage alone can contribute millions in annual revenue.
Regulatory note
In the EU, stored value cards that qualify as e-money require the issuer to hold an Electronic Money Institution (EMI) license and safeguard 100% of outstanding card balances in segregated accounts. This protects cardholders even if the issuer becomes insolvent.
Stored Value Card vs. Prepaid Card
The two terms are frequently conflated, but they have distinct scopes. The table below clarifies the key distinctions for practitioners designing or evaluating card programs.
| Dimension | Stored Value Card (broad) | Prepaid Card (specific) |
|---|---|---|
| Scope | Umbrella term for all balance-based card instruments | A subset of stored value cards |
| Network | Open-loop or closed-loop | Typically open-loop (Visa, MC, Amex) |
| Acceptance | Varies — could be single merchant or global | Anywhere the network is accepted |
| Examples | Gift cards, transit cards, meal vouchers, GPR cards | Netspend, Green Dot, corporate expense cards |
| Regulatory label | E-money (EU), stored value (US state law) | Prepaid account (CFPB Regulation E) |
| Reload capability | May or may not be reloadable | Usually reloadable |
| KYC requirement | Minimal for low-value closed-loop | Full KYC often required for high limits |
The practical takeaway: every prepaid card is a stored value card, but not every stored value card is a prepaid card. When building a program, the distinction determines which regulatory regime applies and which network agreements you need.
Types of Stored Value Card
Stored value cards exist on a spectrum defined by acceptance scope, reload capability, and regulatory classification.
Open-Loop Stored Value Cards carry a Visa, Mastercard, or similar network brand and are accepted wherever that network operates. They are functionally equivalent to prepaid cards and subject to the full weight of network rules and consumer protection regulation. Examples include general-purpose reloadable (GPR) cards and government benefits cards (EBT, Medicaid spending accounts).
Closed-Loop Gift Cards are the most consumer-familiar type — a single-merchant or small-network card that can only be spent with the issuing brand. Starbucks, Amazon, and IKEA all operate major closed-loop programs. Regulation is lighter, but acceptance is narrow.
Semi-Closed-Loop Cards are accepted at a defined group of merchants — a shopping mall network, a fuel station consortium, or an employer benefits program covering selected vendors. They occupy the regulatory middle ground between open and closed.
Transit and Contactless Value Cards (e.g., Oyster in London, Suica in Japan) store fare value on the card chip itself rather than a central server, enabling ultra-fast tap-and-go payments without network round-trips.
Digital and Virtual Stored Value includes digital wallet balances, in-app currencies, and virtual card numbers issued for single-use or recurring online purchases. These are increasingly the dominant form factor as physical card issuance declines.
Corporate and Payroll Disbursement Cards are used by employers and gig platforms to distribute earnings instantly to workers who may not have bank accounts, avoiding ACH delays and check-cashing fees.
Best Practices
For Merchants
Model your breakage economics carefully before launch. Breakage revenue is real, but it comes with ASC 606 / IFRS 15 accounting obligations. Work with your auditors to define the pattern of redemption and the point at which remaining balances can be recognized as revenue. Misjudging this creates restatement risk.
Choose loop type based on your distribution strategy. If you want cards sold at third-party retail (grocery, pharmacy), open-loop gives you reach but comes with network fees and compliance overhead. If all sales happen on your own properties, closed-loop is simpler and cheaper to operate.
Implement real-time balance inquiry at the POS. Cardholders who hit a zero-balance decline in-store have a poor experience and often abandon the transaction entirely. Real-time balance display — via receipt, app, or IVR — reduces friction and chargebacks.
Plan for dormancy and escheatment. Every US state has unclaimed property laws that may require you to remit unredeemed balances to the state after a defined dormancy period (typically 3–5 years). Build this into your program economics from day one.
For Developers
Use idempotency keys on every load API call. Network retries on a load endpoint without idempotency controls can double-credit a cardholder's account. All major card issuing APIs (Marqeta, Stripe Issuing, Adyen Issuing) support idempotency headers — use them.
Handle partial authorization. When a cardholder's stored balance is less than the transaction amount, some merchants support a partial approval flow where the card covers part of the total and the remainder is paid by another tender. Your POS integration must be able to handle split-tender responses.
Subscribe to real-time webhooks for balance events. Load confirmations, transaction authorizations, and reversals should trigger webhooks to your application layer so you can keep your own ledger in sync without polling the issuer's API.
Test edge cases: zero balance, expired card, velocity limits. Stored value card programs often have per-transaction and per-day limits enforced at the issuer level. Simulate these in your staging environment before go-live to prevent production surprises.
Common Mistakes
Ignoring state escheatment law. Merchants often discover mid-program that unredeemed gift card balances must be turned over to state unclaimed property offices. The timeline varies by state — Delaware is as short as two years for gift cards — and non-compliance carries penalties plus interest.
Conflating open-loop and closed-loop compliance requirements. A closed-loop gift card program requires minimal regulatory infrastructure. Adding a Visa logo and enabling ATM withdrawal transforms it into an open-loop prepaid account subject to Regulation E, CFPB oversight, and network operating rules. Many merchants make this transition without realizing the compliance burden it triggers.
Insufficient fraud controls on reload endpoints. Stored value card load APIs are a target for fraud — especially where reloads can be funded by stolen credit cards. Without velocity checks, card-testing detection, and 3DS on load transactions, programs can suffer significant first-party and third-party fraud losses within weeks of launch.
Poor expiry communication. Surprising a customer with an expired card — even if legally permitted — generates chargebacks and brand damage. Send proactive balance and expiry reminders via push notification or email, especially in the 90-day window before expiry.
Underestimating KYC requirements for high-value cards. Open-loop cards above certain load or balance thresholds trigger CIP (Customer Identification Program) obligations under US Bank Secrecy Act rules, or equivalent AML requirements in other jurisdictions. Launching without a KYC flow for high-limit tiers creates regulatory exposure.
Stored Value Card and Tagada
Stored value card programs generate complex, multi-leg payment flows — loads from various funding sources, real-time authorization responses, settlement from multiple acquirers, and reconciliation across closed- and open-loop rails. Tagada's payment orchestration layer is built to handle exactly this kind of complexity.
How Tagada helps stored value programs
Tagada connects to card issuing platforms (Marqeta, Adyen Issuing, Stripe Issuing) alongside traditional acquiring and banking rails through a single API. For stored value programs, this means you can orchestrate load transactions, route authorization fallbacks, and reconcile settlement files across processors — without building custom integrations for each provider. If your program spans multiple geographies or issuing partners, Tagada's routing rules engine handles the complexity so your product team doesn't have to.
Merchants running loyalty-linked stored value programs can use Tagada to correlate card spend data with customer profiles across channels, enabling real-time rewards issuance and balance updates without duplicating integration work across each issuing and acquiring partner.