Skip to content
FuelOne
Menu

For OMCs

Your programme, your card numbers, your tenant.

FuelOne runs the platform. You own the card numbers, the brand your customers see, the rules every swipe is decided by, and the records. Modules are switched on as you sell them, and a new tenant goes from creation to its first swipe in seven steps.

The card numbers
Generated from your own IIN. The numbers belong to you.
The brand the cardholder sees
Your name and logo on invoices, statements, receipts, transactional email, and on the cardholder Android app, which is built per OMC.
The tenant
Your OMC runs at its own subdomain, your-name.fuelone.pk, with host-only sessions. Your staff, your customers, and their cardholders sign in there and nowhere else.
The rules
Card types, per-card limits, fuel prices, the overdue grace period, the stock variance threshold, service charges, and loyalty rates are set by your staff. Velocity rules are configured for your tenant by the platform operator to your specification.
The records
Your transactions, invoices, payments with their proof, and ledgers, exportable as CSV and PDF, and reachable by signed webhook as they happen.

What you own

You own the programme.

The platform never holds your money. Your customers pay you directly, and the platform records the payment against the invoice with proof.

Nothing the platform stores about your programme is ours. Every record on this list exports, and every change to it is in the audit log with the actor and the values before and after.

The hosts
Your tenant subdomain, the operator console, and the API that terminals and the cardholder app talk to.
The scheduled work
Invoice generation on the first of the month, the daily overdue run and automatic suspension, the daily ledger check, and the limit resets.
The app build
The per-OMC build of the cardholder Android app, carrying your name and logo.
The operator console
Where we create your tenant, switch your modules, define your velocity rules, approve platform-level requests, enrol terminals, and manage card types. What we read across OMCs about money is read-only by policy.

What we run

We run the platform.

Your staff never deploy anything. Your tenant, the scheduled work behind it, and the cardholder app build are ours to run, and the operator console is where we do it.

  • Billing
  • Ledger
  • Loyalty
  • Campaigns
  • Referrals
  • Discount codes
  • Prepaid cards
  • Supplementary cards
  • Support chat
  • Supply chain
  • Onboarding

What a module means

Modules switch on as you sell them.

The core is on for every OMC: cards, the swipe and its gates, business customers and cardholders, stations and daily stock, roles and audit, webhooks and single sign-on. Eleven modules sit on top. The Platform page describes each in full.

  • Switched on per tenant by the platform operator, with no deploy
  • A module that is off does not appear for your staff, your customers, or your cardholders
  • The prepaid balance gate acts on the card, so a module that is off can never let a card draw fuel it has not paid for

Onboarding

From a new tenant to its first swipe, in seven steps.

  1. We create your tenant: its subdomain, your IIN, your logo, and your name. The subdomain is live the moment it is saved.
  2. You add your stations, your fuel types and prices, and your card types.
  3. You create your staff with their roles and station assignments.
  4. Business customers arrive three ways: your staff add them, they apply through your public sign-up form, or they follow an invite link.
  5. Cards are issued by your staff, or requested by a fleet and approved by you.
  6. Terminals are enrolled by serial number and assigned to a station.
  7. Modules are switched on as you sell them.

With the onboarding module on, your staff get a setup checklist on their dashboard, a command palette that reaches every page and action they may use, and a guided tour.

Request a demo

Why OMCs choose FuelOne

Six things no other fuel card platform in this market says.

  • Your card numbers, on your own IIN.

    Cards are generated from your issuer identification number, so the numbers belong to you.

  • The platform never holds your customers' money.

    Invoices are generated and payments recorded against them with proof. The fleet pays you directly.

  • Every refused swipe is recorded with its reason.

    A decline is stored as a transaction, with the gate that stopped it, and the cardholder is emailed.

  • Ledgers that cannot be edited, only reversed.

    Append-only, with a gapless sequence. A daily check reports drift and never repairs it.

  • Modules switched on per OMC.

    Eleven modules. What you do not sell stays off and never appears for your staff or customers.

  • A separate tenant on its own subdomain.

    your-name.fuelone.pk, with host-only sessions. A login against the wrong tenant fails like a wrong password.