Chapter 14 — Merchant-Affiliate Card Programmes: Gift Cards, Co-Brand Prepaid & Card-Linked Offers

Three Programmes, Three Architectures, One Coffee Chain

Elena, WhiteBottle Coffee's head of growth, walks into the CEO's office with three proposals for the holiday season.

The first is a WhiteBottle Gift Card — a simple plastic card customers can buy at the register and give to friends. The second is a WhiteBottle Rewards Debit Card, co-branded with Visa, that earns 3% back on WhiteBottle purchases and 1% everywhere else. The third is a partnership with a popular banking app that would surface a "5% back at WhiteBottle" offer to its two million users.

Three programmes. Three completely different architectures. Three different risk profiles.

From the customer's perspective, each one looks roughly the same: a card (or a card-shaped thing in an app) with WhiteBottle's logo on it. But behind that logo, the plumbing couldn't be more different.

1. The gift card never touches a card network.
2. The rewards debit card runs on Visa's rails through a sponsor bank that WhiteBottle has never met.
3. The banking-app deal doesn't involve issuing a card at all — it wires a marketing incentive directly into someone else's payment stream.

Each programme involves different regulated entities, different settlement flows, different fraud surfaces, and radically different economics.

In this chapter we pull apart that plumbing.

By the end, you'll understand what separates a closed-loop gift card from an open-loop prepaid card from a card-linked offer — and why that distinction matters for everyone from the merchant to the regulator to the customer holding the card.

The Taxonomy: What Are We Actually Talking About?

Before we dig into the mechanics, let's establish the four programme types you'll encounter in the wild. The classification matters because each type sits in a fundamentally different regulatory and operational bucket.

1. Closed-loop stored value:

   This is the simplest model. Think gift cards.

   The merchant issues a card that only works at its own stores. No card network is involved. The customer loads money, the merchant records a liability, and when the customer buys a latte, the merchant decrements the balance on its own ledger.

   WhiteBottle's gift card is a textbook example.

2. Open-loop prepaid:

   This is what happens when you add a card network to the mix.

   WhiteBottle's Rewards Debit Card carries a Visa logo, which means it works anywhere Visa is accepted — not just at WhiteBottle.

   But WhiteBottle isn't a bank, so it needs a sponsor bank (a licensed issuer that holds the Visa membership and the customer's funds) and an issuer processor (the technology platform that manages card records and authorizes transactions).

   The card looks like WhiteBottle's product, but the regulated infrastructure belongs to someone else.

3. Open-loop co-brand debit or credit:

   The traditional co-branded card you've seen from airlines and hotels.

   A bank issues a Visa or Mastercard product with the merchant's branding and merchant-funded rewards.

   The bank owns the customer relationship and the credit risk; the merchant subsidizes the rewards to drive loyalty.

   We won't spend much time on this type — it's the most mature and well-understood model — but it's important to place it on the spectrum.

4. Card-linked offers (CLOs):

   CLOs take a completely different approach. No new card is issued at all.

   Instead, WhiteBottle partners with a banking app or offers platform that detects when an existing cardholder shops at WhiteBottle and automatically triggers a reward.

   The marketing incentive is wired into the payment stream after the fact. Think of it as affiliate marketing plumbed directly into the card settlement infrastructure.

Here's how these four types compare across the dimensions that matter most:

Notice the pattern: As you move from left to right, the merchant gives up control in exchange for reach.

A gift card only works at WhiteBottle, but WhiteBottle controls the entire experience.

An open-loop prepaid card works everywhere, but now you're dealing with sponsor banks, scheme rules, and chargebacks.

A CLO doesn't even require the merchant to issue anything — but the merchant is now dependent on someone else's platform and transaction data.

Closed-Loop Stored Value: The Gift Card

Let's start with the simplest programme: WhiteBottle's gift card.

When a customer walks up to the register and pays $50 for a WhiteBottle gift card, something interesting happens from an accounting perspective.

WhiteBottle receives $50 in cash right now, but it hasn't earned that revenue yet. The company records a deferred revenue liability — it owes the cardholder $50 worth of coffee.

