A rental marketplace does not just take one card payment. A weekend e-bike booking might collect money from a renter, hold it until pickup, keep a platform fee, and pay the host who owns the bike. Scooter fleets add another payout path.
Can one processor cover that without you becoming a bank?
Stripe Connect is built for that split. The platform stays the software layer. Hosts and operators become connected accounts, and Stripe moves the funds while running a large share of identity and payout checks.
Turns out the old account labels are gone. Standard, Express, and Custom still appear in older tutorials, but the current model is one Account object with roles you attach as needed.
Account roles that map to rental work
The Accounts v2 API treats every host, contractor, or even a paying rider as the same kind of Account. You add configurations for what that person is allowed to do.
- Merchant lets the account accept payments. It carries
card_paymentsandstripe_balance.payouts, so an e-bike host can take a booking and later receive a payout. - Customer lets the same Account pay the platform. You don't keep a separate Customer record for a rider who also lists a scooter.
- Recipient lets the account receive transfers. Independent chargers, parking hosts, or tour guides often need this for indirect charges.
Dashboard access is a separate switch: full, express, or none. A shop that already runs storefront rentals may want full. A peer-to-peer scooter listing usually works better with express, where you collect bank and ID details and the host sees a lighter Stripe surface.
You create the Account at /v2/core/accounts. Pass configuration, identity, and defaults.responsibilities (who takes fees, who eats losses) instead of a frozen account type.
Which configuration fits a bike or scooter marketplace
Pick the mix from the work, not from a blog's default.
| Configuration | What it enables on a rental platform | Typical dashboard | Best for | Who manages KYC |
|---|---|---|---|---|
| Merchant | Accepts booking payments and can be paid out | full for self-serve shops, express for hosted listings |
E-bike hosts, scooter depots, tour operators | Seller if full; platform if express or none |
| Customer | Pays the platform from the same Account | Not applicable | Riders who also subscribe, or hosts who buy add-ons | Platform |
| Recipient | Receives transfers after an indirect charge | Not applicable | Battery swappers, chargers, relocation contractors | Platform, via transfer_data.destination |
Most peer-to-peer bike marketplaces combine Merchant and Recipient on the host Account. The renter stays a Customer-configured Account if you want one ID for both riding and listing.
dashboard: full gives hosts more autonomy. dashboard: express keeps onboarding short and the platform in control. Apps that feel like ride-share almost always pick express for that reason.
When Connect is the wrong tool
If you only rent your own fleet and never pay a third party, a regular Stripe account is enough. Connect starts to matter once hosts, contractors, or partner depots need their own payouts.
How a booking actually moves money
Connect offers three charge patterns, and the rental timeline should pick among them. Direct charges put the connected account on the receipt, which can fit a branded bike shop that wants its name on the statement, but that model breaks down if one cart includes scooters from two owners. Destination charges are the usual path for a single-host booking: the platform charges the renter, then sends the host share with transfer_data.destination, and your application fee comes out in the same flow. When a group ride pulls bikes from three hosts, or you need to pay a host and a delivery contractor from one checkout, separate charges and transfers are the extra-API-call option.
Thing is, unverified hosts shouldn't receive live payouts. Deferred onboarding lets you create the charge and hold funds on the platform. After KYC clears, you switch to destination charges pointed at the Recipient-configured Account. Stripe's marketplace docs walk through that verified versus unverified path.
Hold windows should match the rental. Capture when the rider unlocks, or after a short damage window, if your terms allow it. Test refunds and disputes in sandbox before the first weekend rush. Confirm delayed-capture rules for your country before you promise hosts a hold you can't keep.
Onboard hosts without a 15-minute wall
Paper KYC before the first listing kills conversion. Some operator writeups still quote 10 to 15 minutes for a traditional compliance form. Stripe shortens that with Account Links: single-use URLs, optional prefills, and a dashboard setting that decides how much the host types themselves. The mechanics live in the Connect accounts docs.
A practical flow for an e-bike listing looks like this:
- Create the Account with Merchant (and Recipient if you pay by transfer),
dashboard: express, and your fee and loss responsibilities. - Prefill legal name, business type, and bank details you already collected on the listing form.
- Send an Account Link so the host finishes identity checks in Stripe's hosted or embedded UI.
- Let the listing go live in a limited state if you use deferred onboarding, with funds held on the platform.
- On verification, enable destination charges and show a payout-ready status in the host dashboard.
- Nudge people who start and stall, because marketplace builders often see 40-60% drop-off on unfinished onboarding, and a reminder email is cheaper than lost listings.
Accounts with dashboard: full let shops manage their own KYC. That's closer to the old Standard model. It launches slower. It fits established rental stores better than a one-bike host.
New connected accounts often wait on the first payout. Guides aimed at platforms mention a 7-14 day hold as a Stripe risk control. Tell hosts about that delay before a Friday booking turns into a Monday ticket.
What the fees look like on rental volume
Don't budget from the headline rate alone.
US domestic cards are widely quoted at 2.9% + $0.30 per successful charge. That's the number most US bike bookings will hit. Rates still change with region, wallet, and volume. Confirm the live schedule in your Stripe Dashboard rather than treating a blog figure as a contract.
Connect adds payout cost on top. Secondary fee roundups describe about 0.25% per connected-account payout, sometimes with a cap around $25, and a separate per-payout component on Express-style setups. Instant payout, if you offer it as a host perk, is often passed through at about 1.5%. Cross-border transfers can add roughly 0.5% to 2%. Paying out in a different currency than the charge typically adds an FX markup around 1% above mid-market.
To be honest, the platform commission is where operators get surprised, because if you take $15 on a $50 e-bike day and Stripe still bills processing on the full $50, processing as a share of your own revenue looks ugly fast and founders only notice after month three. Some shops absorb Stripe. Some pass card cost to the renter where surcharging rules allow it. US card surcharging is legal in most states with a 4% cap and required disclosure, illegal in a handful, and treated differently under EU rules. Check the state. Don't copy a national blog.
Instant payout can be a paid host feature. That's one Connect line item that can become revenue instead of pure cost.
1099s and other US tax paperwork
If you pay US hosts, you're in information-return territory. Stripe's marketplace documentation describes gross-earnings tracking and 1099 support. Stripe Tax Reporting is commonly used to collect a TIN or SSN during onboarding and to produce 1099-K forms.
Federal 1099-K rules moved again. The One Big Beautiful Bill Act restored the older federal threshold of more than $20,000 and more than 200 transactions, reversing the planned $600 path, as Avalara's summary of that change lays out. That's federal guidance, not a pass for every state. A few states still run lower 1099-K thresholds. Service-style payouts, such as a contractor relocating scooters or a mechanic you pay directly, may need 1099-NEC or 1099-MISC instead of, or besides, 1099-K. Ask a tax advisor for the mix you actually pay.
Hosts will ask why a form arrived. Have a short explainer ready. The form reports what the marketplace paid. It's not a tax bill by itself.
Test the money path before you onboard shops
You don't need a live fleet to prove this.
Create two sandbox connected accounts: one Merchant plus Recipient host, one Customer renter. Run a destination charge for a single-bike booking, then a split that pays a host and a fake charger. Refund one payment. Dispute another. Fail a payout on purpose. The end-to-end marketplace guide is the map, and the Accounts v2 reference is where the configuration fields live.
If the sandbox split matches your rental contract, wire Account Links into host signup. If it doesn't, change the contract or the charge type before real shops arrive.