A venue asks for “access to the revenue.” That can mean three different things: permission to view rental activity, agreement on a share of commercial proceeds, or the right to receive a payment. Treating them as one setting creates confusion before a partnership even begins.
For a proposed Lithuanian power-bank pilot, prepare an operating annex alongside the venue arrangement. It should identify who can see which records, how an agreed venue amount is calculated and who makes the eventual payment. The annex is an operational discussion document; have the final commercial and legal terms reviewed appropriately.
First confirm the payment route is available to the account
As checked on 17 October 2026, Stripe’s Lithuania section describes Terminal as Private preview. The operator must obtain confirmed preview access for the intended account and Lithuanian market before reader procurement or public launch. A supported-reader listing does not establish that every account can activate the service.
The proposed setup uses an eligible Lithuanian account, local Terminal Location and EUR. The operator normally purchases and registers its WisePad 3 through its own account. The deployment’s staffed or unattended conditions still require confirmation; a technically integrated reader does not approve an entire operating model.
Write the annex around separate decisions
| Decision | Question to settle | Practical annex entry |
|---|---|---|
| Data visibility | Which venue records should each person see? | Named account role, allowed scope and access owner |
| Customer service | Who handles a guest’s first complaint? | Venue first response and operator escalation contact |
| Commercial calculation | What is the agreed basis for the venue amount? | Defined period, included transactions and treatment of adjustments |
| Statement approval | Who checks and accepts the figures? | Reviewer, evidence required and discrepancy process |
| Actual payment | Who pays whom, and through which agreed route? | Payer, recipient and payment confirmation record |
| Ending the arrangement | What happens to access and unresolved rentals? | Asset handover, access review and named follow-up owner |
Describe the platform’s role precisely
CoreCharge links orders, device state, dispensing, return, pricing and the operating dashboard. Available operational records and Excel exports can support the agreed review. Decide which role and access scope are suitable, then test them with a venue user. Do not promise unrestricted financial access merely because the partner hosts a cabinet.
Stripe processes rental payments into the operator’s own account. A dashboard revenue figure or a commercial venue share is not an automatic Stripe split payout. The parties should agree the calculation and actual payment process separately. Review the project responsibility map when assigning these owners.
Test a statement with exceptions
Build a small illustrative statement from controlled or suitably redacted records. Include a completed rental, an adjustment and an unresolved item. Ask the venue reviewer to identify the period and understand why each item is included or excluded. Do not use a single gross-revenue screenshot as proof of the final payable amount.
Record the agreed handling of refunds, disputes and corrections without inventing a universal commercial policy. Stripe fees and bank payout timing are separate from the rental total and the venue’s contractual entitlement. The daily reconciliation guide provides a foundation for matching the source records.
Hand over the station and the relationship
In the matched reader-ready cabinet, the native Android application and Terminal SDK run on the internal controller. WisePad 3 is the physical card reader; the ordinary flow does not require an external cashier phone. Confirm the supplied mount, cable and configuration, then complete a controlled payment, release and return before venue acceptance.
At the same handover, test the venue user’s permissions and support route. Access should reflect the agreed role, and payment authority should remain explicit. Review the CoreCharge reader solution or request a Lithuanian pilot responsibility worksheet. Account preview status, venue count and the proposed commercial model are useful starting inputs.
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.