Reader-equipped power-bank rental creates three records that operators must understand together: the physical movement of each power bank, the rental order, and the money processed by Stripe. A station can look healthy while an order remains unresolved. A successful charge can appear in the payment account before the associated funds reach a bank.
CoreCharge supplies the device and rental operating layer, including orders, return records, rental rules and reporting. In the customer-owned Stripe arrangement, rental payments go to the operator’s own account. A daily routine joins these records and makes responsibilities clear.
Open with a short physical check
At each venue, confirm power, the customer-facing screen, visible damage, reader readiness and the agreed network connection. Compare available units and return capacity with the operating record. Assign a named person to report discrepancies using the station code.
Do not expect venue staff to repair a payment configuration. Their role is to describe the symptom and follow the agreed service instruction. If borrowing must be paused, retain a clear help route for customers already holding a unit.
Reconcile orders with payments
Choose a reporting timezone and a daily cut-off. Export the relevant CoreCharge rental data and compare it with Stripe activity using the payment reference or another confirmed matching field. Existing operating exports can support this review; agree the exact fields and report access during onboarding.
Stripe’s Balance reporting documentation separates gross activity, fees, net amounts and payouts. Those are different measures. A daily rental total should not be compared directly with a bank deposit without accounting for timing and adjustments.
| Daily check | Records to compare | Action when they differ |
|---|---|---|
| Completed rental | Order, return time and final charge | Investigate missing or incorrect completion |
| Open rental | Physical unit status and payment state | Separate a real ongoing rental from a missing return event |
| Cancelled attempt | Cabinet release history and payment outcome | Check for unintended release or unresolved authorisation |
| Refund | Approved correction and Stripe refund status | Track the existing request to its final result |
| Inventory | Borrowed units, returned units and physical count | Assign a stock or device investigation |
| Bank receipt | Stripe payout record and bank entry | Handle settlement timing separately from rental completion |
Use an exception queue for unmatched rows. Do not force agreement by editing the underlying order or adding an unexplained balancing figure. Each exception needs an owner, evidence, next action and closure note.
Calculate venue earnings from an agreed basis
A venue agreement should define whether its share uses gross rent, rent after refunds, or another expressly agreed base. State how payment fees, disputes, taxes and adjustments are treated. The software’s ability to display a calculation does not determine the commercial agreement.
For example, assume an illustrative venue has 100 currency units of qualifying rent, 10 units of approved refunds and an agreed 20% share of the remaining rent. Its calculated entitlement is 18 units. This is a calculation example, not a promise of actual performance or automatic transfer.
Keep the amount earned, the amount approved and the amount actually paid as separate fields. Record the bank or other authorised payment reference when a venue is paid. Automatic fund distribution is a separate payment architecture and should not be inferred from an earnings report.
Give exceptions a workable order of attention
Prioritise a customer unable to return a unit or facing a possible incorrect charge. Then review unknown payment results, missing return events and repeated reader failures. Inventory balancing and preventive maintenance follow according to your service plan.
Before issuing a financial correction, check the actual Stripe state. Cancelling an uncaptured payment and refunding a captured payment are different operations; Stripe’s cancellation and refund guide explains the payment layer. Apply the operator’s approval policy and retain the reference.
Do not assume alerts, escalation messages or every reconciliation step are already automated. Agree which checks people perform, what reports they receive and which integrations have actually been tested. A simple owned spreadsheet is more useful than an unmonitored promise of automation.
Close the day and improve the next week
Record completed checks, unresolved cases, stock movements and any station paused for service. Preserve the tariff version used by each order, especially when prices change. Limit customer information to the people who need it.
At the weekly review, look for patterns by venue and cabinet: repeated failed attempts, poor return availability, excessive service travel or inconsistent fees. Use these findings to decide whether to rebalance stock, retrain staff, investigate hardware or move a station.
Review CoreCharge’s reader-equipped station approach, or request an operating and reconciliation walkthrough. Bring your venue agreement and proposed tariff so the reports can be mapped to real operating decisions.
Implementation references checked on 16 October 2026. Deployment conditions and payment-method availability should be reconfirmed before ordering.