Does a WisePad 3 rental station need a shop assistant’s phone beside it? In CoreCharge’s compatible POS-ready cabinet design, the Android controller is already inside the station. It runs the rental application and native Stripe Terminal SDK. The physical reader handles the card interaction, while the cabinet application coordinates what the guest sees and what the equipment does.
This distinction matters when comparing equipment offers in Australia. A reader attached to a case is only one component. The project also needs a reliable data connection, the correct Android environment, a configured payment service, cabinet-control integration and a tested rental policy. Buying those items separately without an architecture plan can leave the operator with a terminal that accepts cards but cannot complete a rental.
Four responsibilities behind one customer action
| Component | Job | What acceptance should prove |
|---|---|---|
| WisePad 3 | Collect the supported card or wallet interaction | The actual local reader connects and completes the expected prompts |
| Cabinet Android application | Run the customer interface and native Terminal SDK | Reader events and rental messages agree |
| Payment service | Create payment sessions and handle authorized financial operations | Payments belong to the correct operator and environment |
| Cabinet control and rental platform | Link orders, release commands, returns and charging rules | A real battery journey matches the recorded rental |
Stripe documents WisePad 3 as an SDK-connected reader, with USB available for Android. CoreCharge’s standard technical integration uses that native route in a compatible cabinet. This does not make every Android board or every third-party enclosure compatible; the supplied controller, application, mount and cable must be confirmed for the actual order.
The cable is part of the system
A cable that charges a reader is not necessarily a working data cable. During assembly, verify the data path, connector fit, cable routing and power arrangement. The reader should be usable without strain on its connector and without blocking the customer’s access. Document how service staff can inspect the connection safely.
A useful handover pack includes cabinet and reader serial numbers, the agreed connection method, application version and photographs of the supplied mounting arrangement. If a replacement part is needed later, the operator can identify what was installed instead of reconstructing the configuration through messages.
Keep Australian payment rules in the design
The Australian regional guidance requires the appropriate Australian account, local Location and AUD for Terminal transactions. It also describes eftpos-specific capture behavior. The rental policy must therefore follow the actual payment network and result; a credit-card authorization example should not be copied blindly to every Australian debit transaction.
Rental money is processed in the customer’s own local Stripe account. CoreCharge configures the agreed integration and links financial events with rentals. Account ownership and settlement control stay with the operator. Production access should use a controlled authorization process; account passwords and full secret keys do not belong in cabinet software or routine support chats.
Test the boundaries between components
Start with a normal rental, then challenge each connection deliberately under controlled conditions. Cancel before completing payment. Try a declined test transaction. Interrupt connectivity at an agreed test point. Reconnect a reader during maintenance and verify its state before reopening. The goal is to discover how the configured system behaves, not to assume every interrupted transaction resumes automatically.
For each test, record the customer message, payment state, rental state and physical battery result. A green payment indicator and a release command are different facts. The acceptance record should show whether the cabinet actually reported a release and whether the correct rental was created. When a result is uncertain, reconcile it before another charge or release attempt.
A practical opening checklist
- Confirm the Australian operator account, operating Location and agreed reader procurement route.
- Match the cabinet controller and Android application to the supplied reader and data connection.
- Approve the tariff and the payment-method-specific financial flow.
- Complete a controlled rental, return and financial reconciliation on the actual configuration.
- Assign venue support and a maintenance procedure before making the equipment available.
Network coverage, placement and suitability for the intended staffed or unattended setting require project-specific confirmation. An optional H5 route can supplement the reader journey, but it is not a substitute for testing the physical installation.
Review CoreCharge’s reader-ready solution or request an Australian cabinet configuration review. Share the intended venue and quantity so the hardware and operational checks can be agreed together.
Official references
Technical references checked on 16 October 2026. This is an implementation guide, not a report of a completed deployment in every market.