Fuel card platform for oil marketing companies
FuelOne issues cards from your IIN, decides every swipe against rules you set, and keeps a ledger nobody can edit. Payments are recorded against invoices; the money moves between you and your customers and never sits with us.
What FuelOne does for an OMC
You define card types, postpaid or prepaid, for business or cash holders. A card is issued to a person or to a vehicle, and its number is generated from your issuer identification number.
The terminal sends one request. The platform checks company status, card status, limits, velocity rules, prepaid balance, discount code, and PIN, in that order, and completes, declines, or holds the sale.
On the first of the month an invoice is generated per business customer from its completed transactions, with your NTN, STRN, and logo. The customer pays you directly and records the payment against the invoice with proof attached.
Each station has tanks, dispensers, and nozzles, with prices locked per station and fuel type. Pump managers record dip readings and daily stock from their own portal.
You tell us which modules you sell and the platform operator switches them on for your tenant, with no deploy. What is off never appears for your staff, your customers, or your cardholders.
Why OMCs choose FuelOne
Cards are generated from your issuer identification number, so the numbers belong to you.
Invoices are generated and payments recorded against them with proof. The fleet pays you directly.
A decline is stored as a transaction, with the gate that stopped it, and the cardholder is emailed.
Append-only, with a gapless sequence. A daily check reports drift and never repairs it.
Eleven modules. What you do not sell stays off and never appears for your staff or customers.
your-name.fuelone.pk, with host-only sessions. A login against the wrong tenant fails like a wrong password.
The swipe
A swipe ends in one of three outcomes: complete, decline, or hold for a person to decide. A decline is stored as a transaction with its reason and the cardholder is emailed. Nothing about the decision is discarded.
Company status
The customer that holds the card must be active. A suspended customer stops here, on every card it holds.
Card status and expiry
The card must be active and within its expiry date.
Spending and volume limits
The card's rupee and litre allowance for the period must have room for this sale.
Rate of use
Velocity rules: too many swipes, rupees, or litres in a window, too little time since the last swipe, or too many stations. A rule that trips can flag, hold, or decline.
Prepaid balance
A prepaid card must hold enough balance for the sale. Postpaid cards pass straight through.
Discount code
A code entered with the swipe must be valid for this card, station, and date, with budget left. A bad code declines the sale.
PIN
If the card has a PIN, the sale waits for the holder to enter it: two minutes, three attempts, then the card locks for 24 hours.
A diesel fill on a fleet card with a monthly allowance of 1,900 litres. The card had already drawn 1,862.60 L this month.
Stored as a declined transaction with this reason. The cardholder was emailed.
A petrol fill on a card that had already swiped twice in the past hour. The OMC's rule allows two an hour and is set to hold, not decline.
Waiting for a person to approve it from the web. Most fuel card platforms decline at this point.