A-Charge
FACILITY BRAND × PARKING OS.

Driver UI stays your facility brand. The OS is A-Charge.

Drivers just scan the bay QR (NO APP.). They need your facility name—not ours. Owners call for A-Charge®: the parking OS.

First, the premise

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. Yield is a number the owner calculates and takes responsibility for. After that decision, we help run the site cheaply.

In one screen

Who this is for

Coin parking, hotels, retail, municipalities, and operators of existing OCPP chargers—when you want the customer screen under your brand.

What changes

Logo, facility name, colors on the driver UI. Look-and-feel design orders. Signage around the QR. Terms links. First-line support defaults to the facility.

What does not

Billing logic, extra features, RightOS anonymous queue, Stripe Hosted Checkout, OCPP CSMS, load sharing, 20 languages, horizontal scale, contract/billing/system responsibility. Trademarks A-CHARGE® / I-S3.

Responsibility boundary

What drivers see

Your logo, name, and colors. Bay QR → fee check → pay. No account. No dedicated app.

What A-Charge / I-S3 owns

The parking OS. Contracts, admin, API, invoicing. OCPP central system and load sharing. Payment responsibility (card data never on our servers).

Logic cannot be changed. You can swap look-and-feel and display names.

LOGO
Your Facility Name NO APP. · Just scan.
Powered by A-Charge
Placeholder: facility logo swap example. No third-party logos.

In scope / out of scope

What you can customize

  • Logo (supplied at contract)
  • Facility / display name
  • UI colors
  • Design orders (driver UI look and QR-area signage drafts—no logic changes)
  • Links to your terms/policy (I-S3 privacy & tokusho links stay; co-listing OK)

What you cannot change

  • New features or logic changes
  • Billing logic (time-based parking fees remain the base)
  • RightOS queue design
  • Payment flow (Stripe Hosted Checkout UI is Stripe’s)
  • Language engine, security headers, key management, PCI posture

“Powered by A-Charge”

A small “Powered by A-Charge” footer is on by default. Contracts can turn it off. Your facility brand comes first; OS provenance stays.

A fit—or not

Likely a fit if

  • You want the customer screen under your brand (coin lots, hotels, retail, municipalities)
  • You keep existing OCPP hardware and only put the screen under the facility brand
  • You do not want guests to learn a new app name

Likely not a fit if

  • You want to replace a large membership-app network itself (competition / interconnect—not what white-label is for)
  • You need to rewrite billing or checkout logic, or you need new product features
  • Your goal is eMSP roaming replacement (queueing can optionally use the RightOS public API—that is separate)

Rollout steps

1 Consult

Use case, power, bay count. Whether white-label is required.

2 Brand intake

Logo, name, colors, terms links, Powered-by on/off. Design orders if needed (look only).

3 Connect

OCPP, registry, bay QR. Same as the usual four steps.

4 Operate

First-line support: facility. System, payments, remote charger ops: I-S3.

Pilot (free AC install campaign)

The free AC install campaign (up to 2 AC units, first 2 sites) can run as a white-label pilot—facility brand on screen, parking OS in the field.

Pricing

System fee, setup (~¥100,000/charger), and construction stay as today. Card fees: I-S3. White-label is a premium option above standard (unpublished—ask). Design orders available (look and feel only). No extra feature development.

Legal / display notes

We're going with A-Charge. Screens stay your name.

Email subject: “A-Charge white-label”. Phone works too.

Email us

Tel: 027-384-4646

Owners guide · FAQ

A-Charge Talk to us about installing
027-384-4646Call us (weekdays 9:00-18:00 JST) Chat with us24h · AI answers first (i-s3.com)