Skip to main content

Events

Events are delivered via webhook: you register an endpoint, and the system publishes state-change events to it as fuel/wash operations progress.

Authentication​

When you register your webhook endpoint with Logos Payment Solutions, you provide an auth token. That token is sent as a bearer token on every event delivered to your endpoint, so you can verify the request actually came from us:

Authorization: Bearer {YOUR_TOKEN}

FuelingPoint events​

{
  "instanceId": "<long>",
  "operationId": "<uuid>",
  "terminalId": "<long>",
  "stateId": "<integer>",
  "stateDescription": "<string>",
  "updatedTime": "<datetime>",
  "pumpId": "<integer>",
  "currentProductId": "<integer>",
  "unitPrice": "<integer>",
  "volume": "<integer>"
}

See Fuel Operations for the possible pump states reflected in stateId.

WashPoint events​

{
  "instanceId": "<long>",
  "operationId": "<uuid>",
  "terminalId": "<long>",
  "stateId": "<integer>",
  "stateDescription": "<string>",
  "updatedTime": "<datetime>",
  "siteId": "<long>",
  "carWashId": "<integer>",
  "washProgramId": "<integer>",
  "connectionToCamera": "<boolean>",
  "queue": "<integer>",
  "carAtStop": "<boolean>",
  "licensePlate": "<string>"
}

The exact state changes you'll see for a wash operation depend on which flow type the car wash uses (e.g. license-plate-registration inside vs. outside the wash, with or without a queue); see Wash Operations for the breakdown per flow type.

operationId matches the X-Operation-Id header you sent on the original authorize/terminate request, so you can correlate events back to the request that triggered them.