Park-and-ride
Plate recognised on entry; fee paid by card, QR or wallet on exit.
Running plate recognition, feesRoadmap card tap at the exit lane
The connecting layer for smart urban mobility.
Metro, buses, chargers, battery swap, parking and visitor sites each run on their own system. Dgreen connects them. Residents and visitors make one journey and pay with the bank card they already have. Operators work together, and the city sees the whole network. Charging and parking platforms run today; card payment and public transport follow a published roadmap.
- Vietnamese joint stock company, Hanoi
- Technology integrator, not a payment intermediary
- Open standards: OCPP, OCPI, GTFS and EMV contactless
One journey · Monday
Park-and-ride → charger → bus 09A → metro
- Park entry, plate recognisedBarrier opensRunning
- Tap at the charger, pre-authorization60,000 ₫ holdRoadmap
- Charging done, exact amount captured4,800 ₫Roadmap
- Tap at the bus door, route 09AFare by distanceRoadmap
- Tap at the metro gateFare by zoneRoadmap
- Exit lane, parking fee by QR5,000 ₫Running
Transactions today4
Bus and metro, combined daily1 per operator
Bank pays4 operators
Why it matters
Cities are adding metro, electric buses and chargers, but the systems do not yet connect.
Vietnam is electrifying transport and expanding public transport at the same time: low-emission zones, new metro lines, electric buses, shared charging and park-and-ride sites. Each one arrives with its own ticketing, payment and data.
For cities
Metro, buses, chargers and parking belong to different owners, and each reports data its own way. The city sees each system, not the network. It cannot use data to decide where transfers, prices or new sites should go.
For operators
Each operator runs its own equipment and payment channels. Transfers between operators, reconciliation and incident handling are done by hand. Every extra closed-loop card or app adds cost.
For residents and visitors
A journey across two operators means two apps, two top-ups, or cash and paper tickets. Visitors from abroad often cannot pay at all. Each extra step turns some people away.
With one connecting layer
Every system stays with its owner. The layer adds what they lack on their own: shared information, one journey, payment with the bank card people already have, joined-up benefits, and a full view of the network for the city.
Capabilities
One connecting layer with five capabilities, on top of the systems a city already runs.
The layer sits on top of the ticketing, charging and parking systems a city already runs. It does not replace them, set fares or hold money. It adds what those systems cannot do on their own. The city sets the rules: who joins, who owns which data, and who takes over at handover.
Where the layer sits in a city
Existing systems · kept
- Metro: stations, timetables, gates
- Buses: routes, stops, validators
- Chargers and battery swap
- Parking and park-and-ride
- Visitor sites: airports, ports, attractions
two-way, over open standards
Dgreen connecting layer
- Information: one service directory and live status
- Journey: multi-modal planning and disruption handling
- Open payment: bank cards at every service point, reconciliation across operators
- Benefits: transfer discounts and bundles under city policy
- City operations: aggregated data with no personal details, and alerts
Does not set fares, issue tickets or hold money
one-way, to channels
Channels · existing
- City and operator apps
- City data portal
- Operations dashboard
City governance: participation rules · data rights · acceptance and handover with source code · audit log
Acquiring banklicensed by the State Bank of Vietnam
Money goes from the acquiring bank to each operator's account. It never passes through the layer.
Operator's bank accounteach operator, under its card acceptance agreement
Five capabilities, and where each one stands
| Capability | What it does | Readiness |
|---|---|---|
| Transport information | Locations, routes, hours, prices and live status from every connected system, in one standard form. Each item has an owner and a timestamp. Open formats: GTFS for buses and metro, OCPP and OCPI for chargers, APDS for parking. | Running chargers, parking Roadmap bus and metro feeds |
| Journey planning and disruption | Plans a journey across metro, bus, walking, parking and charging. When a service is disrupted, offers an alternative from live data and records what happened. | Roadmap |
| Open payment and reconciliation | People pay with the bank card they already have, at every service point, through the acquiring bank each operator chooses. At chargers: pre-authorization and exact capture. On buses and at gates: the card schemes' transit model, one transaction per card per day. Once the parties agree the rules, one journey can be reconciled across operators. | Running single-operator reconciliation Roadmap cards at chargers after bank certification; buses, metro and multi-operator reconciliation after that |
| Joined-up benefits | Transfer discounts, park-and-ride bundles and visitor passes, funded by the city or operators. They are applied through an encrypted card token, so no card number is stored. | Roadmap |
| City operations and analytics | Aggregated data for the city, with no personal details: where parking fills up, where charging demand grows, which transfers fail. Fleet dispatch and tracking for operators' vehicles. AI assistants that read files, draft reports and cite sources. Staff approve every output. | Built operations dashboard Running fleet operations, AI assistants Roadmap city data portal |
Readiness is declared by Dgreen and verified by the city's lead agency on real equipment before a design is approved. Nothing is charged to customers before terminal certification with the acquiring bank.
One journey, step by step
A resident parks a petrol motorbike at the edge of a low-emission zone. They charge an e-motorbike or board a bus, then connect to the metro. One tap at each step. A visitor does the same from the airport, with a card from home.
Charge or swap
Tap at the charger: pre-authorization, exact capture, receipt and e-invoice.
Running charging platformRoadmap card tap, after bank certification
Bus
Tap at the door beside the existing validator; the city's ticketing system sets the fare.
Roadmap
Metro
Tap at the gate; the day's taps are aggregated into one transaction per card.
Roadmap
Destination
Airport shuttles, ferries, cable cars and attractions accept the same cards.
Roadmap
Payment methods
Contactless bank cards
Cards in phones and watches
Bank QR codes
E-wallets
RFID cards and monthly passes (parking)
Dgreen app
Available methods depend on the service point, the acquiring bank and licensed payment providers. In-app payments also go through the operator's acquiring bank or a licensed provider. In every case, the bank or licensed provider pays the operator directly.
How it works
Tap once. The bank pays the operator directly.
At chargers, the designed flow runs each session from tap to receipt. The bank pre-authorizes a hold. The session is capped at that amount, and only the energy delivered is charged at the posted tariff. On buses and at gates, the design uses the same readers and bank connections, following the card schemes' transit model. In every case, the acquiring bank pays the operator.
Where the data and the money go, step by step
Card
Dgreen reader
Dgreen platform
Acquiring bank's gateway
Issuing bank
card data stays encrypted until the bank's gateway
- Card → Dgreen readerTap. Card data is encrypted inside the reader.1
- Dgreen reader → Acquiring bank's gatewayPre-authorization request for the hold amount; passes through the platform still encrypted.2
- Acquiring bank's gateway → Issuing bankAuthorization over the card scheme's network.3
- Issuing bank → Dgreen platformApproved amount returned; it becomes the session cap.4
- 5Dgreen platformCharging runs; the charger reports meter values over OCPP.
- Dgreen platform → Acquiring bank's gatewayCapture of the exact amount; reversal for the unused part of the hold.6
- Acquiring bank's gateway → Issuing bankCapture and reversal; the issuing bank releases the hold on its own timeline.7
Money: the acquiring bank pays the operator's bank account. Dgreen never receives, holds or transfers payment funds.
At the charger: the designed flow
-
01
Plug in
The charger reports ready. The reader shows the hold amount and the price per kWh.
Charger → platform, over OCPP -
02
Tap to pre-authorize
The driver taps a contactless card. The platform requests a pre-authorization for the displayed hold amount, and the approved amount becomes the session cap.
Reader → platform → acquiring bank's payment gateway -
03
Charge
Energy and the running total update during the session. Charging ends when the driver stops it, the battery is full or the cap is reached.
Charger ↔ platform, meter values -
04
Pay the exact amount
The platform prices the session from the tariff and captures that amount, within 24 hours by design. A reversal is sent for the unused part of the hold, and the issuing bank decides when it is released. The driver gets a receipt and the operator's e-invoice.
Platform → acquiring bank's payment gateway
This is the solution design. It will be validated through testing and a pilot at each operator's own sites before rollout.
Designed for the exceptions
| When | What happens |
|---|---|
| The card is declined | Charging does not start and the session closes. |
| The issuer approves a lower amount | The approved amount becomes the cap. The driver can accept it or cancel, which reverses the pre-authorization in full. |
| Charging does not start, or no energy is delivered | The pre-authorization is reversed in full at once. The issuing bank releases the hold on its own timeline. |
| The capture fails | The platform retries automatically. If it still fails after 24 hours, the session goes to manual handling. |
On buses and at metro gates
RoadmapDesigned for the next phase, with transport operators, cities and acquiring banks. The city's ticketing system remains the only source of fares. The bank card is just a way to pay.
- 01
Tap at the door or gate
The reader checks the card against a deny list and a daily limit, on the device itself. Boarding works even offline.
Reader, offline-capable - 02
Fare set by the ticketing system
The reader passes each tap-in and tap-out to the city's ticketing system. That system computes the fare by distance or zone.
Reader → ticketing system - 03
One transaction per card per day
The day's trips are combined into one transaction with the acquiring bank: authorization at the first tap, capture at the end of the day. This follows the card schemes' transit rules.
Layer → acquiring bank's payment gateway - 04
Settled to the operator
The acquiring bank pays each operator for its own trips. The layer keeps the tap records and the fare for reconciliation and never holds the money.
Acquiring bank → operator's account
On a bus or at a gate, step by step Roadmap
Card
Reader on the bus or gate
City ticketing system
Dgreen layer
Acquiring bank
- Card → Reader on the bus or gateTap in. The reader checks the deny list and daily limit on the device; works offline.1
- Reader on the bus or gate → City ticketing systemTap record: card token, time, stop.2
- Card → Reader on the bus or gateTap out at the destination.3
- City ticketing system → Dgreen layerFare computed by distance or zone, returned to the layer.4
- 5Dgreen layerEnd of day: the day's trips combined into one transaction per card, per operator.
- Dgreen layer → Acquiring bankAuthorization at the first tap when online; capture at the end of the day.6
Money: the acquiring bank pays each operator for its own trips. The layer keeps tap records and fares for reconciliation only.
For acquiring banks and card schemes
Dgreen brings card acceptance to places that still run on cash, top-ups and closed-loop cards. EV chargers and parking come first, then buses, metro gates and visitor sites. We supply the terminals, the platform and the field work. The bank signs the operator as its merchant, assigns the MCC, certifies the terminal and pays the operator directly. We work with your certification, risk and security teams from the first test.
Devices
Two devices, from the charger to the metro gate.
Two Dgreen-branded terminals cover chargers, battery-swap cabinets, parking lanes, bus doors and metro gates. A payment-terminal manufacturer builds them and holds their EMVCo and card-scheme approvals. Dgreen specifies, configures, installs and supports them. Both accept contactless bank cards, read QR codes, connect over 4G or Wi-Fi and are managed remotely. Certificates and test reports are available on request.
Card reader for chargers and bus doors
A compact reader for each charger or vehicle door. At a charger, the driver sees the hold amount and the price before charging and follows the session on screen. On a bus, the rider taps and boards. Built to the vehicle standards listed below.
- Screen
- 5.5-inch touchscreen, anti-glare, 500 cd/m²
- Card payment
- EMV contactless, ISO/IEC 14443 A/B, on hardware with the manufacturer's EMVCo L1 and card-scheme approvals. Terminal certification with the acquiring bank before go-live
- QR codes
- QR and barcode reading
- Connectivity
- 4G, dual-band Wi-Fi, Bluetooth, GPS
Full specifications
- Security modules
- 6 SAM slots
- Durability
- IK07 impact rating; IP54 version for outdoor chargers
- Status
- Illuminated tap zone, 4 status LEDs, audio
- Transit standards
- EN 45545, ECE R118 and E-mark (manufacturer test reports on request)
- Mounting
- Pole mount with security lock
- Management
- Android 12-based OS, remote device management
Station terminal for sites and gates
A larger, weather-sealed terminal for open-air sites, parking lanes and metro gates. The 7-inch screen shows tariffs, progress and a QR code for the receipt. The scanner reads QR codes on paper or on a phone.
- Screen
- 7-inch touchscreen, anti-glare, 500 cd/m²
- Card payment
- EMV contactless, ISO/IEC 14443 A/B, on hardware with the manufacturer's EMVCo L1 and card-scheme approvals. Terminal certification with the acquiring bank before go-live
- QR codes
- 2D scanner for QR and barcodes on paper or phone screens
- Connectivity
- 4G, dual-band Wi-Fi, Bluetooth, GPS
Full specifications
- Security modules
- 8 SAM slots
- Durability
- IP65 sealed, IK08 impact rating
- Transit standards
- EN 45545 and ECE R118 (manufacturer test reports on request)
- Mounting
- Pole mount with lockable enclosure
- Management
- Android 12-based OS (Linux option), remote device management
Where the readers go
Product images of Dgreen-branded devices; screen content is illustrative. Final finish may differ.
Standards and security
Open standards, no full card numbers stored, the city stays in control.
OCPP
Open Charge Point Protocol
Chargers that support OCPP connect over an open protocol, whatever the hardware brand.
OCPI
Designed for roaming
Designed to support roaming between charging networks through the Open Charge Point Interface.
EMV
Contactless card acceptance
Dgreen readers are built on hardware whose manufacturer holds EMVCo Level 1 and card-scheme contactless approvals. Terminal certification with the acquiring bank, under card-scheme rules, will be completed before go-live.
PCI DSS
Designed to align with PCI DSS
Card data is encrypted in the reader and decrypted only at the acquiring bank's payment gateway. The platform relays it and never sees the full card number; it stores only a truncated number and the transaction reference. Dgreen will complete the PCI DSS assessment and registration the acquiring bank requires.
Licensed banks
Paid directly by the bank
The acquiring bank, licensed by the State Bank of Vietnam, pays the operator directly. Dgreen is not a payment intermediary: it supplies devices, software and integration, and never receives, holds or transfers payment funds.
RBAC
Access and data
Role-based access, an audit log of every action, and data kept in Vietnam where required.
GTFS
Transit data
Bus and metro routes, timetables and live status use GTFS, the open format transit agencies use worldwide. Any journey-planning app can read it.
APDS
Parking data
Parking locations, hours, prices and free spaces follow APDS, the Alliance for Parking Data Standards. A city can then compare sites and plan new ones.
City rules
Governance and handover
The city sets participation rules, data rights and operating roles. Source code and documentation are handed over at acceptance, under the terms of the contract.
Where things stand
| Item | Status |
|---|---|
| Code of Conduct and Compliance, and Privacy Policy | Published |
| EMVCo Level 1 and card-scheme contactless approvals of the terminal hardware | Held by the manufacturer; available on request |
| Terminal certification with the acquiring bank | Before each go-live |
| PCI DSS assessment | Planned; scope agreed with the acquiring bank |
| Bank-card acceptance on buses and at metro gates | Roadmap; scope defined with operators, cities and acquiring banks |
| Reconciliation of one journey across several operators | Roadmap; after the parties agree the rules |
Platform
A console for each operator, an overview for the city.
Each operator gets a console for operations, finance and partners, with its own data kept separate. The city gets an overview of the whole network. Residents and visitors use the apps they already have, or the Dgreen app where an operator chooses it.
Illustration of an operator's charging console. Not a live system or real data.
Dgreen app
Find a charger or a parking space, follow battery level and cost live, and get the operator's e-invoice. Payment goes through the operator's acquiring bank or a licensed provider. Dgreen manages app accounts under its Privacy Policy.
City dashboard
Aggregated data with no personal details: usage by hour, transfer points that lack a service, charging demand, service alerts. The city sees where it needs more parking, more chargers or a better connection.
Partner portals
Separate views for investors, site owners, operators and maintenance teams.
Fleet operations
Dispatch, route options, trip costs and live tracking for buses, tankers and electric fleets, with digital delivery records.
AI assistants
Assistants that read files, check them and draft documents and reports with cited sources. They use each user's own permissions, log every action and can run with data hosted in Vietnam. Staff review and approve.
Roles and audit log
Role-based access and a record of every action taken in the system.
Where it fits
For cities with public transport and many visitors.
The model is the same everywhere: the city picks a transfer hub, operators keep their systems, and one package is repeated. Cities with metro and bus networks start at a transfer hub. Tourist destinations start at the airport, the port and the attractions visitors already pay at.
- Metro and bus networks
- Tourist destinations
Metro and bus networks
Hanoi · Ho Chi Minh City
Low-emission zones, new metro lines and electric bus fleets. Start: one park-and-ride hub where bus, metro, charging and parking meet.
Tourist destinations
Da Nang – Hoi An · Hue · Ha Long · Nha Trang · Da Lat · Phu Quoc
International visitors arriving with a bank card from home. Start: airport shuttles, ferries, cable cars and attractions run by private operators; public transport next.
From 1 July 2026, fossil-fuel motorbikes are banned inside Hanoi's Ring Road 1; from 1 January 2028, petrol cars are restricted inside Ring Roads 1 and 2.
Source: Directive 20/CT-TTg of the Prime Minister, 12 July 2025.
Cities are listed as places where this model fits, not as customers. Programme details are agreed with each city.
Approach
One standard package, one city at a time.
A city names a lead agency and a transfer hub. Operators keep their systems. The same package is replicated: survey, integration, pilot, scale. Twelve months from kickoff to a measured pilot.
1lead agency per city
1transfer hub to start
12months to a measured pilot
0systems replaced
12 months
- 01
Discover
Agree the transfer hub, the connected systems, data rights and acceptance criteria. The parties: the lead agency, the operators and their acquiring banks.
- 02
Test
Connect sample equipment, readers and the layer. Test every journey type and failure case, and complete terminal certification with the acquiring bank.
- 03
Pilot
Go live at one transfer hub with real card transactions for six months. Measured against the agreed criteria: residents complete a full journey, operators reconcile and handle incidents.
- 04
Scale
Add lines, stations, charging businesses and parking sites under the same rules. Then hand over to the receiving agency with the source code. The same package moves to the next city.
What we measure in a pilot
Agreed with the lead agency, the operators and the acquiring bank before the first live transaction:
Plan a pilot with us- Approval rate of card taps
- Journeys completed across two or more systems without staff help
- Captured amount equals the posted tariff or fare, for every session and trip
- A reversal sent for every unused hold
- Equipment and reader availability
- Daily reconciliation that matches each acquiring bank's settlement report
- Incidents resolved within the agreed time, with a record for the city
About Dgreen
Vision
Green, smart mobility for every city in Vietnam.
Purpose
We connect energy, transport and payment so that the green choice is also the easy one.
Mission
We build and run the layer that connects a city's transport systems. People make one journey; the city sees the whole network. One team, on open standards, from the first transfer hub to the whole city.
Values
Open
Open standards and open interfaces. No customer is locked in, not even to Dgreen.
Evidence first
We pilot, measure and then scale, and we only claim what we can show.
Accountable
One point of accountability for the solution we deliver, coordinating our technology partners.
Secure
Customer data stays the customer's: encrypted, permissioned, kept in Vietnam where required and never reused.
Integrity
We do what we committed to. We never receive, hold or transfer payment funds. Our policies are public.
Leadership
The team behind Dgreen.
[Name]
[Title]
[Name]
[Title]
FAQ
Questions partners ask first.
Does Dgreen receive, hold or transfer payment funds?
No. The acquiring bank, licensed by the State Bank of Vietnam, pays the operator directly. Dgreen supplies devices, software and integration, does not provide payment intermediary services, and never receives, holds or transfers payment funds.
Which cards work?
Contactless bank cards, and cards stored in phones and watches, as accepted by the operator's acquiring bank. QR and e-wallet payments are available where the service supports them.
Where does card data go?
It is encrypted in the reader and decrypted only at the acquiring bank's payment gateway. The platform keeps a truncated card number and the transaction reference, never the full number.
Are the devices certified?
The hardware manufacturer holds EMVCo Level 1 and card-scheme contactless approvals. Terminal certification with the acquiring bank, under card-scheme rules, will be completed before go-live.
Can we keep our existing chargers?
Usually, if they support OCPP. We confirm each charger model in integration testing before rollout.
How does a project start?
It starts with a site survey. Then integration testing and terminal certification with the acquiring bank. Then a pilot at a few sites, measured against criteria agreed in advance, before rollout across the network.
I was charged, or a hold has not been released. Who do I contact?
The charging operator named on your receipt is the merchant and handles refunds. The unused part of a hold is released by your card's issuing bank on its own timeline. If you cannot reach the operator, contact Dgreen and we will help the operator check the session.
Who is the merchant, and who handles disputes?
The operator, under its card acceptance agreement with the acquiring bank. For each refund or chargeback, the platform gives the operator and the bank the session record: meter readings, tariff, timestamps, truncated card number and transaction reference.
What is Dgreen's PCI DSS status today?
Not yet assessed. By design, the platform never has access to full card numbers. Dgreen will complete the assessment the acquiring bank requires before go-live.
Do you support bus and metro fares today?
Not yet. Charging and parking platforms run today. Bank cards at chargers follow terminal certification with the acquiring bank. Bank-card fares on buses and at metro gates are on the roadmap, on the same devices, platform and bank connections. We define the scope with transport operators, cities and acquiring banks.
Does a city have to replace its ticketing system?
No. The layer connects to the existing ticketing, charging and parking systems and adds to them. Fares are still computed by the city's ticketing system.
Who owns the data?
Each operator stays the controller of its own data. The city receives aggregated data with no personal details, under rules it sets. Dgreen processes data under contract and keeps it in Vietnam. Source code and documentation are handed over at acceptance.
What does a city pay?
It depends on the programme. The funding model is set out in writing before the city approves the design. In every case, the city keeps governance of the platform.
Talk to the Dgreen team.
Cities and transport agencies, operators, banks and card schemes, tourist destinations: tell us what you want to run, where and when.
Email our team- contact@dgreen.vn
- Registered office
- Hanoi, Vietnam
- Company
- Dgreen Technology Solutions Joint Stock Company
- Legal representative
- Đào Phúc Trí