A customer should not have to solve a translation problem while borrowing a power bank. In a French hotel lobby or café, the cabinet may explain rental pricing in one language while the card reader asks for a different action. The transaction can be technically valid and still feel uncertain. A useful localization plan follows the guest all the way from the first screen to a confirmed return.
For a compatible CoreCharge POS-ready cabinet, the French reader configuration uses WisePad 3 connected to the built-in Android application through the native Stripe Terminal SDK. The customer uses the physical reader at the cabinet; an extra phone or tablet is not the normal cashier device. Payments go into the operator’s own local Stripe account, while CoreCharge connects payments to rental orders and cabinet events.
Check the French payment setup first
Stripe’s France regional documentation supports WisePad 3 and EUR Terminal payments through the appropriate French account setup. It also describes Cartes Bancaires eligibility and routing for co-badged cards. Operators should confirm their account readiness and supported integration rather than treating every French debit card as an identical international credit-card transaction.
Choose the reader through the operator’s local Stripe account and confirm the current software and account requirements during integration. Agreement on a reader model establishes a technical route; the particular venue, customer access and unattended-use conditions need their own review. This article describes a deployment method, not a claim that every French venue has already been accepted.
Review every surface the guest will encounter
| Customer moment | What to check | Acceptance question |
|---|---|---|
| Before presenting a card | French price, authorization explanation and return terms | Can a new guest understand the potential amount? |
| At the reader | Reader language, tap or insert guidance and PIN access | Can the guest complete the requested action? |
| When a battery releases | Clear slot indication and instruction to remove the battery | Does the screen describe what actually happened? |
| During the rental | Approved return locations and their opening hours | Can the guest find an available return point? |
| After return | Confirmation, charge explanation and help route | Can support locate the rental without requesting full card data? |
Translate decisions, not just button labels
“Continue” is easy to translate; an authorization explanation needs more care. If the configured payment method supports a hold followed by later capture, the guest needs to understand the difference between that temporary amount and the final rental charge. If a different payment flow is used, the wording must follow that actual flow. A generic “deposit refunded instantly” promise can create unnecessary complaints.
Write one approved French master version for the tariff and its exceptions. Record how free time, charging intervals, caps and non-return rules interact. Keep this master alongside the configured rules so a later commercial change does not leave an old explanation on a screen. An English option may be useful for visitors, but it should communicate the same policy.
Keep the reader and cabinet messages consistent
The payment terminal controls its payment prompts; the cabinet application controls the rental explanation and equipment guidance. Changing a cabinet screen does not automatically change every reader message or receipt. Assign a reviewer to each surface and test them together with the actual reader.
A guest may pause to select a card network or complete authentication. The cabinet should not imply that payment has failed simply because the reader is waiting for action. Conversely, a completed reader interaction should not be described as a completed rental until the relevant release result has been checked. The support team needs wording for both cases.
Rehearse an exception before the first guest arrives
Use an illustrative hotel test: cancel before payment, finish a normal rental, and investigate a payment with no confirmed release. Photograph the placement and record the redacted order and payment references. Confirm who can approve a refund, how the original status is verified, and what the front desk should tell the guest while the technical team investigates.
The same exercise should cover a return near venue closing time. If the guest cannot enter the lobby, good translation will not solve the access problem. Publish realistic return guidance and give venue staff an escalation route. Localization includes the operating conditions behind the words.
CoreCharge’s role is to connect the local payment setup with the rental workflow and operator dashboard, then help the operator validate the configured experience. See the physical reader solution or request a French screen and acceptance review. A venue description and sample tariff are useful starting materials.
Official references
Technical references checked on 16 October 2026. This is an implementation guide, not a report of a completed deployment in every market.