What are closed loop payments?

Closed loop payments are transactions that process entirely within a single proprietary network, where the issuer controls both the payment method and where it can be used. The sender and recipient must both be within the same ecosystem. A payment method issued in a closed loop system cannot be used outside of it.

The Starbucks app is the most cited example. Customers load funds into the Starbucks wallet and can spend those funds only at Starbucks locations. The funds cannot be used at other coffee shops, transferred to a bank account, or spent anywhere outside the Starbucks ecosystem. The issuer, processor, and merchant are effectively the same entity.

How closed loop payments work

In a closed loop system, one organization controls the full payment stack:

• Issuance: The operator issues the payment method, whether a gift card, prepaid card, app wallet, or wristband, and loads or accepts funds from the user
• Processing: The operator processes transactions internally without routing through external card networks or bank rails
• Acceptance: The payment method is accepted only at merchants or locations the operator controls or has contracted

Because there are no external card networks or bank intermediaries, transactions settle instantly within the system and carry no interchange fees. The operator keeps full visibility into every transaction and can attach loyalty points, rewards, or restrictions at the product level.

Examples of closed loop payment systems

Closed loop systems appear across retail, transit, hospitality, and enterprise contexts:

• Store gift cards: A Target or Amazon gift card can only be spent at Target or Amazon. The issuer controls the balance and the acceptance points
• Transit cards: London's Oyster card, New York's MetroCard, and similar systems work only within their respective transit networks
• Branded app wallets: The Starbucks app wallet, Disney MagicBand, and similar proprietary systems restrict spending to the issuing brand's ecosystem
• Campus and event cards: University campus cards, festival wristbands, and stadium accounts that confine spending to a defined physical or organizational perimeter
• Internal corporate systems: Some organizations issue internal payment accounts for employee expense management within contracted supplier networks

Closed loop vs. open loop payments

Each model makes a different set of tradeoffs depending on the use case.

Open loop systems trade the cost and data advantages of closed loop for universal acceptance across any enrolled merchant or institution. See the open loop payments entry for a full breakdown of the open loop model.

Why businesses build closed loop systems

The economics of closed loop are compelling at sufficient scale. Without interchange fees flowing to an issuing bank or scheme fees to a card network, the operator keeps a larger share of each transaction. For a high-volume business like Starbucks, which processes millions of mobile app payments per day, the fee savings are material.

Beyond cost, closed loop systems give operators data advantages that open loop cannot match. Every transaction in the ecosystem is visible to the operator at the item level if the system is designed to capture it. This makes targeted promotions, personalized offers, and loyalty mechanics far easier to build than on open loop rails where the merchant sees only the total transaction amount and a card token.

Closed loop systems also enable product controls that open loop cannot replicate. A corporate expense card restricted to specific merchant category codes, a transit card that cannot be used off the network, or a festival wristband that only activates within the event perimeter all require the control that a closed loop structure provides.

The network effect problem

The main constraint of a closed loop system is adoption. Both the payer and the payee must be part of the same network. For a retailer issuing its own gift cards, this is straightforward: the customer buys the card to spend at that retailer. But for any system where the payer needs to be recruited into the ecosystem proactively, the network is only as useful as its participant count.

This is why most fintechs and payment service providers default to building on open loop rails via payment APIs, which provide immediate access to the existing banking infrastructure rather than requiring a proprietary network to be built from scratch. Some platforms combine both: accepting open loop payment methods at the front end while settling internally through closed loop ledger mechanics before funds are disbursed externally via ACH or wire.