Unified Forecourt Payments: Define the Interfaces Before Promising One Experience

A unified customer experience can depend on several systems and contracts. Fuel authorisation, retail sales, EV charging sessions and payment settlement do not become one process simply because an operator chooses a single brand of equipment.

Document the responsibility of each component

Gilbarco’s DOMS PSS 5000 documentation describes connectivity between forecourt equipment and the retail environment. It is not a specification for every possible charging, kitchen or loyalty integration. DOMS PSS 5000 product documentation

OCPP addresses charging-station management communication. The implementation, supported functions and interfaces to the retailer’s other systems must still be established. Open Charge Point Protocol

The PCI Security Standards Council publishes different standards for account-data security, payment devices and encryption solutions. A terminal approval, a segmented network and a merchant’s compliance obligations are related but are not interchangeable certifications. PCI security standards overview

Analysis: trace an entire transaction

For each journey, identify which system authorises the service, calculates the price, records the sale, issues the receipt and processes a refund. Record the identifiers that connect those steps. Include partial completion, duplicate requests, offline operation and cancellation in the acceptance plan.

A combined receipt may be desirable, but confirm the merchant arrangements and refund responsibilities before promising it. Consolidating a user interface does not automatically remove acquiring fees or contractual boundaries.

Procurement questions that reveal integration risk

Request a supported interface list for the exact software and firmware versions being bought. Ask who owns a defect spanning suppliers, what logs support investigation and how updates are tested. Agree the conditions under which a release can be rolled back.

Build the financial comparison from actual licences, support, transaction costs, implementation work and staff workload. Include the cost of maintaining existing interfaces during transition. The business benefit should be demonstrated through fewer unresolved transactions and clearer operations, rather than an unsupported forecast that a particular controller will produce a fixed profit uplift.