Who owns the Stripe account and controls payouts?

The operator applies for, owns and manages the Stripe account and its linked bank account. Stripe controls account approval, payment processing and payout availability under its terms.

What does CoreCharge provide in this model?

CoreCharge provides the agreed station and power bank hardware, SaaS rental workflow, payment-status integration, rental rules, station control, operator dashboard, reporting and technical support.

Is this route available in every country?

No. Stripe account eligibility, Terminal availability, supported readers, wallet methods, fees, payout timing and local compliance requirements must be confirmed for the target market before ordering and launch.

CoreCharge Cloud + your Stripe account English only

Your rental revenue goes to your own Stripe account.

Your customers pay through your eligible local Stripe account. CoreCharge Cloud connects the payment status to rental rules, station control, orders and reporting, without collecting, holding or settling your rental revenue.

Review 8-slot and 12-slot POS stations Discuss My POS Setup

For operators in Stripe-supported, card-led markets. Account approval, reader availability and live payment compatibility remain subject to market-specific confirmation.

Direct settlement model End userpays Your Stripe accountprocesses and receives Your business bank accountreceives Stripe payouts CoreCharge remains the technology and device operations layer.

The direct answer

Your account. Your payouts. Our technology.

Account ownershipYou own and manage the Stripe account.

You complete merchant onboarding, KYC and bank-account setup directly with Stripe.

Rental revenueStripe processes funds for your business.

Rental payments enter your Stripe balance and follow the payout settings and eligibility of your account.

CoreCharge roleWe connect payment status to device operations.

CoreCharge does not become the merchant of record and does not receive the operator's rental revenue.

Funds and operating data

The money path stays separate from the CoreCharge operating layer.

Solid arrows show the customer payment and Stripe payout path. Dashed lines show status, rental rules, station commands and operating data.

Diagram showing an end user paying into the operator's own Stripe account, Stripe paying out to the operator's bank account, and CoreCharge providing rental workflow and station control without holding funds — Open the diagram to view the full-size 3200 x 1800 source.

Transaction and device flow

From tap to return in five connected steps.

1
Customer starts the rental
The renter uses a supported card or confirmed contactless wallet at the configured reader.
2
Stripe processes the authorization
The payment or pre-authorization is created in the operator's own Stripe account.
3
CoreCharge runs the rental workflow
The SaaS receives the required status, creates the rental order and sends the reviewed release command to the station.
4
Return determines the final amount
After return, the configured rental rule completes the final charge or releases the unused authorization amount, subject to the approved payment design.
5
Stripe pays out to the operator
Net proceeds remain in the operator's Stripe balance and are paid to its linked bank account according to Stripe's rules.

Responsibility map

Who owns each part of the operating chain?

Party	Primary responsibility	Rental-fund position
End user	Starts, pays for and completes the rental.	Does not hold operator revenue.
Stripe	Payment authorization, processing, payment status and payout to the operator's bank account.	Processes funds as the payment service provider under its terms.
Operator	Owns the Stripe account, sets rental rules, operates venues and handles account-level refunds, disputes and reconciliation.	Owns the rental revenue in its Stripe account.
CoreCharge Cloud	Orders, rental rules, payment-status integration, station control, returns, dashboards and agreed technical support.	Does not collect, hold or settle rental revenue.
Rental station	Releases and receives power banks according to reviewed SaaS commands.	Does not hold funds.

Current overseas SaaS pilot policy

Buy the hardware. Keep the rental revenue.

The customer purchases and owns the agreed hardware. CoreCharge does not take a percentage of POS rental revenue.

1-50 active devicesUSD 0CoreCharge SaaS fee under the current pilot policy

51+ active devicesUSD 1per active device per month

Stripe reader costs, processing fees, refunds, disputes, bank charges, foreign exchange and additional services are separate. Final device counting, included services and commercial terms are confirmed in writing before launch.

Customer responsibilities

Own the merchant and settlement relationship.

Open and verify an eligible local Stripe merchant account.
Purchase, register and manage a supported local Stripe Terminal reader.
Own pricing, refund, dispute, payout and reconciliation decisions.
Provide only the minimum required identifiers or restricted credentials through an agreed secure channel.

CoreCharge responsibilities

Connect the reviewed payment and rental workflow.

Supply the agreed station and power bank hardware.
Configure the SaaS, station identity and reviewed Stripe Terminal route.
Support authorization, release, return, final-charge and refund-flow UAT.
Provide device, order and operating records within the agreed software scope.

Before ordering or launch

Four checks cannot be skipped.

Market eligibility

Confirm Stripe account availability, merchant category acceptance and local legal requirements.

Reader compatibility

Confirm the locally available reader, station enclosure, cables, firmware and network path.

Live UAT

Test authorization, failed payment, release, return, final charge, refund and unreturned-rental scenarios.

Operating ownership

Assign payout review, disputes, support, device replenishment and reconciliation to named operator roles.

Important limits

What this model does not promise.

No payment method can be guaranteed never to fail; outcomes depend on Stripe, issuing banks, cards or wallets, network conditions and risk controls.
A pre-authorization design should not be described as risk-free or as a guarantee of later collection. The amount and capture rules must cover the agreed unreturned-rental risk.
This SaaS route is not source-code delivery, private deployment or automatic support for any third-party terminal.
Stripe country eligibility, readers, wallet methods, fees, payout timing and compliance requirements must be rechecked before final quotation and launch.
This page describes an integration route and does not imply an official Stripe partnership, guarantee account approval or confirm live settlement in a particular market.

Does CoreCharge receive the operator's rental revenue?

No. Rental payments are processed in the operator's own eligible Stripe account. CoreCharge does not collect, hold or settle the operator's rental revenue.

Who controls Stripe payouts?

The operator manages the Stripe account and linked bank account. Stripe determines approval and payout availability under its own terms.

Does a customer need a phone or tablet at the station?

The intended reviewed configuration allows normal renters to pay at the station without an extra phone or tablet acting as the merchant terminal. The exact reader and station configuration must be confirmed before ordering.

Can CoreCharge guarantee Stripe support in my country?

No. Account eligibility, Terminal availability, reader models, wallet methods and compliance requirements are market-specific and must be verified for each project.

Prepare a compatible POS pilot

Tell us your country, venue plan and preferred station size.

We will review the 8-slot or 12-slot station, local Stripe Terminal route, reader availability, rental rules and live UAT scope before an order.

Discuss My POS Setup Ask about country compatibility on WhatsApp