We build operations software. We took on payments only because tight integration demanded it: we needed to see cash in flight in real time, get a chargeback alert the moment one lands, and search every transaction down to the line. No processor would give us that, so we built it in. We run it to cover our costs and liabilities, not as a profit center, and because we are the system of record for many dealers, we buy card processing at a scale no single dealer could.
Most ERPs in this category integrate a third-party gateway and resell it, and each box in the stack adds a markup. Kozy Payments is first-party, so those middleman layers are gone, and because we run payments for many dealers at once, that combined volume earns pricing we pass straight through.
Each box in this chain takes a margin. The ERP markets the gateway under its own name; the gateway resells the processor; the processor settles to the acquirer. Four mouths to feed before interchange.
Kozy Payments is first-party. There is no reseller between the office app and the network. We run it to cover our costs, not as a profit center.
A third-party gateway bolts payments onto the side of the ERP, which leaves reconciliation between the two platforms manual, unreliable, and never fully known. Kozy Payments is first-party, so the integration depth, the rate structure, and the ledger posting all live in one system that reconciles itself.
Kozy Payments is built into the platform and posts every payment, refund, chargeback, and deposit straight through the ledger. We run it to cover our costs and liabilities, not to turn payments into a profit center, so the savings land with you.
KozyOps runs the card-processing layer itself, to cover its costs rather than as a profit center. The point is simple: the payment, the ledger entry, the deposit batch, the refund, and the chargeback all live in the same system.
A third-party gateway moves money. Kozy Payments moves money and tells the books what happened.
A third-party gateway can move money. It cannot reach into your billing engine.
Kozy Payments was built so the processor and the ledger are one system. Every charge creates a ledger entry. AR posts against the same chart of accounts. General-ledger accounting lives at the API layer.
Every dollar is traceable in one system: from the moment a payment is received, through its AR allocation against specific invoice line items, into the deposit batch that goes to the bank. Nothing is siloed off in a separate gateway, so AR and finance can open any payment and see and search every step it took.
That matters when the controller asks who did what.
The dispatcher who takes a card-on-file payment cannot also reconcile the deposit batch, because the API enforces that split. Cards on file belong to the ledger card itself, not a side dashboard.
Partial refunds allocate to specific invoice line items. The ledger card shows which gallon order or service ticket each cent came back from. Chargebacks notify you the moment they post and land on the ledger automatically, with the invoice, delivery ticket, photos, and portal messages linked. The evidence packet is one click.
Kozy Payments is the only way to run payments on KozyOps. We do not support third-party gateways, so moving over is part of onboarding.
The switch does not disrupt open invoices, cards on file, or in-flight autopay schedules. We move customers over without breaking the work AR already has in motion.