A visitor with a flat phone can present a physical card, but cannot conveniently scan a QR code and finish a browser checkout. Another guest may prefer the agreed H5 route on their own phone. Offering both routes can be useful, provided the operator knows what each one requires and what has actually been enabled.
For a Portuguese power-bank cabinet, prepare a route matrix instead of treating every payment symbol as interchangeable. The physical reader remains the primary route in this plan. H5 is a supplementary existing channel where included and configured for the project.
Describe the two customer hosts correctly
In CoreCharge’s matched WisePad 3 configuration, the native Android rental application and Terminal SDK run on the cabinet’s internal controller. The reader uses the agreed data and power connection. A separate staff phone is not needed as the normal payment host, and the guest does not need to start a browser journey to use the physical-card route.
An H5 journey uses the guest’s phone and browser, the approved rental page and the payment methods enabled for that online configuration. It has its own connectivity and customer-action requirements. Stripe’s online Checkout documentation describes an online payment product; it does not establish which methods CoreCharge has already integrated for a particular operator.
| Guest or site condition | Physical reader route | H5 route to verify |
|---|---|---|
| Guest’s phone is flat | Test supported physical-card rental at the cabinet | Do not assume the guest can open the page |
| Guest chooses a browser checkout | No need to start a second reader payment | Check approved page, tariff and enabled payment methods |
| Reader reports a problem | Investigate the original attempt before retrying | Use only if available and the original payment is reconciled |
| Guest asks about a local wallet | Confirm the actual supported reader interaction | Do not advertise a wallet without verified integration |
| Payment completes | Match its reference with the rental and release | Verify the same physical rental outcome through that route |
Keep availability claims narrower than a payment catalog
Stripe’s Portugal guidance lists WisePad 3 and EUR Terminal payments with the appropriate Portuguese account and local Location. It also describes supported co-branded Multibanco cards using their co-brand rails. That is not a blanket claim that the cabinet offers every Multibanco service.
Likewise, Stripe availability for MB WAY or another online method does not prove that it is enabled in this rental flow. Do not describe a new local-wallet or Tap to Pay integration as existing functionality without separate confirmation. A physical reader, phone-based Tap to Pay and a QR link to H5 are different technical routes.
Prevent a fallback from becoming a second payment
If a guest starts one route and then asks to use the other, identify the original order and payment state first. An unresolved reader authorization should not be left behind while the guest starts an unrelated browser payment. Define who can authorize a retry or alternative and how the two references are recorded when an incident spans both.
This is a proposed operating procedure, not a promise of automatic rerouting or automatic duplicate-payment detection across all channels. Use the Portuguese order timeline to preserve the link between payment and battery events. The authorization and refund guide helps classify any unfinished financial result.
Accept each enabled route on the supplied cabinet
Run a controlled borrowing and return through the reader, then separately test the agreed H5 journey. Check displayed prices, released battery, rental end and final payment result. Stripe processes funds into the operator’s own eligible account; CoreCharge connects orders, device events, returns and pricing. Verify account and domain configuration for the actual routes rather than assuming one demonstration covers both.
Confirm the installation’s intended staffing conditions and customer support route before opening. Explore the CoreCharge reader-ready station or request a Portuguese reader-and-H5 acceptance matrix with the methods you want to offer.
References and project scope
Technical references checked on 17 October 2026. The operating procedures above are planning guidance; hardware, account access and payment settings are confirmed for each deployment.