> For the complete documentation index, see [llms.txt](https://doc.ecomm.api.tietoevry.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.ecomm.api.tietoevry.com/features/fuel-and-ev-charging-payments.md).

# Fuel & EV Charging Payments

The Tieto E-Commerce Payment Gateway (EGW) supports specialised payment scenarios for fuel stations and Electric Vehicle (EV) charging operators, where the final transaction amount is not known at the time of initial authorisation.

Through dedicated Merchant APIs, EGW enables merchants to authorise payments before dispensing fuel or electricity and complete transactions for the actual consumption amount, while handling the applicable card scheme processing requirements.

### Automated Fuel Dispenser (AFD) Payments

The **Fuel Payments API** enables fuel retailers to authorise a maximum purchase amount before fuel dispensing begins and complete the payment for the actual amount dispensed.

For example, a customer may pre-authorise EUR 70 but purchase only EUR 56.46 worth of fuel. EGW processes the final amount and initiates the release of the unused EUR 13.54.

The solution also supports **partial authorisation**, allowing merchants to adjust the maximum dispensing amount based on the issuer's approval, as well as payment cancellation when no fuel has been dispensed.

AFD transactions are processed in accordance with applicable **Visa** and **Mastercard** requirements, using MCC 5542.

### Electric Vehicle (EV) Charging Payments

The **EV Charging Payments API** supports charging sessions where the final cost depends on energy consumption and charging duration.

Merchants can initiate a payment with an estimated amount and request additional authorisations if the charging cost increases.

For example, an initial authorisation of EUR 30 can be increased by EUR 20 during the charging session. If the final cost is EUR 43.75, EGW captures the actual amount and initiates the release of the remaining EUR 6.25.

Multiple incremental authorisations are supported within a single payment transaction. EV charging transactions use MCC 5552.

### Functionality in EGW

* **Pre-authorisation** — Reserve funds before fuel dispensing or EV charging begins.
* **Partial Authorisation** — Support issuer approvals below the requested amount.
* **Incremental Authorisation** — Increase the authorised amount during EV charging sessions.
* **Final Amount Capture** — Complete payments based on actual consumption.
* **Automatic Authorisation Adjustment** — Initiate the release of unused authorised funds.
* **Cancellation and Reversals** — Handle cancelled or unsuccessful transactions.
* **Transaction Monitoring** — Track payment statuses, incomplete transactions and processing deadlines.
* **Reporting and Reconciliation** — Maintain transaction history and support financial reconciliation.

### Merchant Integration

Both services are available through dedicated REST APIs and integrate with the existing EGW payment infrastructure, including tokenisation, 3D Secure authentication and payment status notifications.

This allows fuel retailers and EV charging operators to implement specialised payment flows without managing card scheme-specific processing logic.

**EGW manages the payment lifecycle**, while fuel dispensing, charging session management and consumption calculation remain within the merchant's systems.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://doc.ecomm.api.tietoevry.com/features/fuel-and-ev-charging-payments.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
