A-Charge® FAQ

No. Scan the bay QR to park, charge, and pay with card / Apple Pay / Google Pay. The flag is NO APP.

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.

This is not an invitation to invest. 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. The parking rate and the number of cars are the facility’s to set, and the yield is the owner’s own calculation and responsibility. What we help with is running the site after that decision, from about ¥2,000 per charger per month (flat while sales are about ¥10,000 or less). If you need a forecast, please prepare it on the facility side, where the land, power, and guest numbers are known.

We do not calculate or guarantee a payback period. There are no gates, flap locks, or payment kiosks to build — so their construction, maintenance, and breakdown costs never occur. You can start small with QR stickers and only the chargers you need. Note that about ¥2,000 per charger per month is still charged even in a month with zero sales.

Yes. Bays without chargers start earning with QR-based time billing first, and chargers are added only as needed. Output is auto-allocated within the site's intake limit, so you can grow the count without raising contracted power. OCPP chargers auto-register on connection.

The design does not wait for adoption. Billing is on parking time: bays without chargers and gasoline cars pay through the same QR. Even on a day with zero EVs, the lot earns as a parking lot. Global EV sales do keep growing (IEA Global EV Outlook: https://www.iea.org/reports/global-ev-outlook-2025), and Japan targets 100% electrified new passenger-car sales by 2035 — but A-Charge operations do not depend on that pace.

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

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.

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.

Primarily parking time, not selling kWh. You set rates per site and time band. Sales outlook is your number — you know who already comes.

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.

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.

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.

Set the site’s intake limit and simultaneous charging is auto-allocated so the total stays under contract. Easier to grow port count.

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.

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.

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

Consult → pricing & bay design → OCPP connect + QR stickers → go live. Setup fee guide: ¥100,000 per charger. Civil/electrical work is quoted on site.

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.

No. Home/workplace single installs: www.i-s3.com/ev. Multi-bay parking billing and ops: A-Charge on this site.

Yes. It fits destination / stay charging. Guests are not asked to install an app or join a membership — bay QR to card / Apple Pay / Google Pay. Driver UI: 20 languages.

Yes. Bays without chargers can start with the same QR time billing; add ports later. Designed as a whole-lot OS, not just a few DC stalls.

National and local programs depend on facility type, year, and equipment rules (e.g. OCPP). We do not guarantee approval or amounts. I-S3 helps sort eligibility against site conditions.

Yes. Logo, facility name, colors, and look-and-feel design orders are available (white-label). Billing logic, RightOS queue, Stripe Hosted Checkout, and the OCPP central system do not change. No extra feature development. Premium vs standard—ask. See /owners/white-label.

On by default (small footer). Contracts can turn it off. Facility brand first; OS provenance preserved.

No new gates, flaps, or payment kiosks (NO LOCKS. NO CONES.). If you already have a facility app, queueing can optionally use the RightOS public API. Payments stay on Stripe Hosted Checkout (card data never on our servers). Not an eMSP roaming replacement.