What an Open Loop Fleet Card Program Actually Gives You

An open loop fleet card runs on Visa or Mastercard rails. Drivers can use it at any fuel station or truck stop that accepts the network - which is most of them. For fleet operators, the acceptance story is easy: hand a driver a card, they fuel up anywhere, done.

For the platform issuing the card, the economics are a lot less clean.

Interchange on fuel transactions typically runs 1.5–2.5%, and a meaningful chunk of that flows to the card network and issuer, not the platform. On a fleet doing $500K in annual fuel spend, that's potentially $7,500–12,500 in interchange leaving the program before the platform sees a dollar of revenue share.

The data story is similarly limited. Open loop transactions tell you the merchant category, the amount, and the timestamp. They don't tell you which vehicle was fueled, whether the driver followed the authorized route, which fuel grade was purchased, or whether the transaction aligns with a specific dispatch or load. That operational context lives in your platform - the card network has no visibility into it.

What "Closed Loop" Means for a Fleet Program

Closed loop fleet cards in their traditional form just restrict acceptance - the card only works at a defined network of fuel stations or truck stops. You trade acceptance breadth for better data (the merchant is known and cooperating) and sometimes better economics.

But there's a more interesting version of closed loop that fleet platforms should be thinking about, and it has less to do with where the card works and more to do with who owns the payment relationship.

Consider what a fleet management platform actually knows before any fuel transaction happens: it knows the driver, the vehicle, the authorized route, the expected fuel stops, the fleet operator's spending rules, and the billing relationship between the platform and the carrier. That's a lot of verified context that an open-loop card network doesn't have access to.

A closed loop program built in that context looks like this: the fleet operator signs a buyer agreement with the platform. Drivers are issued spend access (physical card, virtual card, or app-based) that works within a defined network of fuel and maintenance vendors. Every transaction is authorized against the platform's rules - not just "is the card valid" but "is this driver, vehicle, and merchant combination authorized for this spend." At the end of the billing cycle, the fleet operator pays a single consolidated bill covering all fleet spend across all drivers.

The platform isn't just distributing a card - it's operating the settlement layer.

Where the Economics Get Interesting

The open loop card program generates interchange, which is a percentage of spend. That model scales with volume, but the ceiling is capped by what the network is willing to share.

A closed loop billing cycle program generates revenue from a different source: the credit extended to the fleet operator between when fuel purchases happen and when the consolidated bill is due. That's effectively a net terms product. And the economics of a net terms product on fleet spend are meaningfully better than interchange.

A fleet operator doing $50K/month in fuel spend who pays on a Net-30 billing cycle is essentially borrowing $50K over a 15-day average outstanding balance. Price that appropriately, and you're generating more revenue per transaction than interchange - without sending a percentage of every gallon to the card network.

There's also a rebate mechanic that open loop programs struggle to replicate effectively. In a closed loop network, the platform can offer fleet operators rebates tied to in-network behavior: paying on time, fueling at preferred vendors, hitting volume thresholds. Those rebates are funded by the economics of the program. That creates a retention flywheel that an open loop card simply can't match.

The Spend Control Difference

Fleet operators care deeply about spend controls, and this is an area where closed loop programs have a structural advantage.

With open loop controls, you can restrict MCC codes (merchant category codes), set transaction limits, and block certain merchants after the fact. But the card still authorizes at the point of sale based on whether the card is valid and the limit allows it - not based on whether this specific driver in this specific vehicle should be buying fuel at this specific location right now.

A closed loop program can enforce pre-authorization logic: only authorize fuel purchases within X miles of the planned route, only authorize up to Y gallons per stop based on tank capacity, flag maintenance spend above a threshold for approval before authorizing. These controls require the platform to know the operational context.

What It Takes to Build a Closed Loop Fleet Program

Merchant network. A closed loop program needs a defined set of fuel and maintenance vendors that accept the program. Building that network from scratch is hard. Platforms that already have preferred vendor relationships or fuel discount programs have a head start -- those vendors are natural anchor points for a closed loop network.

Credit infrastructure. Offering a billing cycle to fleet operators means extending credit and managing the risk of non-payment. Fuel spend is cyclical, fleet operators can have thin margins, and a few bad weeks of freight volume can stress a company's cash position quickly. The platform needs underwriting capability, credit limits, and collections processes -- or a partner that provides all of that behind the scenes.

Authorization infrastructure. Real-time spend controls require a real-time authorization layer. Every fuel transaction needs to hit a system that knows the driver, vehicle, spend rules, and remaining balance before approving. That's a more complex technical requirement than simply issuing on the Mastercard or Visa network.

Reconciliation integration. The closed loop program only delivers its full value if transaction data flows automatically into the fleet operator's accounting or TMS software. If reconciliation is still manual, you've traded one problem for another.

The Strategic Case for Freight and Logistics Platforms

Fleet card programs have been a commodity product for a long time. Most platforms issuing fleet cards today are operating on someone else's rails.

A closed loop fleet spend program is a different strategic posture. It means the platform owns the billing relationship, controls the spend data, sets the authorization rules, and captures better economics of the credit extended.

For platforms that already have deep operational data on drivers, vehicles, and routes, that's not a small advantage. It's the foundation of a payment product that competitors running on open loop rails simply can't replicate.

The fleet card is where the platform captures a transaction. A closed loop fleet spend network is where the platform becomes the financial operating system for the fleet.

Frequently Asked Questions

What is the difference between an open loop and closed loop fleet card?
An open loop fleet card runs on a major card network (Visa or Mastercard) and is accepted anywhere on that network. A closed loop fleet card restricts acceptance to a defined merchant network and allows the platform to control authorization rules, billing terms, and data capture at a more granular level.

Which is better for freight platforms: open loop or closed loop?
It depends on what the platform wants to own. Open loop offers broad acceptance with limited economics and data. Closed loop offers better revenue potential, spend controls, and operational data. It requires more infrastructure to build and operate.

How does a closed loop fleet billing program generate revenue?
Revenue comes primarily from the net terms extended to fleet operators during the billing cycle - effectively a short-term credit product - rather than interchange fees paid by the card network. Platforms can also layer in transaction fees for off-network purchases and rebate mechanics tied to in-network behavior.

What infrastructure does a freight platform need to run a closed loop fleet program?
The four key components are: a defined merchant/vendor network, credit and capital markets infrastructure, a real-time authorization layer, and reconciliation integration into the fleet operator's accounting or TMS system.

Build a Closed Loop Fleet Program with OatFi

Building a closed loop spend program for your freight or logistics platform? Talk to OatFi about structuring a network-based billing and settlement program.

Talk to OatFi