A power-bank station in an Auckland café and another in a distant visitor lodge can share an operating platform, but they cannot share a convenient maintenance visit. For a dispersed New Zealand network, the first design task is the service area: who can reach each station, who can accept returns, and what happens when a venue closes?
The practical starting point is a small, serviceable group of venues using physical Stripe readers, supported by CoreCharge rental software and compatible Android-based cabinets. Expand only after the first group demonstrates reliable borrowing, returns and payment reconciliation.
Start with a route, not a nationwide map
Select an anchor venue that opens reliably and has a staff member willing to perform basic checks. Add nearby complementary venues so a customer has another realistic return option. Record walking or driving time, opening hours and the person who can access each cabinet. A cluster is useful only when those venues form a workable customer journey.
Do not advertise return-anywhere service simply because multiple cabinets appear in the same dashboard. Agree which stations belong to the same return network, validate a cross-station return, and show the actual available choices to customers. Keep an independent opening-hours list for staff and support.
Confirm the New Zealand payment fit
Stripe lists WisePad 3 for New Zealand. Terminal payments require a matching account and reader Location country and use local currency. New Zealand domestic eftpos-only cards are not supported; co-branded cards use supported international card rails. These distinctions should shape the information beside the reader. See Stripe’s New Zealand regional guidance.
In the customer-owned-account arrangement, the operator controls its local Stripe account and receives rental proceeds there. CoreCharge connects payment status to rental orders, cabinet commands, returns and rent calculation. The cabinet’s built-in Android application connects the approved reader; guests should not need an extra merchant phone or tablet to complete the ordinary reader flow.
Before purchase, confirm the exact cabinet, mounting, Android integration, reader supply route and intended placement. Reader availability alone does not establish suitability or permission for every unattended installation. Test the agreed configuration at the actual type of venue.
Build a venue service card
Use one record per site. The following is a planning template, not a claim that every field is generated automatically by the software.
| Field | What to record | Decision it supports |
|---|---|---|
| Access | Opening hours, named contact and cabinet access | When a return or repair is possible |
| Identity | Venue code, cabinet serial and reader identity | Which physical unit support is discussing |
| Connection | Approved Wi-Fi or mobile-data plan and signal check | Whether the site can operate reliably |
| Inventory | Borrowable units, free return slots and spare allocation | When a balancing visit is needed |
| Service route | Nearest trained person and realistic travel time | When to pause new rentals and dispatch help |
Give local staff a short task list: check power, read the customer-facing screen, inspect for obvious damage and contact support using the venue code. Payment configuration and accounting changes should remain with authorised operators.
Validate recovery before the next long drive
Complete a borrow-and-return test at the site, then check the order and Stripe record. Test a controlled cabinet restart and the restoration of the approved network. Record what the customer sees when service is unavailable. If a backup connection is included, test its changeover rather than assuming it works because a SIM is installed.
Do not assume offline borrowing or offline return synchronisation has been validated. Define a support procedure for a customer already holding a power bank during an outage. Reconcile the eventual device and order events before making a billing correction.
Stripe’s Terminal testing guide provides payment test tools. Add cabinet-specific checks for release, return detection, stock and venue handover to make the evidence useful for rental operations.
Use the pilot to choose the next site
Review completed rentals, return availability, support visits and the time spent travelling. A high-traffic venue with difficult access may be less useful than a smaller site that stabilises the return network. Decide whether the next action is adding a station, moving one or improving the existing cluster.
Explore CoreCharge reader-equipped stations, or request a New Zealand pilot configuration with your proposed venues, service area and payment account country. The useful next deliverable is a route, hardware and acceptance plan for your network.
Implementation references checked on 16 October 2026. Deployment conditions and payment-method availability should be reconfirmed before ordering.