The most useful way to understand a Portuguese power-bank rental system is to follow one order. A guest presents a card at the station, takes a bank, uses it and returns it. Behind that simple journey, the reader, rental service, cabinet and payment processor must agree on what has happened.
This guide uses an illustrative hold-based order to explain that connection. It is a deployment model to validate, not a claim that every card or wallet has identical behaviour. The final tariff, authorization amount and payment methods must be agreed for the operator’s Portuguese Stripe account.
Before the guest arrives
Stripe lists WisePad 3 support in Portugal and requires euro Terminal transactions with an appropriately located receiving account. The reader belongs to a Portuguese Location. CoreCharge’s standard matched setup runs the native Android application on the cabinet’s internal controller, so a separate external phone is not required as the payment host.
The Portuguese operator controls its own local Stripe account. CoreCharge supplies the agreed reader-ready cabinet integration and connects orders, payment results, dispensing, return and rental calculation. Stripe handles the payment processing; it does not by itself know whether a power bank physically left or re-entered a slot.
One rental, six checkpoints
| Checkpoint | Illustrative event | What the operator verifies |
|---|---|---|
| 1. Customer consent | The guest reads the euro tariff and temporary authorization explanation. | Displayed conditions match the configured rental rule. |
| 2. Authorization | A supported card approves an illustrative EUR 20 hold. | The payment outcome is attached to the intended order. |
| 3. Dispensing | The station releases an available charged bank. | The actual bank and slot event match the order. |
| 4. Rental in progress | The guest carries the bank away. | The order remains active under the agreed tariff. |
| 5. Return | An eligible station recognizes the returned bank. | The correct order stops accruing rental time. |
| 6. Final payment | Illustrative EUR 3 rent is captured within the supported authorization. | The final amount matches the rental and the unused hold is released. |
The EUR 20 and EUR 3 figures are examples only. They are not a recommended price or a promise that a bank statement updates immediately. The authorization must remain valid and the payment method must support the selected flow. Final settlement to the operator’s bank follows Stripe’s own schedule.
The gaps between checkpoints are where support matters
Suppose a payment is authorized but the cabinet does not release a bank. The customer should not be told simply to tap again. First identify the rental and check payment, cabinet connection and the dispensing event. The agreed exception route should resolve the authorization appropriately and prevent duplicate active rentals.
A different problem occurs when the power bank is physically inserted but the return is not recognized. The operator needs the bank identity, return station and time, then must inspect the relevant order and device evidence. A photograph of a bank near a cabinet is useful context, but it does not replace a confirmed return event.
Be precise about Portuguese debit acceptance
Stripe’s regional guidance explains that co-branded Multibanco cards can be supported over their Visa or Mastercard rails. That does not mean this reader route automatically provides every domestic Multibanco service. Include representative local cards in the test plan and verify the actual network and payment behaviour.
If a payment method cannot follow the intended authorization-and-capture path, agree a separate supported approach before enabling it. A QR/H5 route may remain available as a supplementary channel where configured, but it should not conceal an untested physical-card journey.
Make cross-site return a written rule
A hotel and a nearby bar may appear to be a natural shared return network. Confirm that both stations are in the same agreed network, that the backend ownership is correct and that each has return capacity. Tell guests where return is accepted and when the venue is accessible. Do not imply that every charging station in Portugal accepts the same bank.
Run an actual two-station borrow-and-return test if that is part of the supply scope. Keep the payment reference connected to the original rental even when the bank is returned elsewhere. The commercial agreement should separately define how the participating venues are credited.
Turn the timeline into a launch checklist
Before public use, repeat the normal journey and the cancellation route, verify customer terms and receipt access, and confirm reader suitability for the intended operating environment. Keep a concise record that local staff can use when the first unusual order appears.
Explore the CoreCharge Stripe reader station solution and share your Portuguese venue and return-network plan. CoreCharge can help translate the six checkpoints into a matched cabinet configuration and acceptance test. That is the bridge between an approved tap and an operational rental business.
References and implementation scope
Technical references checked on 16 October 2026. Equipment and payment settings are confirmed for each deployment.