7. Charging and Unified Payment - Post-Launch, Integration-Dependent
For an electric vehicle user, the charging experience begins with finding a suitable station and is complete only after the vehicle has received energy and the user has seen the amount paid. Every step of this process is connected: choosing the right charging point, understanding the tariff, using the payment method, starting the session, following progress and accessing records at the end of the transaction.
eBattery’s unified charging and payment approach brings these steps together in one shared app experience. A station the user discovers on the map or that AI adds to their trip becomes, in supported integrations, a direct starting point for a charging session. This creates continuity between the trip plan, the physical service and the payment record.
The charging and unified payment module will be rolled out in stages after launch, with operator and payment service integrations. The stations where transactions can be made and the supported functions are clearly shown in the app. Each operator’s technical capacity, service terms and the requirements of the market it operates in are reflected in the relevant usage flow.
In this model, while the user is offered a shared experience, the station’s operator, the tariff applied, the status of the collection and the service document remain visible. The value of the unified experience is that it makes the details of different services understandable and manageable.
7.1 Charging Session Flow
7.1.1 From station discovery to an actionable charging point
A charging session begins when the user reaches a station through the map, favorites, a route plan or an AI recommendation. The detail screen of a supported station carries the information reviewed during discovery into the transaction flow.
After seeing the station's location and operator, the user selects the charge point suited to their vehicle. Since the same location may have more than one unit with different power levels, sockets and usage situations, the selection must clearly define the physical point to be used.
Depending on the method the station supports, this pairing can be done through unit selection in the app, an identifier on the device, or a QR code. Before the transaction, the unit and socket information shown on screen is used to make sure it matches the device the user is connected to.
At this stage, the user is shown the following information:
Station and operator name.
The charging unit or connection point to be used.
Socket type and compatibility with the vehicle.
The charging power offered at the relevant point.
Current usage status, where available.
The tariff and payment options that will apply.
Connection steps required to start the session.
The order of connecting the cable and authorizing through the app may vary depending on how the device works. eBattery shows the user, step by step, the sequence of actions supported by the relevant station.
7.1.2 Showing the price and service terms before the transaction
The user should be able to see the pricing that will apply to them before starting a charge. The price information shown during station discovery is re-evaluated at the transaction stage for the relevant socket, service and payment channel.
The tariff structure may include different components depending on the country and service model. In addition to the per-energy fee, there may be time-based, session-based, or post-use fees that apply in the relevant market and service. The conditions under which these components apply are clearly shown.
| Tariff information | The clarity it gives the user |
|---|---|
| Energy unit price | Shows the rate that will apply to the energy received |
| Currency | Specifies the currency in which the transaction is priced |
| Tax information | Explains the tax scope of the displayed price |
| Additional fees, if any | Shows the session, duration or other applicable items |
| Time-dependent conditions | Explains prices that change at certain hours or stages of use |
| Discounts and campaigns | Shows the scope of the benefits that can be applied to the user |
| Pre-authorization information | Explains, where applicable, the amount that will be temporarily held on the card |
The tariff offered through eBattery is based on the terms the user will pay in this transaction. An operator's membership or campaign price in another sales channel is not shown as if applied to the user's transaction unless the same conditions are met.
If the user is proceeding toward a charging target, an estimated total amount can also be calculated. This estimate is based on the planned amount of energy and the known fee components. The amount that results at the end of the transaction is determined from the actual usage records.
If the tariff varies by time slot, this structure is explained at the start. This way, the user can understand how charging extending into different time ranges may affect the cost.
7.1.3 Selecting the payment method and the initiation request
The user selects the supported payment method for the relevant transaction, reviews the conditions shown and starts charging.
At this stage, the verification or pre-authorization step required by the payment service provider may be applied. After payment preparation is complete, the charging start request is sent to the operator’s system.
Receiving the start request and the device starting the session are different stages. Even if the operator system has accepted the request, it may take time for the device to verify the connection and move to the charging process. OCPI's command model also treats the initial system response and the later result from the charge point separately.
eBattery's user flow preserves this distinction. A "Start request sent" state is not shown as "Charging started" until the necessary confirmation arrives.
While waiting, the user can see which stage they are at. If the connection needs to be completed, the relevant guidance is shown; when the transaction concludes, the session screen opens.
7.1.4 Presenting session statuses clearly
The status of the charging session is shown in language that does not require the user to interpret technical messages.
| Session stage | What the user sees |
|---|---|
| Preparing | Checking the charging point, payment method and connection conditions |
| Waiting to start | Request sent; awaiting device or operator verification |
| Session active | Charging session opened; current energy transfer status is being monitored |
| Energy transfer pending | The session is ongoing but no energy is being transferred at the moment |
| Waiting to stop | Stop request sent; waiting for the process to complete |
| Charging complete | Session end confirmed |
| Transaction is being evaluated | Verification of missing or delayed records is in progress |
While a session is active, the instantaneous power may temporarily drop to zero. Waiting states caused by the vehicle or the station are explained to the user in as much data detail as possible. A power value of zero on its own is not used to mean that the session has definitely ended.
Charging and payment statuses are also tracked separately. While the user sees “Charging complete,” the calculation of the final fee may continue for a short time. In this case, the status of the service and the status of the financial transaction are shown under their own headings.
7.1.5 Tracking a charge in progress
The session screen forms the central area where the user can see the progress of the transaction.
Within the scope the integration provides, the following information is offered:
Start time and elapsed time.
The amount of energy measured in the session.
Instantaneous charging power, if shared.
Current or estimated transaction amount.
The unit and socket used.
Current status of the session.
Time of the last data update.
The process of ending the charge.
Battery percentage is shown when it is reliably transmitted by the station or the vehicle connection. An exact battery percentage is not derived solely from the amount of energy delivered.
Similarly, the remaining charging time is presented as an estimate when suitable data and calculation support are available. Because the vehicle's charging behavior and power level may change during the session, the estimate may be updated.
On a trip started with the AI route plan, the suggested charging destination can be added to the session context. However, in the app, showing a destination and being able to automatically stop the device at that destination are separate capabilities. Automatic stop is enabled only when the relevant station and integration support this function.
7.1.6 Ending the session and transaction summary
When a user sends a stop request through the app, eBattery tracks the operator's termination result. The period between the moment the screen is tapped and the physical session closing remains visible.
When charging is complete, the user is shown a summary of the service provided. The amount of energy, session duration, fee components and payment status are matched against the relevant records.
For some services, the end of charging and the end of the connection or parking use may not happen at the same time. If post-use fees apply in the relevant market, the conditions under which they continue are explained at the start and at the end of the session.
In the event of a connection outage or a delayed operator response, the system shows the last known information and re-verifies the status. A transaction with an uncertain outcome is not considered completed or canceled merely because no response was received.
From the user’s perspective, the aim is to be able to see the answers to three questions at every stage of the session: Is charging in progress, what is the payment status, and, if necessary, what action should be taken?
7.2 Wallet and In-App Payment
7.2.1 The wallet’s function within the product
The eBattery wallet is the application layer that lets users manage their charging payments and related usage rights from a shared space.
This area brings together supported payment methods, transaction history, available Charge Credit and related payment activity. When starting a session, the user can see which method they will pay with and, if any, which benefit will be applied.
The wallet experience is designed to preserve the meaning of different types of value. Card payment, prepaid monetary balance and the usage right from the loyalty program have different functions. Their appearing on the same screen does not mean they can be used under the same conditions.
In markets where prepaid balance is offered, this function is put into operation with a suitable payment services structure covering the acceptance of money, the holding of funds, and use and refund processes. The user is shown in which services and under which conditions the balance can be used.
7.2.2 Working with authorized payment service providers
The payment infrastructure is set up with authorized service providers in the market of operation. Card acceptance, verification, collection and, where necessary, e-money functions are matched to the scope of authorization of the relevant institution.
In Türkiye, the activities of payment institutions and electronic money institutions fall within the regulatory and supervisory remit of the Central Bank of the Republic of Türkiye (TCMB); the institutions concerned have operating-license requirements. For this reason, eBattery’s payment experience is developed with a service provider and contract structure appropriate to the legal nature of the function offered.
In this approach, eBattery manages the app experience and the link between the charging transaction and payment. Activities such as accepting, holding or transferring funds are carried out under the relevant authorization and service model.
Which institution the user pays through during the transaction and how responsibilities for the service are divided are explained in an accessible way.
7.2.3 Card payment and protection of payment information
In the card payment flow, the payment provider's secure components and the tokenization method it supports are used as the basis. Tokenization helps manage card details through a reference that allows them to be used in repeat transactions, and reduces the card data the app holds in its own systems. The PCI Security Standards Council addresses tokenization solutions for this purpose.
The user can select their supported card as a saved payment method. Enough masked information to recognize the card is shown within the app; sensitive payment data is not carried into the AI chat, notifications or general transaction logs.
Not storing card security codes after transaction authorization is one of the core rules of PCI DSS. eBattery's payment design respects this distinction; it is not implemented in the form of a card being saved and its security code being kept in the app.
Additional verifications required by the payment provider or the bank are applied during the relevant transaction. The user can see the scope and amount of the transaction they approve.
7.2.4 Separating pre-authorization from final collection
In charging service, total usage is often not final before the session starts. For this reason, under the supported payment model, a pre-authorization hold may be placed on the card.
A pre-authorization is a temporary hold of a certain amount for payment. The final service fee is determined from the records of the completed session. In the transaction history shown to the user, these two stages appear with their separate meanings.
For example, in a purely illustrative scenario, suppose a pre-authorization hold of 500 TL is placed on the card before the session and the actual charging fee is 360 TL. In the supported payment flow, 360 TL is converted into the final charge; releasing the remaining hold amount is handled through the relevant provider and bank processes.
The app does not add the pre-authorization to the total as a second charging expense. The user can see both the service fee and the status of the pre-authorization.
If the session never started or the transaction was canceled, the payment record is compared with the actual service status. Releasing a pre-authorization and refunding a collected amount are tracked as different transactions. The time it takes to appear in the bank account also depends on the terms of those processes.
7.2.5 Linking Charge Credit to the payment experience
CC — Charge Credit, is a usage right that links eBattery's loyalty structure with charging services. At supported stations and campaigns, it may contribute to charging cost, under the conditions shown.
Before paying, users can see whether their existing Charge Credit can be used for the transaction in question and what it will provide. Eligible stations, usage limits, the expiry date if any, and other terms are explained at this stage.
Charge Credit’s place in the payment experience is defined by the following principles:
Use is limited to the scope of the relevant service and campaign.
The consideration that will apply to the transaction is shown before payment.
Used and remaining Charge Credit are tracked separately.
Charge Credit cannot be converted to cash or crypto assets.
There is no two-way conversion between EP and Charge Credit.
EP cannot be purchased and retains its function in the in-game progression structure.
For example, consider a session in which 30 kWh of energy is priced at 12 TL/kWh including taxes, with no other fees, purely to illustrate the calculation logic. The service fee comes to 360 TL. Assuming the user’s eligible Charge Credit provides a 60 TL benefit on this transaction, the amount charged to the card is shown as 300 TL.
| Transaction item | Illustrative example |
|---|---|
| Charging service fee | 360 TL |
| Applicable Charge Credit benefit | −60 TL |
| Amount to be charged to the card | 300 TL |
The prices and benefit amounts in this example are for illustration. The Charge Credit amount and the usage value in a transaction are determined by the displayed rules of the relevant program.
This way, the user can see separately both the cost of the service received and the benefit gained from the loyalty program.
7.2.6 Multi-market and multi-currency approach
eBattery's global product approach requires the payment experience to work with the currencies and service conditions of different countries.
The transaction is recorded in the currency of the relevant service. If the user is also shown an informational equivalent in another currency, the nature of the exchange rate used and the fact that this value is an estimate are explained. The exchange rate or additional fee applied by the card issuer may differ from the informational equivalent shown by eBattery.
Past transactions in different currencies are also preserved with their own amounts. When reporting in a common currency, the conversion method is stated clearly.
The Web2 charging and payment flow is designed to work without requiring users to own crypto-assets. Account and payment functions in later Web3 services are linked to this experience under their own access and eligibility conditions. Charge Credit, game points and Web3 assets are each defined with their own purposes of use.
7.3 Operator Integration Model
7.3.1 Roles behind the service
The unified charging experience relies on different parties working in coordination on the same transaction. The organization operating the station, the app that gives the user access, and the organization processing the payment may take on different roles.
| Role | Core responsibility |
|---|---|
| Charge point operator — CPO | Operating the station, device status and delivering the charging service |
| Mobility service provider — eMSP | The user’s access to partner networks, authorization and shared-use experience |
| Payment service provider | Verification, collection and other payment transactions within its authority |
| eBattery application and integration layer | Discovery, planning, the session experience and presenting the related records to the user |
When working with third-party networks, eBattery provides user access and the app experience within the framework of the relevant operator agreement. At the stage when it takes on the operator role on its own charging infrastructure, it also carries out its operational responsibilities with the necessary licenses and authorizations.
Defining these roles clearly ensures that, in addition to the technical connection, service quality, pricing, billing and support processes are set up correctly.
7.3.2 Direct connections and roaming networks
Access to operators can be established through direct integrations or charging roaming networks.
In a direct connection, a technical and commercial relationship is established between eBattery and the relevant operator. In the roaming model, on the other hand, access and data sharing across multiple networks can be provided through a shared structure.
OCPI — Open Charge Point Interface is an open protocol developed for this communication between charging operators and mobility service providers. The EVRoaming Foundation states that OCPI supports both direct connections and operation through roaming hubs.
eBattery's integration approach is based on connecting in a way that fits the standard the operator uses, the modules it supports and the market it serves. Standard protocols are prioritized, while operator-specific interfaces are adapted to the common data structure when needed.
The technical connection is completed together with commercial access terms. An operator being able to share data and being able to start charging and collect payment on a user's behalf may require different levels of authorization.
7.3.3 Station data, session management and financial records
Operator integration extends from stations appearing on the map to the financial records of the completed service.
The main connection areas are:
Retrieving station, unit and connector information.
Sharing current usage status, where supported.
Communicating the tariffs that will apply to the user.
Charge authorization and remote start-stop.
Usage data is updated during the session.
Obtaining the service record that results at the end of the session.
Matching correction and reconciliation information.
OCPI enables data exchange in areas such as location, tariff, session, remote command and charging detail records. For each operator connection, the usable scope is determined by the supported modules and the mutual integration.
The CDR (Charge Detail Record), used for the details of a completed charge, helps link energy, duration and charging data. This record is an important input for the app's transaction summary and for settlement between parties. The financial document presented to the user is handled separately within the relevant service and invoicing framework.
7.3.4 OCPP’s place in the infrastructure
OCPP — Open Charge Point Protocol is used for communication between physical charging stations and charging management systems. The Open Charge Alliance defines the core scope of the protocol through this device–management system relationship.
This distinction is important for understanding eBattery’s technical architecture:
At the device and operations layer includes the station's communication with its management system.
At the cross-network service layer include user access, tariffs and sharing of session information.
At the payment layer financial transactions are carried out through the relevant payment infrastructure.
At third-party stations, eBattery mostly works with the operator's service interface. In its own operating infrastructure, connecting devices to the management system creates a more direct area of responsibility.
This layered structure keeps the separate requirements of device communication and user payment while allowing an end-to-end service experience to be built.
7.3.5 Reflecting the integration scope to the user
The features available at a station are clearly shown in the app. Discovery, live status, charge start and payment functions do not necessarily all apply to the same station.
| Integration scope | Function that can be offered to the user |
|---|---|
| Basic station information | Reviewing the location, operator and technical specifications |
| Live status link | Seeing the current status of supported charging points |
| Session link | Supported start, stop and session tracking |
| Payment and financial record link | In-app payment, transaction summary and access to related documents |
These scopes are used consistently on the map and in the station details. When the user selects a station, they know from the start which actions they can complete through eBattery.
When assessing the network’s growth, the number of discoverable stations, points with live data, and points where in-app transactions are possible are tracked with separate indicators. This way, the size of the network and the depth of service can be measured together.
7.3.6 Transaction reliability and reconciliation
Operator and payment systems may respond at different times. The same notification may arrive again, or an update may arrive later than expected.
eBattery's integration design is built on transaction IDs and duplicate checking that prevent more than one charge request or collection from arising from the same transaction. If the user presses the button again because of a connection problem, this is not treated as an independent financial transaction.
The session record, the fee calculation and the payment result are compared regularly. The energy amount and the fee, the discount and the collection, and the refund movement and the original transaction are kept consistent with each other.
Corrections are also made through traceable records. In OCPI’s CDR approach, credit/correction records linked to the original record are used to correct a record that was sent earlier. This approach helps explain the change while preserving the trail of the earlier transaction.
7.4 History and Spending Tracking
7.4.1 Collecting the user's charging history in one place
Charge history lets completed sessions be seen in an orderly way in the user's account. The user can review the transactions made through eBattery along with their date, station and payment status.
The history screen is organized to answer everyday usage questions: Which station was used for charging, how much energy was received, how much was paid, and how can the relevant document be accessed?
The detail view of each session includes the following fields, depending on the data scope:
| Record field | Content |
|---|---|
| Transaction date | Session start and end time |
| Station and operator | Where the service is received and the operator |
| Unit or socket | The physical charging point used |
| Amount of energy | Energy measured in the session record |
| Duration information | Charging and other usage times within the scope communicated |
| Fee breakdown | Energy fee and other applicable items |
| Benefit used | Charge Credit or campaign contribution |
| Payment information | Method, currency and transaction status |
| Documents and references | Accessible payment document, invoice and support reference |
Failed, canceled or under-review transactions are also displayed with their own statuses. These are not automatically included in completed charging spend.
7.4.2 Service fee, user payment and refunds
Spending tracking clearly separates different monetary values.
A session's service fee, the Charge Credit used and the amount charged to the card give different pieces of information. The user can see both the total value of the service received and the amount deducted from their own payment method.
In the earlier illustrative example, the service fee is 360 TL, the Charge Credit benefit is 60 TL and the card collection is 300 TL. In the monthly report, these values are collected under their own headings.
A pre-authorization set aside for the same transaction is not added to spending a second time. Refunded amounts are also linked to the original transaction concerned. This way, the user can tell apart total charges, refunds and net payment.
If a correction is needed in a transaction where a partial payment and a loyalty benefit were used together, the portion that belongs to the payment method and the portion that belongs to the usage entitlement are kept distinct. An unused or re-credited loyalty benefit is not treated as money collected from the card.
7.4.3 Periodic summaries and comparisons
The user can review their charging history by period and operator. Where suitable data exists, a per-vehicle assessment can also be made.
Periodic summaries cover the following indicators:
Number of completed charging sessions.
Total energy taken in recorded sessions.
Total service fee.
Charge Credit used and campaign benefits.
Net payment amount.
Spending breakdown by operator and station.
Distribution of AC and DC sessions.
When cost per energy is shown, the scope of the calculation is stated. Dividing the total service fee by the total energy produces a session cost indicator that also includes any additional fees. This value may not mean the same thing as the station's energy tariff alone.
Similarly, dividing the net payment after discount by the energy shows the cost the user actually bears. Because the two calculations answer different questions, they are presented under appropriate headings.
Transactions made outside eBattery and not transferred to the account are not included in the scope of these totals. The summary shown to the user makes clear which records it includes.
7.4.4 Access to documents and the relationship with invoicing
The charging summary, payment document and invoice are linked to one another from the user's point of view, but they may be separate records.
The app links the documents available for the relevant transaction to the session. The party issuing the invoice is determined by the service model and the requirements of the market it is in. For transactions with document integration, the user can reach the relevant invoice or document from the history screen.
Showing transactions from different operators in the same list makes it easier for the user to keep track of their records. The scope of financial documents, on the other hand, is preserved according to the relevant service relationship.
When the user wants to review an expense, they can move forward without having to search again across station information, the payment record and the document.
7.4.5 Support and transaction review flow
Each session is designed to have a transaction reference that can be linked to a support request.
When a user submits a request about a need such as “Charging did not start”, “I want to check the amount” or “I want to see the refund status”, they can select the relevant session from their history. Linking the station, time, energy and payment records to the request makes it easier to assess the issue.
During the support process, the user is given clear status information. It can be explained that the review is carried out through the operator record, the payment result or document matching.
Initiating the refund and its appearing at the bank are also tracked through their own stages. The aim is for users to see not only the outcome but also the process still in progress.
7.4.6 Spending data creating value under user control
Charging history helps users better understand their EV life over time. Which stations are preferred, the costs incurred with different operators and the charging expenses of specific trips can be assessed from concrete records.
Where appropriate, this information also contributes to eBattery AI's efficiency analysis. However, the difference between the energy purchased during charging and the energy consumed while driving in the same period is preserved. A precise driving consumption result is not derived without knowing the battery levels and the measurement scope.
Because charging records carry location and time information, they are managed with access control. They are not shared automatically through the user’s payment history, community profile or social map visibility. In support and operations processes, access is limited to the scope required for the task at hand.
By reviewing their history, users can make more informed choices on later trips: they can compare the cost of the stations they are used to, see the benefit provided by Charge Credit, and track their vehicle usage budget through completed transactions.
