CoreCharge CloudShared Power Bank Platform
Request a Plan
Browser-based renter flow

H5 Shared Power Bank Rental Platform for QR Scan-to-Rent

CoreCharge Cloud provides an H5 shared power bank rental flow that opens in a mobile browser after a user scans the station QR code. The flow can show rental rules and pricing, send the user into the configured payment-authorization path, request a power-bank unlock, display the active order and guide the return or refund-support process. Operators manage the same orders, devices and support states from the SaaS dashboard. Final payment methods and white-label scope are confirmed for each market and project.

For shared power bank operators, agents and local brand teams. This is not a retail power bank checkout page.

Renter-facing shared power bank station map with QR scan entry
Shared power bank rental payment selection with wallet and card methods
Merchant and operator dashboard with orders, devices and merchant statistics
Rent flowPayment optionsMerchant operations
What H5 means

A renter-facing web application, connected to the operating system.

H5 is a mobile web route rather than an App Store download. It can reduce the first-use barrier for a venue pilot, while the operator still needs a configured station, order service, payment-provider path and support workflow behind the page.

1. Scan the station QRThe browser opens the configured rental route for that station or market.
2. Review rules and pricingThe renter sees the current terms, pricing and support entry before authorization.
3. Authorize and unlockThe selected provider handles the configured authorization step before an unlock request is sent.
4. Rent, return and reviewThe active order guides return; support staff review exceptions, settlement or refund questions.
Operator workflow

The browser flow is only one side of the operating loop.

Device stateReview station connectivity, available power banks and offline alerts before venue teams report a problem.

Order stateFollow authorization, unlock, active rental, return and exception states from the same operating layer.

Merchant and agent rolesPlan access for operator, merchant, agent and support users without exposing every function to every role.

Support and refundsGive support teams the order and device context needed to review a return or refund request.

CoreCharge Cloud operator dashboard interface showing orders, devices and merchant reporting fields
H5 first

Use a browser route for lower first-use friction.

Suitable when a pilot needs QR access without requiring every renter to install an app. Provider compatibility and browser behavior still need project review.

Native App

Use an App when the operating model justifies it.

A branded App can support repeat-use journeys and store discovery, but introduces store, update and maintenance work that an early pilot may not need.

Hybrid path

Keep H5 entry while preparing an App path.

Operators can preserve QR browser access and later add an App where market behavior, support capacity and brand plans support the extra scope.

White-label and payment boundaries

Branding and payment availability are confirmed, not assumed.

Renter interface

Selected logo, colors, language, rental copy and support entry can be reviewed as part of the white-label scope.

Payment provider

Authorization, deposit, settlement and refund behavior depend on the selected provider, target market and approved integration plan.

Hardware link

QR identity, station protocol and unlock behavior must match the compatible station model and project configuration.

Public route evidence

Review browser-based rental entry patterns without inferring a customer relationship.

Public H5 route example

This independently accessible route is linked only as observable browser-flow evidence. CoreCharge Cloud does not assert that the brand is a customer or partner.

Open public route

Public payment-flow route

This link points to an independently visible web route. It is not a customer, provider, download or partnership claim, and payment availability still requires project review.

Open public route
Implementation inputs

What an operator should prepare for an H5 flow review.

Market and languageTarget country, renter language, venue type and the intended first city or operating cluster.

Station and protocolStation model, QR identity, communication protocol and power-bank return behavior.

Rental rulesPricing logic, rental duration, return rules, support escalation and refund review expectations.

Payment pathSelected provider, onboarding status and the desired authorization, settlement and refund sequence.

Does an H5 rental flow require an App download?

No. H5 opens in a supported mobile browser after the renter scans a station QR code. The configured payment and authorization path may still depend on the selected provider and market.

Can the H5 interface use an operator's brand?

White-label planning can cover selected colors, logos, renter copy and support entry. Final scope depends on the agreed software, hardware and deployment requirements.

How does H5 connect to the operator dashboard?

The renter flow creates and updates order states that operators review through the CoreCharge Cloud SaaS dashboard alongside device, merchant and support information.

Are local payment methods automatically available?

No. Payment methods, authorization behavior, settlement and refund handling must be reviewed with the selected provider for the target market and project.

Review an H5 rental flow for your target market.

Send the station model, target market, payment-provider path and preferred renter journey. We will identify the software, device and integration questions for a controlled pilot.

Last reviewed: 18 July 2026.

Request PlanWhatsApp