Not a few DC stalls in the corner. A parking OS built to roll out across the whole lot — including ordinary AC chargers — with one simple QR checkout. OCPP chargers and bay stickers are enough to start. We do not solicit investment. We support the facility that has already decided to spend, from about ¥2,000 a month. Yield is the owner’s own calculation.
Simple checkout, including AC chargersDesigned for every parking spaceNo app / no registration for usersYield is the owner’s own calculationAuto power sharing within the site cap (an option to grow without an upgrade)Works for non-EV parking tooCamera bay occupancy visibilityNo card data on our serversHorizontal scale by designOur own anonymous queue
Installing chargers does not guarantee a profit. A-Charge is the intake system for a facility that has already decided to spend on bays or chargers, so it can run them at low cost. Yield is a number the owner calculates and takes responsibility for. After that decision, we help run the site cheaply.
Whether to invest is the facility’s decision. We do not solicit it.
Parking rates and how many cars come are yours. Yield is the owner’s own calculation.
Even in a month with zero sales, about ¥2,000 per charger per month is still charged (flat while sales are about ¥10,000 or less).
Look at I-S3’s electrical construction and monitoring systems—not at how many A-Charge billing sites exist yet. A-Charge is the parking OS built on that work.
Large-scale solar
High-voltage interconnection, self-consumption, repowering, and O&M. Food-plant ~200 kW self-consumption and high-voltage ~500 kW upgrades: live sites, multiple stakeholders, electrical work done safely.
Advanced operations systems
Remote solar monitoring and 30-minute demand sizing, our own RightOS anonymous queue, and an OCPP 1.6 / 2.0.1 central system with load sharing under the site power cap. Not spreadsheets bolted on after the fact.
EV charger installs (AC through DC)
Hundreds of jobs centered on Gunma. Mostly AC (Tesla Wall Connector and similar); over 99.9% of residential jobs finish the same day. Eleven prefectures by our own visits, six in Kansai via partners (17 total). We also design turnkey facility packages that include 50 kW / 120 kW DC.
Billing sites under the A-Charge name are still being added. Installing, isolating, monitoring, and reconnecting electrical plant is I-S3’s core work.
Share the long-form clips matched to your language before the brochure—why lots get chosen, the guest journey, and no locks/cones. Other languages, Shorts, and the classic ~90s intro are in the video library.
Be the lot that gets chosen
AC × every bay × NO APP.—plus how utilization-linked fees feel from the owner’s side.
Intake, billing, payments, queueing, power sharing, and monitoring, designed as one system from day one for fleet-scale operation.
Queueing is our own RightOS
Not a generic kiosk app bolted on. No membership list — only anonymous digital rights. No personal registration. If you already have a facility app, you can add just the queue through a public API.
Security is in the architecture
Card numbers never touch our servers (Stripe Hosted Checkout). We keep PCI card-data environments out of our stack. TLS, HSTS, CSP. Keys in Google Secret Manager. Bank accounts encrypted at rest.
Not one forever-growing box
Each charger’s endpoint is resolved from a ledger, so the same design scales out horizontally. Utilization is watched; adding capacity is alert-driven. Google Cloud managed infrastructure, monitored around the clock.
Standard protocol and power control
OCPP 1.6 and 2.0.1 on the same central system. Vendor-neutral. Output is shared automatically under the site power cap. Driver screens in 20 languages.
How we differ — and why owners choose us
🔌
Even with AC chargers, checkout is just a QR
Not a heavy membership app built only for rapid chargers. Drivers scan the bay QR — card / Apple Pay / Google Pay. First-time guests start in seconds; 20 languages keep inbound visitors.
🅿️
Built for every parking space
Not “a few EV stalls in the corner.” Same QR intake and payment for bays with or without chargers. With optional cameras, timed parking for gasoline cars rides the same flow.
🖥️
Almost no operational workload
Chargers register themselves when connected. Pricing, monitoring, and refunds are all handled by our team on your behalf. No on-site staff needed; collection finishes automatically through online payment.
⚡
Gentle on your electrical equipment
Within the site power cap (a value set by the operator), output is shared evenly across the chargers in use. It gives you an option to add chargers without upgrading your electrical service, and pairs well with rolling out more AC ports across the lot. Output per charger drops as more units charge together, so the cap is designed after we check the site's equipment.
FACILITY BRAND × OS
Driver UI stays your facility brand. The OS is A-Charge.
Swap logo, name, and colors. Billing, queue, checkout, and OCPP stay fixed. NO APP. — owners call for the parking OS by name.
If another charging app or CSMS shuts down or becomes unsustainable, you can often reconnect the same OCPP 1.6 / 2.0.1 hardware to A-Charge instead of replacing the units.
Point the charger at our URL and it registers automatically. Drivers keep app-free QR checkout. Parking and charging stay one flow. When a vehicle identifier is available, we still require no membership—only a matching token is used.
As the fleet grows, our team tracks status, occupancy, and issues per facility from our ops screen, and can send you a CSV or printed report whenever you'd like one.
* Compatibility depends on model, firmware, and network. We verify before go-live.
Actual screens
User screen (after scanning the QR) No app, no sign-up. Users check the rates, pay on the spot, and start charging or parking.Our admin screen: pricing plan settings Our team sets parking and charging rates and billing rounding per facility from this screen on your behalf. We apply changes whenever you'd like.Our admin screen: operations dashboard Our team monitors charger connectivity, faults, and bay occupancy live from this screen, and handles refunds from here too.
* Screens from the system actually in operation. Displayed contents and rates are examples.
Go deeper: why owners choose A-Charge
The AC × every-bay × simple-checkout wedge, utilization-linked fees, and load sharing—on one page.
Billing is based on parking time, not selling kWh like a public charging station. That means you need not pass electricity-price swings into the rate. It does not mean we forecast your sales.
Parking and charging rates can be set freely per facility and per time period. Switching from free (promotional) to paid operation takes effect instantly from the web.
Settlement is calculated automatically from actual usage time at the end of each session. Even if a user leaves without checking out, billing is automatic with an upper limit, so you never miss revenue.
At busy facilities, our own RightOS anonymous queue & reservation (no personal data collected) improves turnover. It is not a generic tool bolted on later.
Optional cameras provide bay occupancy visibility—vacant/occupied on the user screen and ops dashboard.
Whole-lot by design: the same QR intake and payment apply to bays without chargers. With optional cameras, that becomes timed parking for all vehicles, including gasoline cars.
Information security (no card data on our servers)
Card data never touches our servers. Payments use Stripe Hosted Checkout; A-Charge does not collect or store PAN, CVV, or expiry (we keep card data out of our own environment).
Traffic is protected with HTTPS (TLS). Responses include HSTS, CSP, nosniff, Referrer-Policy and related security headers.
Secrets for Stripe, OCPP, and encryption keys are stored in Google Secret Manager — never hard-coded.
Sensitive owner data such as bank account numbers is encrypted at the application layer before storage.
No user accounts. Anonymous queues. Arrival location is checked but not stored. Vehicle IDs from chargers are not bound to membership—matching tokens only. Admin tools are limited to our corporate domain.
Scalability — from a few chargers to large fleets, same design
Horizontally partitioned by design — no re-architecture as you grow. Each charger's connection endpoint is resolved through a shard registry, so capacity grows simply by adding connection servers, with zero impact on existing chargers or users, on the same architecture from a handful of units to large fleets. We do not assume one box holds everything forever.
Capacity is managed automatically. New chargers are placed on the least-loaded connection server, utilization of every server is monitored continuously, an alert fires automatically when a threshold is reached, and adding a server is a one-command operation.
Runs on Google Cloud managed infrastructure. Auto-scaling with demand, plus uptime checks, error-surge detection, and automatic charger-fault detection and alerts via Cloud Monitoring (alerts go to email). On-call coverage and response times are set separately by contract.
Connects over a standard protocol (OCPP 1.6J). Live connection tests have been run on only a limited set of AC and DC chargers, so connection conditions are checked per model and firmware (OCPP 2.0.1 is supported on the server side and mock-tested only; live-charger verification is still to come). The operations dashboard uses differential updates built for growing fleets.
Remote commands survive scale-out and updates. Charge commands are handed off so the server that holds the WebSocket is the one that sends them — less breakage when capacity is added or software is replaced.
System fee
All fees are per charger, per month. To keep low-utilization sites viable, the fee is a flat ~US$14 while monthly sales stay within about US$70 (JPY ¥2,000 up to ¥10,000). Above that, the rate declines with sales: ~20% from just over US$70 up to about US$175, 15% from about US$175, and 10% from about US$350. The same rule works whether utilization is still low or rising.
Parking-only bays without a charger are billed at 10% of the facility's combined parking sales with no flat fee; a month with no sales costs nothing.
Card / Apple Pay / Google Pay processing fees are paid by I-S3. Owner payouts deduct only the system fee from sales.
The one-time system setup fee is JPY 100,000 per charger (both fast and standard chargers). Installation work is quoted separately based on site conditions. We can also supply chargers and arrange installation work for you.
This fee rule is the same worldwide. The figures above are approximate US-dollar equivalents; actual contracts and settlement use the currency of the country where the charger is installed.
Each charger is registered with its installation site (facility location) and currency. Parking and charging rates for users are also set and displayed in the installation country's currency.
Monthly sales (per charger)
System fee
〜10,000円
定額 2,000円
10,000円超〜25,000円未満
20%
25,000円以上〜50,000円未満
15%
50,000円以上
10%
Easy setup in 4 steps
Install chargersChargers that connect over OCPP 1.6J are eligible (connection conditions are checked per model and firmware). LTE-equipped models may need no network construction, depending on the device
Connect to A-ChargeSet the connection URL and the charger registers automatically. Setup guide provided
Set your pricingTell us your preferred parking rate, charging rate, and power limit, and our team configures it on your behalf. Just let us know if you'd like to change it later
Post the QR codesApply a QR sticker to each bay and start operating
* Chargers and electrical work can be arranged by the facility, or we can propose and arrange them. We also support reconnecting existing OCPP-compatible chargers.
Solar, operations systems, and EV installs (AC through DC) are I-S3’s core work. We will size the site to your budget, and demo screens are available right away.
A-Charge. Just scan. NO APP.
