Submit a fuel POS sale → get Fawtara QR + invoice reference

POST 
/api/v1/pos/fuel-invoice

Submit a real-time fuel point-of-sale transaction (e.g. from an OOMCO pump or an Oracle APEX/ORDS fuel automation system).

GoRoute will:

1. Build the Fawtara QR (TLV) from the receipt figures and render a scannable PNG to print on the consumer receipt.
2. Map the sale to the canonical PINT OM model and validate it.
3. Compute the deterministic invoice UUID.
4. Schedule reporting: TDD to OTA Fawtara within 24h for B2C simplified sales, or real-time Peppol AS4 for B2B fleet sales.

The QR + invoice reference are returned synchronously so the pump can print the receipt on the spot with the Fawtara QR already on it.

Only an organisation whose country is OM may call this endpoint. Any other organisation, or one with no country set, is refused with 422 POS_COUNTRY_NOT_SUPPORTED: nothing is recorded and no QR is returned.

Request

Responses

201

Successful Response

409

The invoice UUID this sale computes to (seller, invoice number, date and totals) is already held by a different document of this organisation: a sale issued by another counter, or as the other of B2B/B2C. The sale was NOT recorded and there is no QR in the body, so do not print a receipt. Resubmitting the same sale will not succeed; issue it under a new invoice number.

422

Validation Error

503

The sale could not be confirmed as recorded (a transient platform fault). There is no QR in the body — do not print a receipt. Resubmit the same sale, with the same invoice number, after Retry-After seconds; never re-key it under a new number. The deterministic invoice UUID makes the resubmission idempotent: the sale is recorded and reported once (if the save did land but its acknowledgement was lost, the resubmission returns the original with 200).

Response Headers

Retry-After

Seconds to wait before resubmitting.