32. White-Label Solutions and International Station Development
The growth of charging infrastructure requires an organization that goes beyond placing devices at different points. Finding suitable locations, securing the energy connection, putting the financing together, integrating the devices with software and operating the service in line with local conditions are all parts of the same development program.
eBattery's white-label approach aims to offer reusable technology and operations components for these processes. Partners can use station management, digital identity, data verification, investor reporting and the related transaction infrastructure in a way that fits their own service models.
This approach complements eBattery’s goal of developing its own stations. The platform may operate directly as an operator in suitable markets; in other projects, it may take on defined roles alongside local operators and other authorized service providers.
The core principle of international expansion is to adapt a shared technology infrastructure to the real operating conditions of each country. That software can be reused does not mean that the energy connection, licenses, investment rules or local service responsibilities are the same.
32.1 White-Label Service Model
The white-label service model covers the use of certain eBattery technology and operational components under partners’ brands or in a co-branded service structure.
The scope of the model is not limited to a logo and color change. The partner's devices, users, payment flows, support organization and reporting needs are connected to the shared infrastructure in a controlled way.
The service can be structured at three levels:
Technology infrastructure service, covers providing software components such as station management, data records, APIs, digital passport and analytics.
Managed service model, in addition to the technology, involves eBattery carrying out certain monitoring, reporting, reconciliation or support activities.
Joint station development model, enables the local partner's field and operations capacity to be used together with eBattery’s technology, project development and suitable financing infrastructure.
In every model, responsibilities are set by contract. The brand under which a service is offered does not blur who the legal service provider facing the user is. The station operator, the payment service provider, and the parties to the investment transaction are clearly shown on the appropriate screens and documents.
Being a white-label customer does not automatically grant the authority to publish an RWA project or raise investor funds. These functions are enabled once the project and the relevant parties pass the required acceptance and eligibility processes.
32.2 Offering eBattery Technology to Partners
The technology eBattery offers to its partners is built on a modular structure. This way, a business can use the components it needs without having to replace all of its existing systems at once.
The main components that may be offered are as follows:
| Component | Function provided to the partner |
|---|---|
| Station and device management | Managing device, socket, status and session records |
| Station e-ID and passport | Permanent project identity and lifecycle tracking |
| Map and discovery integration | Delivering suitable station information to the user |
| Data and analytics infrastructure | Monitoring energy, usage and service performance |
| Financial reconciliation tools | Establishing the relationships among session, fee, collection and expense |
| Oracle and report records | Turning suitable data into verifiable reports |
| Investor interfaces | Presentation of project, entitlement, and distribution information |
| Smart wallet connection | Access to authorized Web3 transactions |
| Corporate management panel | Role, authorization, service status and operations tracking |
Each customer’s data and authorization domain is kept separate. A user of one business partner cannot access the customer or investor records of another business partner. Shared software use does not mean shared data ownership or unlimited data sharing.
Integrations use versioned APIs and defined data schemas. The impact of changes on existing devices and corporate systems is checked. It is not mandatory for an update to be applied to all customers at the same time and under the same conditions.
Data continuity is also addressed if a partnership ends or the service provider changes. Within the contractual access and transfer terms, the necessary operational records, project history and document references are preserved. Long-term investment rights do not become invisible because access to a short-term software service agreement is cut off.
32.3 Hardware, Software and Operations Components
A successful station installation depends on hardware, software and field operations working together. A shortfall in one of these layers cannot be fully made up for by strength in the others.
Hardware layer, covers the chargers, connection equipment, meters, protection systems, communication components and the necessary site infrastructure.
Software layermanages device communication, session management, pricing, the payment connection, data storage and reporting.
Operations layer, includes installation, maintenance, customer support, spare parts, site access and fault response.
eBattery sets clear acceptance criteria across these layers. Protocol support in a device’s technical brochure is not treated as proof that the relevant features work in a real integration. Session, metering, remote control, and connection-loss behaviors are verified for each manufacturer model and software version.
Hardware selection is not assessed on the initial purchase price alone. Energy efficiency, ease of maintenance, warranty terms, local service availability and spare part availability affect the total cost of service.
For example, a device with a low purchase price that stays out of service for a long time when it fails may create a higher total cost for the project economics. For this reason, the purchase decision is considered together with the service the equipment will provide over its operating life.
In a partnership model, which party is responsible for which component is also determined separately. The device manufacturer's warranty, the local maintenance company's obligation to respond, and eBattery's remote monitoring duty are not treated as the same responsibility.
32.4 Combining RWA Financing with Installation Programs
RWA financing helps create funding for eligible station projects. The installation program ensures that this funding is turned into physical service capacity.
eBattery links these two processes in a shared project plan. The financing target is prepared by taking into account not only the device cost but also site preparation, power connection, installation, commissioning, service start and the necessary budget allocations.
Project development proceeds along this logic:
The regional need and candidate site are identified.
Technical, commercial and legal feasibility is carried out.
The roles and contracts of local parties are defined.
The net budget and the gross financing need are calculated.
An eligible project is taken into the Launchpad process.
After a successful close, funds are used in stages.
Installation and acceptance requirements are completed.
The station is commissioned and periodic reporting begins.
The release of funds is not tied only to reaching a certain date on the calendar. It is linked to evidence such as the contract, delivery, site progress and acceptance records. For procurement that requires advance payment, the relevant contractual protections and delivery obligations are also assessed separately.
Having several stations in the same installation program does not mean that investor funds can be used freely across all projects. Each station's budget and rights structure are preserved. If a shared purchasing discount or shared expense arises, the project-based allocation method is explained.
RWA financing does not replace an energy connection or an official permit. Completing the financing and the station being ready for commissioning are separate stages. These stages are shown to the user and the investor with separate statuses.
32.5 Licensed Activity and Local Partnership Models
eBattery’s international operating model clearly defines operating responsibility according to the market where the project is located.
In its own station projects, eBattery’s targeted role is to be the service provider and operator under the required local authorizations. In white-label projects, eBattery’s role may vary depending on whether the scope is technology provision, a managed service or joint development.
The main operating models are as follows:
| Model | eBattery's role | The role of the local party |
|---|---|---|
| Direct operation | Project and service management through the relevant local structure | Installation, energy, maintenance and other specialist services |
| Providing technology to the local operator | Software, data and reporting infrastructure | Authorized charging service provision and local operation |
| Joint development | Technology, project coordination and suitable financing connection | Site, permit, installation or operating capacity |
| Integration into the existing network | Certain product and data services | Operating and service responsibilities of the existing network |
In Türkiye, a charging network operator and a charging station operator are distinct. According to EPDK’s statements, a station operator may operate under a certificate obtained from a licensed network operator, while the network operator carries the relevant license responsibilities. The brand and role structure of the white-label model should be set up to preserve this distinction.
Charging operation authorization obtained in one country does not automatically authorize the same activity in other countries. Moreover, authorization to offer charging service is not the same as authorization for issuing investment units, investment brokerage, custody or payment services.
For this reason, each project has a separate responsibility mapping for the physical service and for the investment services. In a service offered under a partner’s brand, too, the user and the investor can see which relationship they are entering into with which party.
32.6 Country-Specific Physical Infrastructure Conditions
International station development is not completed by shipping the same device to different countries. Power connection, site layout, metering, accessibility and technical acceptance conditions are assessed locally.
The main areas of physical feasibility are as follows:
Right of use on the site and contract term.
Electrical connection capacity and connection schedule.
Transformer, cabling and protection requirements.
Suitable device and connection types.
Metering and billing requirements.
Fire, electrical and occupational safety conditions.
Vehicle entry–exit and parking layout.
Physical accessibility, including for users with disabilities.
Communication coverage and local continuity.
Climate, temperature, humidity and environmental effects.
Maintenance team and spare parts access.
Nominal device power and power actually available on site are assessed separately. Installing a high-power device does not mean the grid can supply the same power continuously. Where multiple devices share a connection, the power-sharing policy is included in the user experience and revenue scenarios.
For example, a hotel or workplace site where vehicles park for a long time and a roadside point where only short stops are expected may create different capacity needs. Device selection is tied to how the location is actually used.
Installation targets are set taking into account the verified progress of the energy connection. A preliminary meeting, connection approval and actual energization are different milestones.
32.7 Initial Expansion Focused on Türkiye and Europe
eBattery’s mobile app strategy is built on global access. The focus on Türkiye and Europe refers to the initial expansion approach for physical station development and RWA activities; it does not limit the app’s general availability to these regions.
In the station and Web3 development program targeting 2027, the readiness level of sites and local partnership capacity are prioritized. Country selection is not made on market size alone. Energy connection, service cost, the feasibility of the investment structure and the sustainability of the operation are evaluated together.
In the Türkiye leg, network build-out obligations are tied to the financing and procurement plan. EPDK’s current statement specifies that, within six months of the start of the license, at least 50 charging units must be operated in at least five different districts, and that this structure must be maintained throughout the license term. Planning is done using the relevant definitions, without confusing units with sockets or provinces with districts.
eBattery's RWA and white-label tools support managing suitable sites, procurement processes, financing and the commissioning schedule together. However, the sale of investment units or the ordering of devices is not deemed to replace the actual operation condition required by the regulations.
On the European side, common rules within the European Union are considered together with country- and site-specific requirements. European countries outside the European Union are also assessed under their own rules.
The EU's AFIR regulation introduces requirements on user-friendly payment and price transparency in publicly accessible charging infrastructure. For new points within scope, ad hoc access and payment design is assessed according to conditions such as the device's power and installation date. In particular, for new points of 50 kW and above, a payment setup with cards or contactless payment that can read cards should be included in the hardware and site design from the start.
This approach assesses physical expansion not only by the number of stations but by the capacity put into operation in the right place and with the right service model.
32.8 Adapting to New Countries
Entering a new country is a broader adaptation process than translating shared software. For each market, eBattery builds a country configuration that brings together technology, operations, finance and data conditions.
This configuration covers the following areas:
User language and local support.
Currency, number and date formats.
Time zone and financial period boundaries.
Tax and financial document format.
Payment and settlement methods.
Station and operator definitions.
Required data-sharing interfaces.
Investor eligibility rules.
Complaint and dispute processes.
Data retention and access policies.
Local maintenance and emergency response organization.
Adaptation separates the common core from country-specific rules. For example, the station e-ID and the report versioning logic may remain common; the invoice format, investment access or payment method may vary by country.
This distinction reduces the need to develop an entirely different product for each new country, while preventing local rules from being lost within a single generic flow.
Country launches follow defined acceptance conditions. Not all services are activated at the same time before local payment works successfully, the support organization is ready, or device acceptance is complete. Showing stations on the map does not automatically mean that charging start and investment offering functions are also open.
32.9 Local Payment, Tax and Data Requirements
A significant part of international operations depends on setting up the local payment and data arrangements correctly. Even if the same interface is presented to the user, the service providers and obligations in the background may differ.
In payment design, the nature of the service is preserved. Charging payment, investment participation and fiat-to-digital-asset conversion are separate flows. A method available in one market is not automatically enabled for the same service in another market.
In publicly accessible charging services within the scope of AFIR, ad hoc access must be available without the user having to establish a prior ongoing membership relationship. For this reason, at suitable sites the payment experience is not built on a requirement to register with the eBattery app or open a Web3 wallet.
For tax and invoicing, the party providing the service, the party collecting payment and the party issuing the document are clearly identified. The white-label brand does not blur these responsibilities. Shared platform revenue and local station revenue are tracked with separate accounting and reconciliation references.
On the data side as well, the roles of eBattery and the business partner are determined for each data processing activity. User account management, payment, charging sessions and investor verification do not necessarily have the same data responsibility relationship.
The following topics are addressed in the app design:
The purpose for which the data is collected.
Which parties have access.
How long it is retained.
Which countries and service providers it is processed in.
How user requests are handled.
How it is managed when the contract ends.
Which information is linked to publicly available onchain records.
Raw user routes, identity documents and sensitive financial information are not made available to white-label customers as general usage data. Appropriate anonymization and aggregation are applied in regional demand analyses.
32.10 Installation and Commissioning Management
Installation management relies on verifying the project plan at the physical site. The device having been delivered does not mean the station is ready for commercial service.
eBattery’s commissioning process is carried out through successive acceptance stages:
| Stage | Basic verification |
|---|---|
| Site preparation | Right of use, placement and installation conditions |
| Energy infrastructure | Connection, protection and the required electrical acceptance |
| Hardware delivery | Model, serial number, scope and physical condition |
| Assembly | Installation and safety checks appropriate to the project |
| Communication | Device identity, secure connection and data flow |
| Software integration | Session, tariff, metering and remote management |
| Payment test | Authorization, pricing, collection and refund link |
| Operational readiness | Support, maintenance, field access and incident response responsibilities |
| Commercial acceptance | Required documents and conditions for going into service |
| Start of operations | Verified commissioning record |
Acceptance tests cover outage scenarios as well as normal use. Situations such as preserving records when communication is lost, a device restarting, a failed payment and an interrupted session are assessed.
Device serial numbers, meters and outlets are matched with the station e-ID. Equipment that is replaced later is tracked in the same lifecycle record.
Installation deficiencies are classified by their impact. The station is not opened for commercial use until deficiencies related to safety or mandatory service conditions are resolved. For other deficiencies, the responsible party, a completion plan and an acceptance condition are recorded.
Test transactions are separated from commercial activity. In investor reporting, trial charges are not presented as revenue or real customer demand.
After commissioning, the initial period is monitored closely. The first field data is compared with the feasibility assumptions and technical acceptance results; required operational corrections are recorded.
32.11 Service Quality and Performance Monitoring
The success of the white-label model is measured by the continuity and accuracy of the service, not only by the number of installations. The experience offered under the partner’s brand is also monitored against shared quality principles.
Performance tracking is carried out at three levels:
User experiencecovers the driver being able to find a suitable point, start the session, understand the service fee and get support when needed.
Technical operations, covers device availability, measurement quality, communications and fault response.
Financial and investor servicecovers income–expense reconciliation, report timing, data accuracy, and distribution processes.
The key indicators are:
Success rate of valid charge start attempts.
Technical availability per outlet.
Unexpected session interruptions.
Data freshness and coverage rate.
Payment and invoicing consistency.
Support response and resolution times.
Field response and return-to-service times.
Repeat failure rate.
Financial close and reporting timing.
Verified user complaints.
Service level targets are defined together with the measurement method and the responsible party. A provider’s system being accessible does not mean the physical charging service is running without problems. Similarly, a hardware failure and a payment integration problem are tied to different responsibilities.
Breaches and deviations are not used merely to produce an end-of-period score. They are tied to root cause analysis, corrective action and a re-check process. Service credits or other compensation mechanisms defined in the contract also apply under their own conditions; these do not constitute a fixed-return guarantee to the investor.
eBattery’s international station development approach is based on combining shared technology with local service capacity. The white-label structure makes this combination reusable while preserving each station’s physical, legal, and economic reality in its own records.
