For many enterprise card program buyers, "private label card" brings up a specific picture: a card that works only inside one company's environment, on its own private network, outside the Visa or Mastercard system.
That picture is often inaccurate, and the distinction matters when you choose a card program.
In payments, the terms private label, white label, closed-loop, and restricted open-loop often get used as if they mean the same thing. Some of them describe whose brand appears on the card and who owns the customer experience. Others describe where the card can actually be used. Both distinctions matter, for different reasons.
A private label prepaid card might be a true closed-loop card that works with only one merchant. It might be a white-labelled Visa or Mastercard prepaid card that carries a store's branding but runs on major network rails. Or it might sit somewhere in between: an open-loop prepaid card built on Visa or Mastercard infrastructure but restricted to a defined list of merchants.
This guide breaks down what each term really means, where the confusion comes from, and how to think about the right structure for your program.
Private label: the original definition
The original private label card wasn't a prepaid card at all. It was a retail credit card, the kind your grandmother carried from Bloomingdale's or Macy's.
A private label credit card was a store-branded credit product designed for use at a specific retailer or retail group. It carried no major network logo, and unrelated merchants didn't accept it. The purpose was simple: keep a customer's spending inside the retailer's own ecosystem while offering store-specific financing, promotions, and loyalty benefits.
That original definition still shapes how people use the term. When someone says "private label," they may mean any of the following:
- The card carries our brand.
- The customer thinks of it as our card.
- It can only be used with us.
- It doesn't run on Visa or Mastercard.
Those ideas overlapped neatly in the old retail credit model. In prepaid, they don't always overlap, and that is where the confusion starts.
A prepaid card can be branded for one company without being limited to that company. A card can also be restricted to one merchant or merchant group without running on an entirely private network. The brand on the card and the acceptance rules behind it are related business decisions, but they are not the same technical decision.
Private label prepaid: the stored-value version
When you apply the classic private label concept to prepaid, you are usually picturing a stored-value card that can only be used at a specific merchant, much like the retail credit model.
This is the model most people recognize from traditional gift cards. A customer buys or receives a card with a fixed value on it, redeemable at a particular retailer, restaurant, campus, mall, or affiliated group. Once the balance is spent, the card may no longer work, depending on the program design.
In payment terms, this is a closed-loop prepaid card. Closed-loop cards are redeemable only with the issuing merchant, unlike open-loop cards, which work across a much larger acceptance network. Restricted open-loop or semi-closed-loop cards sit in the middle and can be used at a defined group of merchants, such as every retailer in a particular shopping centre.
Closed-loop cards can work well for simple, single-property programs. A small retailer, a local restaurant group, or a single-site campus may not need broader network functionality. If the acceptance environment is small and stable, a closed-loop prepaid model is easy to understand and easy for customers to use.
For larger operations, the operational burden grows quickly. In a multi-property mall group, a campus network, or a franchise system, every participating merchant has to be onboarded to the program separately. Every new store, seasonal tenant, or pop-up creates more technical and operational work. Data ends up fragmented across systems, and the cardholder experience can feel dated next to the digital wallet and e-card experiences consumers now expect.
The hybrid reality: open-loop rails with merchant restrictions
Today, what people call a private label prepaid program usually isn't a private network in the classic sense. More often it is a restricted open-loop prepaid program.
In this structure, the card is issued on Visa or Mastercard rails through a sponsor bank and processor. It can carry the client's brand, offer a branded cardholder experience, and support modern capabilities like digital wallets, real-time issuance, reporting, and fraud controls. The program manager (like Berkeley) configures the acceptance rules so the card only works at approved merchants.
In other words, it uses the same core rails as an open-loop card, with a restriction layer added on top.
That restriction layer can be built in different ways depending on the program. It may rely on merchant identifiers, merchant category codes, terminal identifiers, merchant lists, or other processor and network controls. Restricted spend programs typically combine controls such as MCCs, Merchant IDs, Terminal IDs, and SKU-level restrictions to approve or deny spend at the transaction level.
For program operators, here is the critical point: a restricted prepaid program does not require every merchant to join a new private network. If a merchant already accepts Visa or Mastercard, the card can ride those acceptance rails while the program enforces where the card is allowed to work.
That makes for a far more scalable model when you want both control and modern acceptance infrastructure.
Case in point: modernizing a mall gift card program
Berkeley helped a large mall group move from a legacy closed-loop system to a network-branded prepaid program. The new program was designed to function only at merchants within the mall group's nation-wide properties, while running on open-loop Visa and Mastercard infrastructure.
The card wasn't open-loop in the everyday "use it anywhere" sense. The program still restricted where the card could be used. But it also wasn't a legacy closed-loop system that required every merchant to be separately wired into a proprietary gift card network.
The result was a scalable mall card model. Any participating retailer that already accepted Visa or Mastercard accepted the card, with no separate technical onboarding.
The program also supported digital wallet integration, real-time activation, richer transaction data, fraud monitoring, and multi-property scale.
The better question was never "private label or open-loop?" It was "Do you need a card that carries your brand, a card that only works in your ecosystem, or both?"
Whose brand vs. where it works
The easiest way to avoid confusion is to separate two decisions.
The first is about branding and business relationships. Whose brand does the cardholder see? Who owns the customer experience? Is the program presented as the enterprise's own payment product, even when a third-party platform powers it behind the scenes?
The second is about network and acceptance. Where can the card actually be used? Is it limited to one merchant? Can it be used anywhere Visa or Mastercard is accepted? Or does it use network rails but restrict acceptance to a specific merchant list?
Why enterprises choose a restricted model
Enterprises usually choose restricted prepaid when they want the balance between a branded customer experience and more control than a general-purpose open-loop card offers. Specifically, they are looking for:
- Loyalty and ecosystem retention. A restricted prepaid card keeps funds inside a defined commercial environment, which helps drive repeat visits and cross-location spend.
- Better spend data. A general-purpose prepaid card shows that funds were spent. A restricted program can be designed to show more relevant, program-level insight, including which categories or items drive the most activity.
- Fraud and misuse control. Restricted prepaid gives enterprises more control over how funds are used, which matters most when the funds are meant for a specific purpose such as benefit disbursements or relief programs.
- Operational scale. A legacy closed-loop card may require every merchant to be integrated manually into a proprietary environment. A restricted open-loop card uses existing network acceptance while enforcing program rules behind the scenes.
The right model depends on what the program is trying to accomplish. A true closed-loop card may be enough for a small, stable merchant environment. A fully open-loop prepaid card may be better when the goal is maximum cardholder flexibility. A restricted open-loop prepaid card is often the middle ground, offering branding, scalability, and control at once.
The bottom line
A private label prepaid card is not automatically a card running on a private network. The phrase can mean several different things depending on how it is used.
The original private label model referred to a retailer-branded card that worked only with that retailer. In prepaid, that idea maps most closely to closed-loop stored value, such as a gift card or incentive card usable only inside a defined merchant environment.
Many modern enterprise programs work differently. They use open-loop Visa or Mastercard rails, sponsor bank and processor infrastructure, and a branded customer experience, then apply merchant-level or category-level restrictions to control where funds can be spent.
The cleanest way to frame the decision is this: branding determines whose card the customer thinks they are using, and acceptance determines where the card actually works.
Once you separate those two questions, the right model becomes much easier to evaluate.
Berkeley Payment Solutions helps enterprises design prepaid programs that match both sides of that equation: branded experiences that reflect the client's business, and configurable infrastructure that supports the right level of control, scalability, and acceptance.
If you are considering a prepaid program, let's structure the model around your specific use case. Contact us to get started.