Revenue is only recognized when the cardholder actually redeems the card.

So how does that work? The answer is, no card network is involved.

There's no acquirer, no issuer (in the four-party sense), and no interchange. WhiteBottle is simultaneously the issuer, the acquirer, and the network.

When the cardholder taps the gift card at a WhiteBottle store, the POS system checks the balance on WhiteBottle's own ledger, decrements it, and records the sale.

The entire transaction is internal.

Simple. No external parties, no interchange fees, no settlement delays.

Float and Breakage: Why Merchants Love Gift Cards

The economics of closed-loop stored value are remarkably attractive for two reasons.

1. Float:

   The merchant receives cash before delivering any product.

   That $50 sits on WhiteBottle's balance sheet as usable cash from day one, even though the revenue hasn't been recognized yet. For a chain selling millions in gift cards during the holiday season, that's a significant source of working capital — interest-free.

2. Breakage:

   Not every gift card gets fully redeemed. Some get lost in a drawer. Some have a remaining $1.37 balance that nobody bothers to use.

   That unredeemed portion is called breakage, and it eventually becomes revenue.

Under ASC 606 (the US revenue recognition standard), breakage isn't recognized all at once when the card "expires" or is deemed unlikely to be used.

Instead, it's recognized proportionally — as actual redemptions occur, the merchant also recognizes a proportional share of the expected breakage. If WhiteBottle expects 10% breakage on a $50 card, it recognizes a small slice of that $5 every time the cardholder buys a coffee.

The scale of this can be staggering. Starbucks — the canonical example of closed-loop stored value at scale — reported $1.87 billion in unredeemed gift card liabilities on its balance sheet as of fiscal 2024, and recognized $207.6 million in breakage revenue that year.

That's a 13.7% breakage rate, generating hundreds of millions in pure-margin revenue from coffee that was never poured.

Risks and Obligations

Gift cards aren't all upside. Two risks in particular come with the territory:

1. Fraud:

   Gift card scams are among the most common payment fraud vectors, with scammers directing victims to buy gift cards and read the codes over the phone.

   Merchants need activation controls, velocity limits, and anti-fraud monitoring.

2. Escheatment:

   Then there's escheatment.

   In the United States, unclaimed property laws require businesses to remit abandoned property to the state.

   The landscape is fragmented: 37 states exempt gift cards from escheatment (often conditional on having no expiration date or inactivity fees), but 14 jurisdictions require it, with dormancy periods typically ranging from two to five years.

   Escheatment is the hidden cost of breakage — in states that require it, the merchant must remit unredeemed balances to the state rather than booking them as revenue.

Open-Loop Prepaid: The Rewards Debit Card

WhiteBottle's second programme — the Visa-branded Rewards Debit Card — is a fundamentally different animal.

Unlike the gift card, this card works anywhere Visa is accepted, which means it runs on the four-party model we covered in Chapter 5. But WhiteBottle isn't a bank, so how does it issue a Visa card?

The answer is a three-layer stack:

1. Programme manager:

   A programme manager owns the brand, defines rewards, handles marketing and customer acquisition. For example, WhiteBottle or its contracted partner.

2. Issuer processor:

   The technology platform that creates card records, allocates PANs from a BIN range, authorizes transactions against the prepaid balance, and generates scheme-compliant files.

3. Sponsor bank:

   A licensed bank that holds the Visa membership and the BIN.

   The sponsor bank is the regulated entity. It holds the safeguarded customer funds and is responsible for scheme settlement.

   The sponsor bank lets WhiteBottle's programme access the Visa network under the bank's Bank Identification Number — the first six to eight digits of the card number that identify the issuer.

   The card says "WhiteBottle" on the front, but Visa and the regulatory world see the sponsor bank.

As a worked example, consider the Walmart MoneyCard as a real-world parallel:

1. Walmart is the programme manager and distributor.
2. Green Dot Bank is the sponsor bank and issuer.

The card is available in both Visa and Mastercard versions, and customer funds are FDIC-insured because they sit in a demand deposit account at Green Dot Bank. Nine card variants are available across more than 4,100 Walmart stores.

