A Polish power-bank operator needs more than a price on the cabinet. The public tariff, rental calculation and card-payment design must describe the same business rule. If the screen promises one amount while the payment holds or captures another, even a technically successful transaction can become a customer complaint.
CoreCharge’s matched reader-ready route uses WisePad 3 with a native Android application running on the internal cabinet controller. Stripe processes payments through the operator’s own local account. CoreCharge connects the payment result to the order, release, return, billing and operating records. This guide focuses on how to prepare the PLN tariff around that workflow.
Set the currency before discussing the numbers
Stripe’s Poland Terminal guidance lists WisePad 3 support and requires Polish złoty transactions with a Polish receiving account. Register the reader to the correct Polish Location. Check that the cabinet display, rental configuration and payment request all use PLN rather than copying a euro demonstration unchanged.
Choose the customer-facing format deliberately. Display a clear currency label and use consistent rounding in examples, tariff descriptions and final receipts. Polish-language customer content needs review independently of the reader language setting, including the explanation of a temporary hold and any non-return charge.
Write the commercial rule as a plain-language example
An illustrative test tariff might contain a 30 PLN temporary authorization and 3 PLN for an initial rental period. These are sample values, not a CoreCharge price recommendation. Before implementation, specify when charging begins, how a period is rounded, whether a daily cap applies and what happens when the bank is never returned.
Then ask whether the selected payment method can support the complete rule. A 15 PLN authorization is not automatically permission or technical capacity to collect a later 99 PLN non-return amount. Saving a payment method, obtaining appropriate consent and attempting a later charge are separate design questions; later collection must never be described as guaranteed.
Use a boundary test sheet
| Test case | Tariff question | Evidence required |
|---|---|---|
| Return just before a charging boundary | Which period is billed? | Order timestamps and final PLN calculation. |
| Return just after the boundary | Does rounding match the published rule? | The same explanation in interface and order record. |
| Reach a daily cap | Is the cap applied to the intended period? | A controlled test using the agreed configuration. |
| Cancel before dispensing | Should any rent exist? | Cancelled order and appropriate payment outcome. |
| Authorization approaches expiry | What action is permitted before it expires? | Actual payment validity and agreed exception handling. |
| Bank remains unreturned | What is the supported collection route? | Terms, payment design and tested outcome kept distinct. |
Treat authorization time as a real operating constraint
An authorization is not an indefinite deposit held for any future event. Stripe exposes an actual capture deadline, and extended authorizations depend on eligibility and card conditions. Do not assume a power-bank business has a thirty-day hold simply because another rental industry may qualify.
The operator and integration team should verify how the configured rental duration fits the permitted payment window. If the commercial policy can continue beyond it, design and test the exception. The backend tariff cannot create payment-network authority that the transaction does not have.
Test the reader and the cabinet as separate evidence
At the first site, confirm successful reading, order creation and actual release of an identified bank. Complete a return and reconcile the final payment. Also check a decline and a customer cancellation. A reader approval screenshot alone does not prove that stock changed or rental time stopped correctly.
Keep a small acceptance pack with the station identifier, reader registration, account environment, tariff version and redacted payment references. If the price later changes, retain the previous terms associated with earlier orders. Ask which rule applies to a rental already in progress rather than assuming that a new setting should rewrite its history.
Make the venue explanation short and accurate
Venue staff need to describe the temporary authorization, actual rent and support route in everyday language. They should not promise an immediate statement update or manually charge a disputed amount without the operator’s process. Rental payments enter the operator’s Stripe account, while processing fees and payout timing remain separate.
Review CoreCharge’s reader-ready station approach, then send your Polish venue plan and proposed PLN tariff. CoreCharge can help turn it into a matched cabinet and test matrix. Reader suitability, installation conditions, receipts, local terms and any unattended use must still be confirmed for the actual project.
References and implementation scope
Technical references checked on 16 October 2026. Equipment and payment settings are confirmed for each deployment.