A viable shared power bank management backend should cover five core business modules: Power Bank Rental Stations & Assets, Orders & After-Sales, Merchants & Settlements, Data & Dispatch, and Users & Content. System fundamentals—including permissions, auditing, backups, APIs, and payment security—must be integrated across all modules and cannot be postponed until after go-live.
| Business Scope | Key Questions to Answer | Evidence Required During Acceptance |
| Power Bank Rental Stations & Assets | Where are the charging stations? Are they online? Which slots are malfunctioning? | Real-time status, last heartbeat, alarm logs, operation logs |
| Orders & After-Sales | How are rentals, returns, billing, and refunds processed? | Complete order trajectories, exception queues, refund and reconciliation records |
| Merchants & Settlements | How is revenue distributed? Who has the authority to modify rules? | Commission versioning, effective dates, approval records, settlement details |
| Data & Dispatch | Which locations are effective? Which stations need adjustments? | Metric definitions, raw data export, location vs. station performance comparison |
| Users & Content | How are campaigns and display content managed? | Permission scopes, publishing logs, withdrawal mechanisms, user consent status |
| System Fundamentals | Who can access the system? How are errors traced and recovered? | Role-based permissions, MFA, audit logs, backup and recovery protocols |
1. Module 1: Power Bank Rental Stations & Asset Management
The primary task of asset management is to ensure operators know the current status of every kiosk and power bank, and can pinpoint the exact time and location of any anomalies. The backend must display the rental station ID, location, network status, last heartbeat, slot status, battery status, and the most recent maintenance record.
- Alarms must be tiered by severity, trigger conditions, notification recipients, and resolution status to prevent all anomalies from appearing as identical red alerts.
- High-risk operations—such as remote reboots, unlocking, parameter modifications, and firmware updates—must be restricted to specific roles. The system must log the operator, timestamp, and values before and after the modification.
- Asset transfers must track movements from the warehouse to a location, from a location to repair, and to scrapping, ensuring the physical station count aligns with financial ledgers.
- Network connectivity may rely on 4G, WiFi, or wired connections. During procurement, confirm the actual network capabilities of the target model and the order processing rules in the event of a network outage.
2. Module 2: Order Processing & After-Sales
The order module must do more than just display paid orders. It requires dedicated handling for failed rentals, dispensed-but-unbilled items, returned-but-unclosed orders, duplicate charges, refunds, disputes, and overdue unreturned items.
| Stage | Content to Confirm During Procurement | Common Omissions |
| Pricing | Duration-based rates, cap amounts, currency, taxes, pre-authorization, or deposit rules. | Conflicting rules across locations; price adjustments lacking effective dates. |
| Payment | Target countries, merchant entities, acquiring accounts, and actual availability of wallets/cards. | Assuming that listing payment brands guarantees availability in all countries. |
| After-Sales | Refund permissions, dispute documentation, customer service notes, and processing time limits. | Settlements and commissions not being reversed synchronously after a refund. |
| Reconciliation | Correspondence between payment flows, order amounts, refunds, fees, and actual deposits. | Focusing only on gross revenue without explaining discrepancies in received funds. |
PCI DSS provides the technical and operational baseline for organizations handling payment account data. Even if payment processing is fully outsourced to a third party, the merchant must still confirm the service provider’s responsibilities, compliance status, and written division of labor. Backend demonstrations should clarify which data is stored by the system and which is handled by the payment service provider.
3. Module 3: Merchant, Agent & Settlement Management
The complexity of merchant and agent management lies in rule changes. A single location may change partners, an agent may manage cross-regional areas, and commission rates may be adjusted based on contract dates. The system must maintain rule versions; historical orders should be calculated based on the rules active at the time, while new rules should only affect orders placed after their effective date.
- Role hierarchies must align with actual contractual relationships, avoiding unnecessary agent levels created solely for display purposes.
- Withdrawals and settlements must feature clear statuses (application, review, payment, failure, and cancellation) and support detailed export.
- Data visibility should vary by role; finance staff, regional operators, merchants, and technical support should see different data scopes.
- Cross-currency settlements must define the exchange rate source, conversion date, fee bearer, and tax documentation requirements.
4. Module 4: Data Analytics & Dispatch
The value of a data dashboard depends on clear metric definitions. Revenue, successful payment orders, rental counts, return rates, station online rates, slot availability, and loss rates must all have explicit calculation methods and allow drill-down to individual orders, stations, and locations.
- Separate gross revenue from actual received funds, and distinguish between created orders and successfully paid orders.
- Incorporate station offline duration, empty cabinet duration, and full cabinet duration into location performance assessments.
- When calculating the payback period, factor in location revenue sharing, payment processing fees, communication costs, cloud services, maintenance (wear/loss), taxes, and depreciation.
- Allow for the export of raw data to facilitate financial audits and the creation of independent local reports.
5. Module 5: User & Content Operations
Coupons, memberships, messaging, and screen advertising can enhance operational flexibility, but they should not take precedence over order accuracy and station stability. During the initial phase, prioritize confirming pricing displays, user consent, unsubscription options, content moderation, and publishing logs.
Promotional campaigns must specify applicable locations, validity periods, eligibility criteria, usage caps, and the party bearing the cost.
Screen content should support previewing, scheduled publishing, emergency withdrawal, and file specification limits.
Any message distribution must comply with the consent and privacy requirements of the target market.
6. System Fundamentals Beyond the Five Modules
| Fundamental Requirement | Minimum Inspection Items |
| Accounts & Permissions | Independent accounts, role-based permissions, least-privilege access, MFA, deactivation of departed accounts. |
| Auditing & Tracing | Indelible records for logins, price adjustments, refunds, remote controls, and settlement modifications. |
| Data Protection | Transmission and storage encryption, data retention periods, export/deletion processes, and vendor responsibilities. |
| Backup & Recovery | Backup frequency, storage location, recovery objectives (RTO/RPO), and results of the most recent recovery drill. |
| Interfaces & Migration | API/Webhook scope, rate limits, error retries, data export formats, and exit strategies. |
| Support & Change Mgmt | Service hours, fault classification, response targets, version notifications, and rollback plans. |
7. How to Conduct Acceptance Before Procurement
Demonstrations should not be limited to page browsing. Require the vendor to run through business scenarios using a test power bank rental kiosk and deliver screenshots, logs, or exported files.
| Test Scenario | Operation | Pass Criteria |
| Network Outage & Recovery | Disconnect a running station from the network, then bring it back online. | Status changes are visible; no duplicate billing; alarm and recovery times are traceable. |
| Abnormal Return | Return a power bank to a slot while simulating an unclosed order. | The order enters the exception queue; customer service can verify the power bank and billing records. |
| Price Adjustment | Set a new price and effective time for a test location. | Old orders remain unchanged; new orders are billed according to new rules; modification logs are complete. |
| Refund & Settlement | Initiate a partial refund for a settled order. | Refunds, fees, and merchant commissions are adjusted according to agreed rules. |
| Permissions | View the same order using merchant, regional operator, and finance accounts. | Each role sees and processes only the content they are authorized to access. |
| Data Export | Export one day’s orders, payments, and rental status. | Field definitions are clear; data is recalculable; time and currency are consistent. |
8. Information to Prepare Before Requesting a Quote
- Target countries and planned go-live date.
- Merchant entities, acquiring accounts, and supported currencies.
- Kiosk models, network methods, initial batch quantity, and projected number of locations.
- Role relationships between operators, agents, merchants, customer service, and finance.
- Rules for pricing, caps, deposits/pre-authorizations, refunds, and revenue sharing.
- Required languages, maps, SMS, email, payment, and financial interfaces.
- Data storage, backup, service support, and exit/migration requirements.
STW can compile a functional list and demonstration scenarios based on the above information. Specific modules, payment methods, interface scopes, pricing, and delivery cycles are subject to the current version description and formal quotation.
9. Frequently Asked Questions
(1) Are more backend modules always better?
Module quantity cannot replace business correctness. First verify rentals, returns, billing, refunds, settlements, and station status, then evaluate extended features like memberships and advertising.
(2) If the payment list includes bank cards and e-wallets, is it ready for launch?
You must still verify countries, merchant entities, currencies, acquiring banks, account approvals, and specific payment products. Brand names displayed on a page only indicate potential integration directions.
(3) Can procurement decisions be made based solely on a demo backend?
It is recommended to complete scenario acceptance using the target hardware model and a test payment environment, and to include the pass criteria in the contract annex or delivery checklist.






