01 / Kozy Payments · first-party, built in

Payments Built Into KozyOps

Not a resold gateway stack.

KozyOps built payments directly into the platform because fuel dealers need more than a payment processor. They need visibility. Payments, deposits, refunds, chargebacks, and ledger activity all live in one system, tied to the customer, invoice, delivery, and service record from the moment a transaction occurs.

Talk about switching See how the rails differ
02 / The Mechanism

Fewer Layers Between the Office and the Card Networks.

Most ERPs bolt on a resold gateway stack. Kozy Payments is built into KozyOps, so payment activity, ledger posting, refunds, chargebacks, and deposits stay in one system.

· OTHER ERPs

The Reseller Stack.

A resold gateway stack stands between the dealer and the card networks. The ERP markets the gateway under its own name; the gateway resells the processor; the processor settles to the acquirer. Four layers in the way.

01Dealer's office app
02Third-party gatewayRESOLD LAYER
03ProcessorRESOLD LAYER
04Acquiring bank
05Card networks
HOPS · 5MIDDLEMEN · 2
● KOZY PAYMENTS

The First-Party Path.

Kozy Payments is first-party. There is no resold gateway stack between the office app and the card networks. Fewer layers, a more direct path.

01Dealer's office app
02Kozy PaymentsFIRST-PARTY
03Card networks
HOPS · 3MIDDLEMEN · 0
Diagram is structural, not literal. The card networks always settle the transaction. What the first-party path removes is the resold layers in between.

What’s Wired Together

  • Cash in flight. Every authorized, captured, and settling charge is visible in real time. You always know what is actually collected versus what is still moving.
  • Deep transaction search and reporting. Search and report across every transaction down to the line item, by card, account, ticket, or date, without exporting to another tool.
  • Autopay per service line. Split fuel, service, and service-plan autopay cards. Book each line to its own card.
  • Manage Cards. Show Card ID/Token, Brand, Last 4, Expiration, and linked autopay services. Lock cards, change assignments.
  • Charge Deposit. Charge a service-deposit card. Land account credit for balances, future deliveries, or service work.
  • Immediate charge on delivery request. Toggle flag. Run card when delivery completes. Skip batches and overnight waits.
  • Preauthorized amount. Set a credit-card hold on the Delivery Request before the truck rolls, from dispatch or Customer HUB.
  • Add-card-on-request. Add, verify, and use a card inside the same delivery-request flow. Skip Manage Cards.
  • Card-denial notifications. Alert the user when charges fail. Put denial on the ledger card for AR’s next open.
  • Collections charging. Charge posted Collections invoices with one click. Route no-card accounts to Bank Deposits.
  • Bank Deposits. Create one daily deposit. Categorize Visa/MC/Disc, AMEX, Check/Cash. Drop CSV export into reconciliation.
Diagram of payment sources (subscriptions, one-time payments, refunds) flowing through Kozy Payments into the financial ledger, then into revenue, cash flow, and reconciliation reports that feed the finance dashboard.

Switching From a Third-Party Gateway

Kozy Payments is the supported payment platform for KozyOps. The onboarding process includes a migration that keeps invoices, cards on file, and autopay schedules intact.

Talk to us about switching

Switch From a Third-Party Gateway

Bring last month's processor statement.
We'll show what Kozy Payments would have cost, usually inside 10 minutes of the call.

Switching does not require a contract change. No early-termination fee from KozyOps.

Talk to us about switching Platform pricing