A reader-ready cabinet should arrive with a defined installation plan, not a loose terminal and a promise to configure it later. For a US shared power-bank project, the practical questions include how the M2 is mounted, how it communicates with the cabinet, which account receives the rental payments, and what evidence establishes that the supplied station is ready to open.

This guide focuses on delivery and acceptance. CoreCharge’s US M2 and H5 overview introduces the broader payment routes. Here the main route is the physical M2 reader working with a compatible POS-ready cabinet, its built-in Android controller and native Stripe Terminal SDK. A separate cashier phone is not required for the ordinary integrated rental flow.

Lock the US configuration before shipment

Stripe’s US regional guide lists Reader M2 for the United States and requires USD Terminal payments with the appropriate US account and Location. WisePad 3 should not be substituted from a European proposal. The operator normally purchases and registers its M2 through its own local Stripe account, with the cabinet structure and integration scope confirmed separately.

CoreCharge’s M2 technical route includes successful real card-payment integration work alongside existing rental modules. Each delivered unit still needs its own configuration and acceptance. That evidence should not be represented as proof that every US venue has already completed the same end-to-end test or that every unattended placement is approved.

A delivery record for each station

Item Confirm before dispatch Confirm after installation
Cabinet identity Model, serial number and agreed battery inventory Correct operator and venue in the dashboard
M2 installation Agreed mount, connector access and cable route Reader accessible without connector strain
Android connection Application version and supported data path Reader connects through the installed application
Power and network Included adapter, plug and connectivity scope Stable operation at the actual location
Stripe setup Account authorization and mode documented securely Correct live account, Location and payment result
Customer journey Approved tariff and interface content Card prompts, release, return and help route checked

Inspect the mechanical and data connection together

Stripe documents M2 as an SDK-connected reader with Bluetooth and Android USB options. Use the connection method agreed for the cabinet rather than assuming a charging cable also carries data. Inspect the installed cable, service access and reader position before making the equipment available.

Record photographs of the actual supplied cabinet and mounting parts. A generic factory photograph cannot establish that the correct hardware was packed. The delivery list should also state which components the operator buys locally, which the cabinet supplier includes and which replacement parts require a separate arrangement.

The cabinet screen must explain the card interaction

M2 does not have its own full customer display. Stripe’s payment guidance requires the application to present reader events and instructions. In a rental cabinet, that makes the Android interface important: it must tell the guest when to present a card, how to respond to a retry request, and what happened next.

Review those messages at the actual installed height and lighting. Avoid a screen that announces a completed rental when only payment authorization has been confirmed. A guest should know which battery to remove, where to return it and how to contact support if no battery is released.

Accept the delivered system with a controlled rental

First complete the agreed pre-production tests. Then arrange a controlled real-environment card transaction on the intended US account. Follow the battery from release through return and compare the final rental amount with the payment record. Retain the redacted order reference, reader identity, cabinet serial number and observed result.

Also rehearse a cancellation and an uncertain outcome, such as a payment result without confirmed release. Staff should check the original transaction before creating another charge or sending another release command. For authorization-based rentals, validate capture conditions and expiry handling rather than assuming a permanent hold or guaranteed future non-return collection.

Hand over responsibilities before opening

The operator owns its local Stripe account and receives rental funds there. CoreCharge connects the agreed payment configuration with orders, cabinet events and the management platform. The venue and operator need a first-response process, maintenance access and an approved customer policy. Local equipment obligations and suitability of the proposed staffed or unattended setting remain separate project checks.

Review the CoreCharge physical reader solution or request a US M2 delivery checklist. A cabinet quantity, venue type and intended reader procurement plan are enough to begin defining a concrete acceptance scope.

Official references

Technical references checked on 16 October 2026. This is an implementation guide, not a report of a completed deployment in every market.