A visitor can borrow a power bank in seconds and spend the rest of the day moving between a hotel, restaurant and attraction. For an Italian tourism operator, the difficult question is often where that visitor can return it. A convenient physical card reader starts the rental; a realistic return network makes the service useful.
A sensible pilot defines the guest journey before distributing cabinets. Choose a small group of locations that guests actually move between, check their opening hours and agree how each venue will handle returns. More dots on a map do not necessarily create a better network if access is uncertain or all the return slots are full.
Start with a local reader configuration
For compatible CoreCharge POS-ready stations, the Italian configuration uses WisePad 3 with the cabinet’s built-in Android controller and native Terminal SDK. The ordinary card rental flow does not require a separate cashier phone. Payments are processed in the operator’s own local Stripe account; CoreCharge links the payment to rental orders, release, return and the configured billing rules.
Stripe’s Italy guidance specifies EUR, an appropriate Italian account and local reader Locations. It also distinguishes co-branded Pago Bancomat cards processed over their supported co-brand rails. The operator should test the cards relevant to its customers without advertising acceptance of every local payment network.
Design return access before publishing “return anywhere”
“Return anywhere” should mean anywhere within a defined, tested network. It should not suggest that a guest can return to another operator’s cabinet or an unrelated country. Specify participating stations, actual access hours and a support route for a failed return. When cross-station return is part of the project, include it in the acceptance scope.
| Planning question | Record for each venue | Operational consequence |
|---|---|---|
| When can a guest enter? | Guest-facing access hours and seasonal closures | Return guidance must reflect actual access |
| Will guests arrive or depart here? | Likely borrow and return direction | Plan battery and empty-slot availability |
| Who checks the station? | Named venue contact and operator backup | Exceptions have a first responder |
| Can inventory be moved? | Permitted maintenance route and service window | Rebalancing becomes practical |
| What happens at closure? | Alternative return point and published contact | Guests receive a usable next step |
Run an illustrative two-venue pilot
Imagine a hotel reception and a nearby restaurant joining the same approved network. A guest borrows at the hotel and returns after dinner. The trial should check the battery identity, the second cabinet’s ability to accept it, the original rental’s end time and the final financial result. Record both cabinet references with one rental reference so support can follow the journey.
Then reverse the direction. A network that works only when all batteries move one way can run short at the busy lending point and fill up at the receiving point. Early operating records help determine when staff need to move inventory. This is a planning example, not a claim about an existing Italian customer’s results.
Make the price understandable to a short-stay guest
Display the charging interval, any cap, applicable authorization or deposit approach and the non-return terms before payment. Provide Italian instructions and a suitable visitor-language option. Explain how the guest can identify the correct return location without assuming that they have installed an app or still have a working mobile connection.
If the configured payment method supports authorization followed by later capture, check the applicable capture conditions against the maximum intended rental duration. A tariff setting cannot extend a bank authorization or guarantee a later non-return charge. Align the commercial terms with the verified financial flow before opening.
Prepare venue staff for three practical situations
- A guest sees no free return slot: staff know the nearest usable alternative and support contact.
- A guest says the battery was returned but the order remains open: support checks the physical return event and matching order.
- A guest is leaving the area: staff provide the approved return options without promising an undocumented exception.
Reader suitability, equipment obligations and the proposed staffed or unattended environment need local review. CoreCharge’s technical integration provides a starting point for configuration and testing rather than a blanket approval for every tourism site.
Explore the CoreCharge physical reader solution or request an Italian pilot and return-network review. Bring a short venue list with access hours; it often reveals the most important deployment choices before hardware is shipped.
Official references
Technical references checked on 16 October 2026. This is an implementation guide, not a report of a completed deployment in every market.