20. Digital Identity: Station e-ID and Investor e-ID
eBattery’s digital identity approach ensures that physical stations, investors and transaction authorizations are correctly linked to one another. The aim is for it to be clear which project, person or authorized transaction each record in the ecosystem belongs to.
A station's name may change, its device may be renewed, or it may be moved to another location under suitable conditions. An investor may also change their phone, contact details or the wallet they use. During these changes, the project history, entitlement and authorization records must remain consistent.
In eBattery’s Web3 architecture targeted for 2027, digital identity is one of the core structures supporting this continuity. While the station e-ID links project and physical infrastructure records, the investor e-ID serves to manage a person’s verification and access conditions.
The core principle is to define identity, information about the identity, and the authority to perform a specific action separately, and then link these elements together in a controlled way.
This approach addresses providing investors with open project records and protecting personal data together. Which information will be public, which information can be seen only by authorized parties, and which changes will require re-verification are part of the identity design.
20.1 eBattery Digital Identity Approach
At eBattery, e-ID does not mean that all information held about a person or project is gathered in a single open record. The identity is the reference that allows the relevant asset or person to be recognized consistently within the system. The information linked to this reference is managed separately according to its purposes and access conditions.
The identity approach is built on four core elements:
| Item | Function | Example |
|---|---|---|
| Identifier | Distinguishes the relevant project or person within the system | Station e-ID or investor e-ID |
| Identity-linked record | Carries information about the relevant person or project | The station's devices, the investor's verification status |
| Verification information | Makes it possible to assess the source and validity of a piece of information | Document source, signature, verification date |
| Authority | Determines the conditions under which a specific transaction can be made | Joining a project, updating a record or approving a distribution transaction |
This distinction prevents the system from operating on wrong assumptions. A person's identity being verified does not mean they can access all investment projects. A station being registered also does not show that its license, maintenance or current operating status has been verified automatically.
Information with a known source and scope
In an important identity-linked record, the source is preserved along with the information itself. Who created the information, which document it is based on, when it was checked and the scope in which it is valid are all traceable.
For example, a station's hardware information can be verified from the manufacturer's document, installation status from field records, and operating authorization from the relevant official and contractual documents. If these sources differ from one another, this is kept visible in the record structure.
On the investor side as well, identity verification, country eligibility and authorization for a specific transaction are separate review steps.
Design aligned with standards
The W3C approach to decentralized identifiers (DIDs) offers a technical framework for associating an identity with verification methods and control authorities. This structure makes it possible to define separately the person or entity the identity refers to and the party authorized to manage the identity record.
In eBattery’s design as well, identity reference, record management and economic rights ownership are kept separate. The authority to update a station’s digital record is not the same authority as owning that station’s investment units.
eBattery e-ID is the platform’s identity and registry architecture. Official identity documents, operating permits and legal registries keep their own validity; e-ID serves to establish a link to these documents.
20.2 Station e-ID: Permanent Project Identity
The station e-ID is the permanent reference used throughout the life cycle of a station project under RWA. Financing, installation, operation, maintenance and renewal records are linked to this ID.
A permanent identity does not mean all project information is immutable. Information that changes is managed within the same project history with date and version information.
The principle is that the station e-ID is not derived directly from information that can change, such as the station name, device serial number or location. This way, a name change or equipment renewal does not require the project to be redefined.
Project identity and sub-assets
A station project may include more than one physical or technical element:
Site or installation area.
Charging units.
Independent charging service points.
Sockets and connectors.
Meters.
Communication devices and related control components.
These elements are tracked with their own sub-identities and linked to the station e-ID. When a meter is replaced, the meter record is updated; the project history is preserved. When a charging unit is decommissioned, the date until which it was in service can be seen.
This link prevents a past session from being incorrectly matched with another device set up later.
Operator and external system mappings
Different operating systems may use different identifiers for the same station. eBattery matches operator records, device management system IDs and other related references to its own project ID.
The validity periods of these mappings are retained. When an integration or operator reference changes, past data is not mixed up with the new identity.
While the station e-ID provides the shared reference within the platform, external systems' identifiers are preserved together with their sources.
The limit of identity continuity
The same e-ID is not allowed to represent two independent projects. The identity of a cancelled or closed project is not reallocated to a new, unrelated project.
Continuing the same project identity in a transfer or a change of scope depends on preserving legal and economic continuity. If a new project is created, it must be identified with a separate identity and its relationship to the previous project must be explained.
20.3 Digital Station Passport
The Digital Station Passport presents the information linked to a station’s e-ID in a project view that users can understand.
The passport allows the investor or an authorized service user to review the current status and history of the station. Technical information, operating records and economic data are shown with their own sources and access levels.
Core contents of the passport
| Information group | Content |
|---|---|
| Project definition | Project name, e-ID, scope and operating status |
| Location and access | Location, access details and service hours, within the appropriate scope |
| Technical structure | AC/DC type, devices, sockets and power information |
| Operations | Service provider, operator and related authorization references |
| Life cycle | Installation, commissioning, maintenance, renewal and relocation events |
| Economic structure | Unit structure, reporting periods and public financial indicators |
| Verification | Source, update date, record version and verification status |
The presence of information in the passport is distinguished from its verification status. A document having been uploaded is not shown as the relevant check having been completed.
Current view and historical view
The passport presents the station's current status while also linking to records from past periods. When reviewing the report for a particular period, the user can see the device and operating structure that applied in that period.
For example, the past energy sales of a station whose capacity has been increased are not presented as if they had been achieved with the new capacity. The date on which the new hardware went into service is taken into account in comparisons.
This approach helps investors interpret changes in station performance correctly.
Access to documents and transactions
Links the passport, project documents and the related onchain transaction records. An investor can go from a distribution summary to the relevant period account, and from there to the disclosed verification references.
QR codes or similar access tools used in the field are meant to direct people to the verified app view of the relevant passport. This redirection alone is not used as wallet transaction approval or as sufficient proof of the physical device's authenticity. The displayed station ID, location and service provider information are checked together.
20.4 Location, Socket, Power and Hardware Records
A station’s technical record affects the driver’s choice of service and the investor’s project assessment. For this reason, the meaning of technical fields and which physical element they belong to are clearly defined.
Location record
Location information includes, beyond the coordinates, elements that explain how users can access the station. Parking entrance, floor information, vehicle access direction, operating hours and special access conditions are added to the record when needed.
Correcting a small location error on the map and moving a station to another site are different events. A coordinate correction is recorded as a data correction; a relocation is recorded as a separate change affecting the project lifecycle.
For private or residence-related points, the extent to which the location is shown is assessed together with the service model and privacy conditions.
Relationship between charging unit and socket
In the record-keeping structure, station, unit and socket levels are kept separate. Which socket is associated with which device and how many vehicles can be served at the same time are described.
Having multiple connectors on one unit may not mean that all connectors can be used independently at the same time. The capacity offered is defined by the unit’s actual operating arrangement.
What the power information means
In the power record, different values are kept separate:
The hardware's nominal power capacity.
The capacity that the site or connection allows.
Structured operating boundary.
Power distribution that can be applied in shared use.
Instantaneous power measured during the relevant session.
This distinction prevents theoretical capacity from being confused with delivered service. The amount of energy is also measured separately from power; kW refers to capacity or instantaneous power, while kWh refers to the energy transferred over a given period.
Hardware and data reliability
Manufacturer, model, serial number, relevant technical documents and the version information needed for maintenance are kept in authorized records. Security-sensitive system information is not published without limits in the public passport.
Real-time status data is also separate from the technical specification record. A device's capacity is relatively permanent information, whereas availability or fault status depends on time. Real-time data is assessed together with its source and last-update information.
20.5 License, Service and Operating Information
The station's digital identity should explain under which responsibility structure the service is provided.
In the operating model eBattery targets, the licenses and the documents required for including the station in the network, for site relationships and for service delivery are linked to the relevant project record. The scope, validity and basis of each document are kept separate.
Visibility of authorities and responsibilities
The following relationships are explained in the passport and in authorized project records:
The charging network or service provider organization.
The party responsible for the station's day-to-day operation.
The ownership or usage relationship of the physical equipment.
The contractual arrangement that enables use of the site.
Maintenance and technical service responsibilities.
References to the relevant permits, licenses or certificates.
These records make visible the operating framework that also supports the investor's economic rights.
Tracking document status
The issue date, validity period, check date and, if any, amendments of the relevant documents are tracked. An expired document is not presented as current proof of authorization.
Verification is carried out through accessible official sources and authorized document checks. A document being marked as verified in the eBattery system does not mean that the relevant public authority has given a digital approval on-chain. The party that issued the source document and the party that performed the check are shown separately.
Operating changes
When the service provider or maintenance party changes, the effective date of the change is recorded. Which party was responsible in past periods is preserved.
A change in the operating relationship is assessed separately for its effect on the investment units’ economic rights. The station ID records this change; the legal validity of the change is ensured through the relevant permits and contracts.
20.6 Installation, Maintenance and Device Replacement History
A station's life cycle does not consist of a single initial record. The events that take place from installation onward form the project's technical and economic history.
In eBattery's approach to event logging, for an important transaction the date, the affected asset, the party performing the transaction, the supporting document and the outcome for the service are kept together.
Installation and commissioning
The installation history covers the equipment arriving at the site, assembly, connection work and required checks. Completion of physical assembly and the start of commercial service can be tracked as separate dates.
The commissioning record determines the period in which the station became operational by meeting the conditions required for service. A project in the financing and installation stage is not confused with an active station that generates operating performance.
Maintenance and fault records
A maintenance record contains the type of action, its reason, the affected device and service interruption information. The fault detection time, the response time and the time service was restored are tracked separately.
The fact that a maintenance request has been opened does not show that the maintenance has been completed. Separating the request, execution and closing stages makes it possible to understand the station’s actual condition.
These records help explain changes in revenue or availability indicators. It can be examined whether low usage in a given period was caused by maintenance.
Device renewal
In a renewal, the records of the old and new devices are linked to each other. The reason for the change, the cost, and the decommissioning and commissioning dates are retained.
If the new device has different measurement or communication capabilities, data comparisons are made taking this change into account. Linking the old and new measurement records during a meter replacement aims to prevent the same amount of energy from being counted twice or the continuity of the record from being lost.
Integrity of history
Corrections made to the verified event history are recorded together with their reasons. The relationship between the previous and the new record is preserved; an explanation added later is not confused with the time of the original event.
It is also essential to link technical events to financial documents. A record showing that a device was replaced can be reviewed together with the cost of that change as reflected in the project.
20.7 Investor e-ID and Investment Eligibility
Investor e-ID makes it possible to manage the verification and access status of a person or organization with respect to investment services.
This identity is a reference separate from the community username and the wallet address. This way, the social profile, personal verification documents and financial transactions can be managed with different access levels.
Identity verification and investment eligibility
Identity verification serves to recognize the person or organization carrying out the transaction. Investment eligibility assesses whether the conditions for participating in a specific project and transaction are met.
Under investor e-ID, the following elements are addressed to the extent the service requires:
The identity verification status of the person or organization.
Relevant country and residence information.
Individual or corporate participation structure.
Required investor classification.
Representation and signing authority in corporate transactions.
Participation conditions by project or transaction.
Validity and update status of the verifications.
For an institutional investor, the representative carrying out the transaction and the entity that holds the economic right are defined separately. A change of representative is not recorded as the entity's entitlement passing to someone else.
Project- and transaction-based assessment
An investor being eligible for one project does not automatically give access to a project in another country or with a different structure. Checks are applied according to the relevant service and the conditions at the time of the transaction.
Initial participation, secondary purchase and other transactions may require different assessments. The steps needed to complete the transaction are shown to the user clearly.
Preserving the current state
The validity of an ID document, residence, authority to represent, or the relevant classification may change. Investor e-ID supports updating this information and re-verifying it when necessary.
The need for an update is kept separate from the existing investment right. Restricting new transaction authority does not mean that rights a person acquired in the past are deleted automatically. Transactions involving existing assets and distributions are managed under the applicable agreement and legal framework.
The investor e-ID is not designed as an investment unit that can be bought and sold. It carries the verification and authorization relationship tied to a person or organization.
20.8 User Account, Smart Wallet and Identity Link
In eBattery, the user account, investor identity and smart wallet take on different roles.
The user account manages access to the app and preferences. The investor carries the e-ID, verification and eligibility status. The smart wallet handles interaction with on-chain transactions.
Linking these elements is carried out with the user's knowledge and the relevant verification steps.
Verifying wallet control
Writing a wallet address to an account does not prove that the address is controlled by the user. In the connection process, a transaction with a clearly stated purpose that verifies control of the wallet is used.
The signature given for the connection is designed to be limited by account, network, duration and a one-time verification value. This approval is not turned into an asset transfer or unlimited transaction authority.
Verifying wallet control and completing a person's identity verification are separate checks. Linking the two results together can be used for authorized investment transactions.
Account Abstraction approach
Account Abstraction supports managing wallet operations through smart account rules. ERC-4337 provides the technical foundation for capabilities such as customizable validation, different signature methods, recovery mechanisms and, in suitable structures, covering transaction fees. The scope of these capabilities depends on the smart account implementation used.
In eBattery's approach, the user is shown which account is connected, which transaction is approved and which authority is granted. A normal app session does not carry unlimited authority for financial transactions.
Multiple wallets and identity continuity
The same investor can use more than one authorized wallet. In this case, eligibility, limit and entitlement checks are applied consistently across wallets. Adding a new wallet is not used as a way for the same person to exceed participation limits by using different identities.
A change of wallet address may not require a change of the investor e-ID. However, verifying the new address and moving existing assets are different transactions. Adding a new address to the account record does not by itself move the tokens at the old address.
20.9 Verifiable Credentials and Authorization
Verifiable credentials make it possible to check the source and integrity of a statement a given party has made about a person or project.
The W3C Verifiable Credentials Data Model 2.0 defines the relationship between the party that issues the information, the party that holds it and the party that verifies it. Cryptographic verification provides control over the source and integrity of a claim; for the truthfulness of the claim's content, the authority of the source and the verification process are assessed separately.
Use within eBattery
Verifiable records can be used, for example, to show that an investor has completed the required identity check or that a maintenance operation was recorded by an authorized service provider.
Each of these records has a specific scope. A statement by the party that performed the identity check does not verify the station’s technical suitability. The maintenance provider’s record likewise does not determine the investor’s eligibility.
eBattery’s authorization model clearly defines which party can create which type of information and which action it can approve.
Checks performed during verification
For a record to be usable, its source, signature, validity period, link to the relevant person or project, and current status are checked together.
A correctly signed document is not considered sufficient for the transaction concerned if it was issued by an unauthorized issuer. Likewise, a verification that was valid in the past is not used as current evidence in a new transaction if it has expired or been revoked.
Access to information versus authority to transact
Being able to view a report does not grant the authority to change the report or approve a distribution. Authorization is applied according to the scope of the task.
For example, maintenance staff can create a technical incident record but cannot access investors' identity documents. The financial control role can review revenue and expense documents; this access does not create authority to transfer investment units.
In critical transactions, segregation of duties is designed to limit any one person from managing, alone, the entire process of creating data, checking it and applying the financial result.
Verification with minimal information
If it is enough to know that a certain condition is met for a transaction, the aim is not to share personal information outside that scope.
The verification result can be used separately from the underlying documents. Techniques such as selective disclosure can improve this approach to the extent they are supported and their security conditions are verified. The level of privacy offered by the method used is described in line with the capabilities actually provided.
20.10 Public Records and Personal Data Privacy
eBattery’s transparency approach aims to make the station’s economic and operational information open to review. This transparency does not require the unlimited publication of investors’ or drivers’ personal data.
The basic principles of KVKK require that data be processed for specific and legitimate purposes, in a manner related to those purposes and proportionate, that its accuracy be maintained, and that it be kept only for the necessary period.
These principles guide how eBattery's identity architecture separates data fields and limits access to what a task requires.
| Access level | Sample content | Management approach |
|---|---|---|
| Public project information | Project e-ID, explainable technical scope, activity summaries | Published after undergoing a personal data and security review |
| Rights holder access | The investor’s own transactions, distributions and related documents | Provided with account and authorization verification |
| Operational access | Maintenance details, device connections, service records | Limited according to the task and responsibility |
| Restricted personal data | Identity documents, address, contact details and required verification records | Protected in authorized systems; not made public |
Separating on-chain and off-chain records
Identity documents, personal addresses and similar data are not treated as content to be written to the open chain. Onchain records are limited to the scope needed for the transaction; personal data is managed off-chain under appropriate access and retention conditions.
The EDPB's final blockchain guidelines, published in 2026, also recommend keeping personal data beyond the identifiers in transaction metadata off-chain, and minimizing data at both the content and metadata level.
Identifiers may also qualify as personal data
A wallet address, a permanent investor number or a document hash can be linked to a person when combined with other information. For this reason, not every record without an explicit first and last name is considered anonymous.
In particular, taking only a hash of easily guessable ID numbers is not treated as a sufficient privacy method. Which reference is passed onto the chain is assessed together with the risk of re-linking.
The investor e-ID is prevented from turning into a single publicly visible tracking number across different services. Cross-context matching is kept within the necessary authorization and purpose limits.
Social profile and investment privacy
The community username, social map visibility and investor record are not linked to one another in a publicly visible way by default.
A user being active in the community does not mean they allow other members to see their wallet assets or investment history. The traceability of transactions on the public chain is also explained to the user in an understandable way.
Retention and deletion processes
The retention period of personal records is tied to the purpose of processing and applicable obligations. The status of financial or transaction records that must be retained despite an account closure request is assessed separately.
That permanent public chain records cannot be deleted like an ordinary database record is taken into account at the start of the architectural design. Privacy is supported by choosing the right data from the outset rather than relying on deleting records later.
20.11 Identity Update, Revocation and Recovery
The digital identity structure must be able to manage changes in information and access conditions over time. Updating, suspension, revocation and recovery are defined as distinct operations.
Update
Changes such as station capacity, the maintenance contact or the investor’s contact details are processed with the verification the relevant field requires. Not every change needs to restart the entire identity process; the affected information and authorizations are assessed.
For example, a change in an investor's residence may affect the eligibility check for certain projects. A change of phone number, on the other hand, may require an additional check for account security.
The effective date of updates and their relationship to the previous record are preserved.
Suspension and cancellation
Suspension means that a specific record or authority is temporarily unavailable for use. Revocation means that the relevant verification is no longer considered valid.
The W3C Bitstring Status List standard offers a mechanism for publishing the suspension or revocation status of verifiable information. In eBattery’s status management as well, the record content and its current validity status are assessed separately.
Revoking an eligibility record does not mean investment units are automatically destroyed. New transaction access, existing rights and obligations to be fulfilled are managed through separate processes.
On the station side too, a temporary service interruption, a change in operating authority and the permanent closure of the project are recorded as different situations.
Account and wallet recovery
Recovering the user account, re-verifying the investor’s identity and regaining control of the wallet are separate steps.
The recovery process covers verifying the requester, assessing existing security records, verifying the new access method and eliminating the risk of unauthorized access. It is designed so that additional approval, notification and appropriate waiting-period controls apply to high-impact changes.
If the smart account supports a recovery mechanism, the transaction is carried out through the predefined authorizations of that account. Assets in an external wallet that has no such mechanism are not assumed to be transferable just because the eBattery account has been recovered.
The new wallet connection, the status of assets in the old wallet and the records of investor rights are handled consistently. Creating the same economic right a second time during recovery is prevented.
Key and authorization changes
When the signing key of a device, verification provider or authorized employee changes, the authority of the new key is verified. The validity period of the previous key and the reason for the change are retained.
If a key is suspected to have been compromised, the affected records are reviewed by the relevant period and sources. Creating new records with secure keys and evaluating past records are carried out separately.
Closure and access to history
When a project ends, the station identity is not transferred to a new project. The closure status is recorded; project and transaction history that must be retained is protected under the relevant access conditions.
When closing an investor account as well, actions relating to identity, access, custody and existing rights are assessed separately. The user’s request, ongoing obligations and data protection rights are handled together.
In all of these processes, the reason for the change, the authorized party, the time and the outcome are recorded. This allows the digital identity to be used as a reliable reference throughout the life cycle of the station and the investor.
