{"data":[{"id":"cpo","title":"For charge point operators","intro":"Publish your locations and tariffs once; decide per partner which eMSP sees which site; receive sessions, CDRs and settlement statements from one place.","needs":["Reach drivers of several eMSP apps without a separate integration for each","Keep control of which sites and tariffs each partner can see","Get a netting statement per period instead of reconciling partner by partner","Carry the Türkiye-specific CDR fields without a custom integration"],"modules":["credentials","locations","tariffs","sessions","cdrs","tokens","commands","chargingprofiles","tr-cdr-additionals","parking-bays"],"portal_views":["My settlement statements","My invoices (after the financial go-live gate)","My records: sessions and CDRs","My contract and relationships","Sharing sets: which partner sees which location","My tariffs","Data quality"],"requirements":[{"id":"agreement","gate":"technical","text":"Signed roaming participation agreement and data processing agreement"},{"id":"identity","gate":"technical","text":"Legal name, tax number and, where applicable, charging network operator licence number"},{"id":"versions","gate":"technical","text":"An OCPI versions endpoint reachable from the hub and a Token A for the handshake"},{"id":"modules","gate":"technical","text":"Sender implementations for locations, tariffs, sessions and CDRs; receiver for tokens and commands"},{"id":"tr-fields","gate":"financial","text":"tr-cdr-additionals populated on every CDR"},{"id":"collection","gate":"financial","text":"Collection and invoicing details as set out in the agreement"}],"how_it_proceeds":[{"title":"Application and agreement","body":"You apply with your role and versions endpoint; the agreement and DPA are signed; your party is created in the hub directory."},{"title":"Sandbox and handshake","body":"Credentials are exchanged against the sandbox first; each module is exercised with test data and the gaps are listed before anything is live."},{"title":"Scope and relationships","body":"You decide which eMSPs see which sharing set; each relationship is accepted explicitly by both sides before data flows."},{"title":"Flow and statements","body":"Locations, status and tariffs reach your partners; sessions become CDRs; each settlement window closes with a netting statement you can verify against the ledger."}],"faqs":[{"q":"Do I have to open all my sites to every eMSP on the hub?","a":"No. The default is closed. You create sharing sets and accept relationships one by one; the hub never publishes a location outside an accepted relationship."},{"q":"My charging software is not Electroop’s. Can I still connect?","a":"Yes. The hub speaks OCPI 2.2.1 and 2.3.0 to any compliant implementation. Electroop products are one of several ways to connect; the hub is operated by E-Gridium independently of which software a partner runs."},{"q":"Which OCPI version should I implement?","a":"Either. The hub negotiates the version with each partner separately and translates between 2.2.1 and 2.3.0 where objects differ, so your partners’ version is not your constraint."},{"q":"How are fees charged?","a":"As a percentage per CDR, split between the two parties of a session, booked as its own line in the statement. The rate is in the participation agreement; it is not published here."}],"canonical_url":"https://egridium.com/en/for-cpos"},{"id":"emsp","title":"For e-mobility service providers","intro":"Receive locations, live status and tariffs from every CPO you have a relationship with; push your tokens once; start, stop and reserve through a single command channel.","needs":["Show more chargers in the app without integrating each network","Authorize drivers in real time at partner chargers","Get one statement per period across all CPO partners","Keep the driver relationship and the app in your own hands"],"modules":["credentials","locations","tariffs","sessions","cdrs","tokens","commands","chargingprofiles","bookings","token-groups","payment-sessions"],"portal_views":["My tokens","My sessions","My reservations","My commands and results","My settlement statements","My records: CDRs received","My contract and relationships"],"requirements":[{"id":"agreement","gate":"technical","text":"Signed roaming participation agreement and data processing agreement"},{"id":"identity","gate":"technical","text":"Legal name and tax number"},{"id":"versions","gate":"technical","text":"An OCPI versions endpoint reachable from the hub and a Token A for the handshake"},{"id":"modules","gate":"technical","text":"Receiver implementations for locations, tariffs, sessions and CDRs; sender for tokens and commands"},{"id":"authorize","gate":"technical","text":"Real-time authorize endpoint for tokens"},{"id":"collection","gate":"financial","text":"Collection and invoicing details as set out in the agreement"}],"how_it_proceeds":[{"title":"Application and agreement","body":"You apply with your role and versions endpoint; the agreement and DPA are signed; your party is created in the hub directory."},{"title":"Sandbox and handshake","body":"Credentials are exchanged against the sandbox; token push, authorize and the command round trip are exercised with the charger simulator."},{"title":"Relationships","body":"Each CPO relationship is accepted by both sides; from then on that CPO’s shared locations, tariffs and status reach you."},{"title":"Sessions and statements","body":"Your drivers charge at partner sites; sessions and CDRs arrive through the hub; each settlement window closes with one statement across all your CPO partners."}],"faqs":[{"q":"Do I get every CPO on the hub automatically?","a":"No. A relationship has to be accepted by both you and the CPO. Discovery of who is connected comes through hubclientinfo; the commercial step is yours."},{"q":"Can I run both roles?","a":"Yes. A party can be CPO and eMSP at the same time; the hub keeps the two role contexts and their statements apart."},{"q":"Is the hub a payment institution?","a":"No. The hub produces netting statements and payment obligations; money moves between the parties through the collection method set in the agreement. Card data never passes through the hub."}],"canonical_url":"https://egridium.com/en/for-emsps"},{"id":"nsp","title":"For navigation and data providers","intro":"Receive locations, status and tariffs that CPOs choose to publish to you; no sessions, CDRs or settlement, because you neither operate chargers nor sell to drivers.","needs":["Show accurate charger availability in a map or vehicle product","Receive one feed instead of scraping or integrating networks one by one","Respect each CPO’s publishing decision"],"modules":["credentials","locations","tariffs","hubclientinfo"],"portal_views":["My contract and relationships","My records: locations received","Data quality"],"requirements":[{"id":"agreement","gate":"technical","text":"Signed participation agreement for the data-consumer role"},{"id":"versions","gate":"technical","text":"A receiver-only OCPI endpoint for locations and tariffs"}],"how_it_proceeds":[{"title":"Application","body":"You apply as a data consumer; the agreement covers use of the data you receive."},{"title":"Handshake","body":"Inbound registration against your receiver endpoint."},{"title":"Publish decisions","body":"Each CPO decides whether and what to publish to you; the default is nothing."}],"faqs":[{"q":"Can I get historical sessions for analytics?","a":"No. The role is receiver-only for locations and tariffs; session and CDR data belong to the two parties of a session."},{"q":"How fresh is status?","a":"As fresh as the CPO publishes it; the hub relays status updates as they arrive and does not poll chargers itself."},{"q":"Is there a fee?","a":"Commercial terms for data consumers are agreed in the participation agreement."}],"canonical_url":"https://egridium.com/en/onboarding-and-sandbox"}]}