Shared power bank rental software evidence
Shared power bank rental is the primary software use case. The canonical buyer-facing capability page is CoreCharge software features. This Developer Center page supplements that canonical page with implementation evidence and delivery boundaries; it is not a second marketing canonical.
Evidence boundary
Publicly documented means a CoreCharge page describes the capability area. It does not prove that every field, provider, market or station model is enabled in a particular tenant.
Capability matrix
| Capability | Operator outcome | Evidence state | Delivery boundary |
|---|---|---|---|
| Renter browser H5 | Open the rental journey without requiring an installed app | Owner-defined scope | Camera access, browser support, QR permission and market UAT must be verified |
| Camera and QR scan | Read a station code from the renter's supported browser | Owner-defined scope | Permission, HTTPS, browser and device behavior vary; scanning is not payment approval |
| Optional renter apps | Offer Apple or Google mobile applications where approved | Optional, project-specific | Store, account, region, review and compliance gates apply; availability is not universal |
| Operator desktop web | Run daily device, order, payment and support workflows on desktop | Public software scope | Role and tenant acceptance remain release-specific |
| Operator mobile H5 | Access approved operating workflows from a mobile browser | Owner-defined scope | Exact pages and responsive acceptance require project confirmation |
| Optional operator app | Offer an operator app when included in an approved project | Optional, project-specific | Store, region, device and account gates apply |
| Role-based access control | Separate platform owner, operator, agent and merchant permissions | Publicly documented | Exact permissions and data scope must be accepted per role and tenant |
| Station health visibility | See online state, freshness and abnormal behavior | Publicly documented | Exact telemetry and alert thresholds require project confirmation |
| Slot and battery availability | Review inventory and available power banks | Publicly documented | Model and firmware mapping require compatibility evidence |
| Rental and order timeline | Connect renter action, station, time, return and support history | Publicly documented | Retention and export fields require contract confirmation |
| Payment and refund review | Distinguish authorization, payment, refund and manual review | Publicly documented | Provider approval, account state and market rules are external dependencies |
| H5 rental journey | Validate scan, payment, release, return and exception states | Verification guide available | Production URLs and provider callbacks are environment-specific |
| Agent and merchant roles | Separate operator, agent and venue visibility through RBAC | Publicly documented | Role permissions must be agreed and verified per deployment |
| Dashboard and reconciliation fields | Trace source, freshness, role and action for operating fields | Field guide available | Exact field inventory requires tenant and version evidence |
| Operating reports | Compare venue, station, order and support performance | Publicly documented | Metric definitions and settlement rules require project confirmation |
| Multi-format station support | Plan pilots across published slot formats | Public product signal | Exact model-to-protocol certification is pending |
| Hardware interoperability | Evaluate approved alternative software integration | Public documentation only | Partner profile and authenticated test evidence are pending |
| Machine-readable API contracts | Review event, HTTP and frame shapes | Placeholder schemas available | No production endpoint or credential is included |
| White-label brand configuration | Align renter and operator surfaces to a brand | Needs product-owner evidence | Assets, languages, app accounts and scope are project-specific |
| Notifications and escalation | Route offline, payment and support exceptions | Needs product-owner evidence | Channel, recipient and delivery proof are environment-specific |
| App distribution | Distribute optional renter or operator applications | Needs project-owner evidence | Apple/Google store availability is not universal and must be verified by store, account and region |
Canonical public evidence
- Canonical CoreCharge software features
- Overseas shared power bank software specification
- H5 payment, return and refund UAT guide
- Agent dashboard field and reconciliation guide
- Operator software feature checklist
- Station slot selection guide
Feature acceptance record
For each contracted capability, acceptance should record:
| Field | Example of acceptable evidence |
|---|---|
| Capability ID | Stable identifier from the signed scope |
| Tenant and role | Named non-secret tenant label and tested role |
| Release | Application release or asset hash |
| Data source | API, database view, provider result or device event category |
| Freshness | Timestamp and expected delay |
| Test case | Input, expected behavior and result |
| Visible result | Browser or API evidence with secrets and personal data removed |
| Owner | Product, engineering, operations or external provider |
| Status | VERIFIED, CONDITIONAL, FAILED or UNKNOWN |
Buyer checklist
Before purchase, ask for evidence that connects the proposed station models, renter H5 or optional app entry, camera and QR behavior, payment provider, refund policy, operator desktop/mobile channels, RBAC roles and reporting fields. A complete-looking dashboard screenshot is not a substitute for a release-specific acceptance record.