Issuance, Activation, and Loading

Notice the parties involved — this is nothing like the gift card flow. KYC (Know Your Customer) checks are mandatory because this is a regulated financial product. The sponsor bank must verify the customer's identity before funds can be loaded.

Once the card is active, loading works through two paths:

The card-based load path is worth noting: when a customer loads their WhiteBottle prepaid card using their existing bank card, that load transaction flows through the four-party model as a purchase on the existing card. The customer's bank sees a charge; the sponsor bank receives funds; the issuer processor credits the prepaid balance.

Spending, Settlement, and Safeguarding

When the customer uses the WhiteBottle Rewards Debit Card at any merchant — not just WhiteBottle — the transaction flows through the standard four-party model from Chapter 5. The issuer processor authorizes against the prepaid balance. Clearing and settlement happen via Visa's normal processes. The sponsor bank must fund the scheme settlement from the safeguarded customer funds.

This is where the operational complexity lives. The sponsor bank has a legal obligation to safeguard customer funds — to keep them segregated from the bank's own assets and available for return if the programme fails. The specific requirements vary by jurisdiction:

• In the UK, the FCA's PS25/12 (effective May 2026) requires daily reconciliation of safeguarded funds, annual audits by a qualified auditor, and monthly regulatory returns.
• In Singapore, the MAS Payment Services Act requires segregation into a trust account or a bank guarantee, with safeguarding by the end of the next business day after receipt and daily reconciliation.
• Under FATF guidance (the 2013 framework, still the primary reference), prepaid cards require risk-based AML/CFT (Anti-Money Laundering / Combating the Financing of Terrorism) controls — full customer due diligence for reloadable cards, with simplified measures potentially available for low-value, non-reloadable products.

Card-Linked Offers (CLOs): Marketing Through the Payment Stream

WhiteBottle's third programme takes a completely different approach. No new card is issued. No sponsor bank is needed. No KYC is required.

Instead, WhiteBottle partners with a banking app that has two million users. The app surfaces a "5% back at WhiteBottle" offer to eligible cardholders. When a cardholder adds the offer and then pays at WhiteBottle with their existing card, the banking app detects the transaction and automatically triggers a cashback reward.

This is a card-linked offer — affiliate marketing wired directly into the payment settlement infrastructure.

How CLOs Work

The mechanics involve three operational steps:

1. Enrollment: The customer links their existing card to the offers platform and opts into specific offers. This consent step is critical — the platform needs permission to monitor the customer's transaction data for qualifying purchases.
2. Transaction qualification: When the customer pays at WhiteBottle, the offers platform detects the transaction by matching data from the authorization stream (faster but less detailed) or the settlement stream (slower but richer data, including exact amounts and merchant identifiers). The platform checks: Is this cardholder enrolled? Does the transaction match the offer rules — right merchant, right MCC, right spend threshold, right time window?
3. Reward settlement: Here's what makes CLOs architecturally distinctive: the purchase and the reward settle through two separate streams.

The purchase settles normally through the four-party model. Separately, the offers platform matches the transaction, triggers the reward, invoices WhiteBottle for the reward amount (plus a platform fee), and instructs the issuing bank to post a statement credit to the customer's account.

Who Runs CLO Platforms?

CLOs are operated at three levels:

Network-operated platforms like Visa's offers capability and Mastercard's merchant-funded offers platform. Mastercard's platform is notably network-agnostic — it can deliver merchant-funded offers across any payment type and network, not just Mastercard cards. This positions it as an issuer service rather than a network-exclusive feature.

Issuer-operated platforms, the most prominent being Amex Offers. Amex uses an explicit "add then pay" model: card members browse available offers, manually add an offer to a specific card, then make a qualifying purchase. The reward — a statement credit or bonus points — appears within 90 days. Because Amex is both the issuer and the network, it has complete visibility into the transaction and can do precise attribution.

Independent platforms operated by fintechs and data companies that aggregate transaction data from multiple issuers and networks.

Key Operational Concerns

