Prepaid takes payment before the fuel leaves the tank: better cash flow, zero credit risk, no collections. Postpaid extends credit against a limit and invoices monthly: it is how you win fleet and corporate contracts, and it makes you an unsecured lender to your own customers. Offer prepaid to small and retail customers, postpaid only to accounts you have underwritten — and enforce the limit at the pump, not in a report.
1. The actual difference
Both are just fuel cards. The difference is entirely about when money moves.
With a prepaid card, the customer pays first. A balance — either an amount of money or a quantity of litres — is loaded onto the card, and each fuelling draws it down. When the balance hits zero the card stops authorising. You are never owed anything.
With a postpaid card, the customer fuels first against an approved credit limit and you invoice them later, typically monthly. Between the fuelling and the payment, you have given away fuel and are holding a promise.
That is the whole distinction, and everything else — who to offer which to, what controls you need, how much it costs you — follows from it.
2. What each does to your cash position
Fuel retail runs on thin margins and heavy working capital. You buy a tanker load, it sits in the ground, and you recover the money litre by litre. Anything that changes the timing of that cycle matters more than it looks like it should.
Prepaid improves the cycle immediately. Money arrives before the fuel leaves, which means you are effectively funded by your customers instead of funding them. For a station under working capital pressure this is the single most useful thing a card programme can do.
Postpaid worsens it, deliberately. If a fleet customer takes 30-day terms and averages 20 days to pay, you are permanently funding roughly three weeks of their fuel consumption. That is a real cost, and it is the price of the contract. The mistake is not extending credit — it is extending it without ever calculating what it costs you.
There is a variant worth knowing about: litre-based prepaid, where the customer buys a quantity of litres rather than an amount of money. In a market with volatile fuel pricing this is attractive to customers because it hedges their exposure — and it commits you to supplying at a price that may have moved. Whether that is a good trade depends on your own supply arrangements, and it is worth thinking through before you offer it.
3. The credit risk nobody prices properly
Here is the pattern we see repeatedly. A station starts offering informal credit to a few local businesses — paper vouchers, a ledger book, a handshake. It works. More customers ask. Two years later nobody can state total outstanding exposure without an afternoon of adding up, credit limits exist only as a vague understanding, and one large account has quietly grown to represent an uncomfortable share of the station’s annual profit.
Three things go wrong, always in the same order:
- Exposure becomes unknowable. If you cannot state total outstanding credit within thirty seconds, you are not managing it. You are hoping.
- Limits are advisory. A limit that is checked when the invoice is raised is not a limit; it is a note about something that already happened.
- Concentration builds silently. Nobody decides to let one customer become 15% of receivables. It accretes, one uneventful fill at a time.
All three are solved the same way: the limit has to be enforced before the nozzle is released. That requires the card platform to be connected to the dispenser authorisation layer. A card system that only records transactions is an accounting convenience; a card system that can refuse to dispense is a credit control.
4. Which customer gets which card
| Customer | Recommended | Why |
|---|---|---|
| Large corporate or government fleet | Postpaid | Their procurement requires consolidated invoicing; they will not use prepaid. Underwrite properly. |
| Small local business, 1–5 vehicles | Prepaid | Credit checking costs more than the account is worth, and small accounts are where bad debt concentrates. |
| Taxi and delivery drivers | Prepaid + loyalty | High frequency, low value per visit, price-sensitive, and no credit relationship to manage. |
| Regular private motorist | Loyalty (optionally prepaid) | You want frequency and identification, not a credit line. |
| Staff and family fuelling | Prepaid or capped postpaid | Set hard caps. Informal staff fuelling is a common and awkward leak. |
| Construction or agricultural customer | Postpaid with product restriction | Seasonal cash flow makes credit necessary; product restriction stops diesel cards buying gasoline. |
| New customer of any size | Prepaid first | Let them earn postpaid terms with a payment history. This one rule prevents most bad debt. |
That last row is the most valuable line in this article. Start every new account on prepaid and graduate it to postpaid on evidence. It costs you nothing, it filters out the customers who were always going to be a problem, and it turns credit terms into something a customer values rather than something they assume.
5. Controls that make fleet cards safe
Fleet card abuse is rarely dramatic. It is a driver topping up a private car, filling a jerrycan, or buying gasoline on a diesel account and selling the difference. A monthly exception report documents all of this beautifully, after the fuel is gone.
Applied at authorisation, these controls prevent it instead:
- Per-transaction volume cap sized slightly above the vehicle’s actual tank capacity. This one control eliminates most jerrycan filling.
- Product restriction per card, so a diesel vehicle cannot draw gasoline at all.
- Permitted days and hours, matched to the customer’s operating pattern. A 3am fill on a card belonging to an office-hours business is a question, not a transaction.
- Daily and weekly ceilings on top of the monthly credit limit, so a compromised card cannot exhaust the whole limit overnight.
- PIN requirement, which converts a lost card from a liability into an inconvenience.
- Odometer prompt, which gives the fleet manager consumption-per-distance data — and gives you an anomaly signal when the reading does not progress sensibly.
- Site restriction where you run a network, limiting a card to the stations on the customer’s routes.
Log the declines as well as the sales. A card that fails authorisation four times in a week is telling you something useful, and it is a signal you only get if the system records attempts that dispensed nothing.
6. Where loyalty fits
Loyalty is a different instrument entirely, and confusing it with the other two causes real problems. Prepaid and postpaid are about settlement. Loyalty is about frequency — and it creates a liability rather than settling one.
Two things are worth being disciplined about. First, calculate reward from actual dispensed volume rather than a keyed figure, or the scheme becomes a way to generate rewards without selling fuel. Second, carry the outstanding reward balance in your ledger as a liability. A loyalty scheme with no visible liability is a debt you have chosen not to look at, and it always becomes visible eventually — usually at the worst moment.
The best use of loyalty is not a discount. It is identification: turning anonymous litres into named customers with a visit pattern you can actually analyse. Time-based multipliers to pull demand into quiet hours are worth more than a flat percentage off.
7. Running both without chaos
Most stations end up offering all three. That only stays manageable if they share one platform, one customer master and one ledger. Run prepaid on a spreadsheet, postpaid in a ledger book and loyalty on paper stamps, and reconciliation becomes a permanent part-time job.
What “one platform” needs to mean in practice:
- One customer record that can hold several cards of different types.
- A single card able to carry more than one function — postpaid settlement plus loyalty accrual is a common and sensible combination.
- Authorisation decided at the pump for every model, on the station server so it survives an internet outage.
- All settlement landing in the same accounting ledger, so card revenue reconciles against dispenser data automatically.
- One place to block a lost card, effective across every site.
Get that architecture right and adding a card model later is a configuration change. Get it wrong and every new model is a new set of books.
Related: Fuel card platform · Dispenser automation · Multi-station management
General commercial guidance, not financial, legal or credit advice. Credit decisions and terms remain yours, subject to the regulations applicable in your market.