A-Charge® FAQ
A parking OS that turns a lot EV-ready. Industrial design — not a patchwork.
Do drivers need an app or account?
No. Scan the bay QR to park, charge, and pay with card / Apple Pay / Google Pay. The flag is NO APP.
Is this a small homemade system?
The opposite. A-Charge is a parking OS on Google Cloud: payments, charge control, queueing, power sharing, and monitoring in one design. Not spreadsheets or on-site DIY. Drivers just scan.
Is the queue a generic tool bolted on later?
No. It is our own RightOS. No membership list — only anonymous digital rights. No personal registration. If you already have a facility app, you can add just the queue via the public API. Docs: https://rightos.i-s3.com/software/rightos/docs
How do you handle payments and personal data?
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. Owner bank accounts encrypted at rest. Drivers generally need no account; queues stay anonymous.
Will the same system hold as chargers are added?
Yes. Endpoints are resolved from a ledger, so the same design scales out horizontally — not one forever-growing box. Utilization is watched; adding capacity is alert-driven. OCPP 1.6 and 2.0.1 share the same central system.
Is billing by kWh?
Primarily parking time. That keeps revenue more predictable than kWh-only models. Rates are set per site and time band.
Why “every parking space”?
A-Charge is a parking OS, not a few corner EV stalls. Bays with or without a charger share the same QR intake and checkout.
Does it work with AC (Level 2) chargers?
Yes. The wedge is simple checkout including AC chargers—not a heavy membership app for DC only. OCPP 1.6 / 2.0.1 chargers connect to the network.
What is the system fee?
Per charger per month. About ¥2,000 flat while monthly sales are around ¥10,000 or less; higher months use tiered rates. Card processing fees are paid by I-S3.
Can we add ports without raising contracted power?
Set the site’s intake limit and simultaneous charging is auto-allocated so the total stays under contract. Easier to grow port count.
Can we migrate existing chargers?
Many OCPP 1.6 or 2.0.1 units can be pointed at A-Charge and auto-registered without replacing hardware. The central system accepts both protocols side by side. Confirm per model/firmware.
Are vehicle identifiers stored as personal membership data?
No. Session start remains bay QR payment. When a charger provides a vehicle identifier (e.g. idTag), we do not keep the raw value—only an HMAC matching token bound to the active paid bay session. A token alone never starts charging.
Can we connect our own app or existing system to the queue?
Yes. Drivers still get NO APP (bay QR only), but if you already have a membership or facility app, you can add anonymous queue / usage rights via the public RightOS API. This is not an eMSP roaming replacement. Docs: https://rightos.i-s3.com/software/rightos/docs
What is the rollout flow?
Consult → pricing & bay design → OCPP connect + QR stickers → go live. Setup fee guide: ¥100,000 per charger. Civil/electrical work is quoted on site.
Who installs the hardware?
A-Charge® is a registered trademark of I-S3 Co., Ltd. Installation is handled by I-S3 (and partners). Home single-charger jobs → i-s3.com; parking billing OS → a-charge.jp.
Is this the same as a home wallbox install?
No. Home/workplace single installs: www.i-s3.com/ev. Multi-bay parking billing and ops: A-Charge on this site.
We're going with A-Charge.
For materials and a consultation, start on the owners page.
Owners guideRead the in-depth guide ｜ Installation by I-S3 (EV chargers)