CLOs sound elegant, but the operational details are thorny. Consent and privacy are paramount — using transaction data to trigger marketing requires explicit cardholder opt-in under most privacy frameworks. Merchant identification is harder than it sounds — matching transactions to the right merchant requires accurate MCC codes and merchant IDs, and a single merchant may appear differently across acquirers. Deduplication is essential — you don't want to reward the same transaction twice if it appears in both the auth and settlement feeds. And reconciliation between the transaction feeds and the reward payouts must be airtight, because WhiteBottle is being invoiced for every reward.

Regulation and Compliance: What Changes by Programme Type

One of the most important things to understand about these programmes is that the regulatory burden varies enormously depending on the type. Here's how the key obligations map:

The pattern is clear: the more you look like a bank, the more you're regulated like a bank. A closed-loop gift card sits mostly outside the financial regulatory perimeter (though escheatment and consumer protection laws still apply). An open-loop prepaid card is fully inside it — KYC, safeguarding, scheme compliance, chargebacks, the works. A CLO sidesteps most of it because no new financial product is being issued.

This is exactly why Elena's three proposals carry such different operational implications for WhiteBottle. The gift card is something WhiteBottle can largely manage in-house. The prepaid card requires a regulated partner stack. The CLO is operationally lightweight but depends entirely on the banking app's platform and data.

The Economics: Who Pays, Who Earns

Let's bring it back to WhiteBottle and look at the unit economics of Elena's three programmes:

The economics tell a compelling story. If WhiteBottle sells $100,000 in gift cards this holiday season with a 10% expected breakage rate, that's $10,000 in eventual revenue with zero cost of goods sold — pure margin. The float is free working capital from the day the cards are sold until the last latte is redeemed.

The Rewards Debit Card is the most expensive to launch and operate — KYC onboarding, card production, scheme fees, settlement funding, dispute handling — but it drives spend both at WhiteBottle (3% back) and everywhere else (1% back), keeping the brand in the customer's wallet permanently.

The CLO partnership is the lightest-touch option. WhiteBottle pays only for verified purchases — say, a 5% reward on each qualifying transaction. No card to issue, no KYC to run, no compliance to manage. But WhiteBottle is entirely dependent on the banking app's platform, data quality, and user base.

What Comes Next

We've now covered the full arc of card payments. Part II introduced the four-party model and the cast behind it. In this Part, we traced how a card payment actually executes, how debit and credit diverge on the same rails, how 3D Secure adds authentication, how network tokens and vaults abstract the card number away, and how the dispute and chargeback lifecycle works. And this chapter showed how merchants repurpose card infrastructure as a distribution and retention tool — or deliberately avoid it.

Part IV shifts from one-time payments to ongoing relationships: recurring billing, subscription management, and the dunning mechanics that keep revenue flowing when cards decline.

But before we leave card infrastructure entirely, note that closed-loop stored value will resurface in Chapter 22 (Wallets, Super Apps & Closed-Loop Payments) in Part V — the same stored-value mechanics, but in the context of digital wallets and platform ecosystems.

Sources

• Starbucks Corporation Fiscal 2024 Annual Report (10-K): stored-value card liability, breakage revenue, and ASC 606 revenue recognition disclosures
• Green Dot Corporation / Walmart MoneyCard cardholder agreement and product disclosures
• FATF, Guidance for a Risk-Based Approach to Prepaid Cards, Mobile Payments and Internet-Based Payment Services (2013)
• FATF, Recommendation 16 revisions (June 2025 Plenary)
• FCA Policy Statement PS25/12, Changes to the safeguarding regime for payments and e-money firms (August 2025)
• MAS Payment Services Act 2019, Section 23 (safeguarding requirements) and Notice PSN01 (AML/CFT)
• Alston & Bird, How Changes in State Gift Card Laws May Affect Cos. in 2025 (2025)
• National Conference of State Legislatures, Gift Cards and Gift Certificates Statutes and Legislation
• American Express, Amex Offers Terms & Conditions
• Mastercard Services, Offers for Publishers capability documentation
• ASC 606 / IFRS 15 guidance on breakage recognition (customers' unexercised rights)