There's no gravel-specific payment rail hiding in processor manuals. Rental operators use ordinary card gateways, then let fleet software fire the charge when a lock opens.
Do you need a dedicated gravel checkout product? No. Match the processor to how many hourly hires you actually run. Hook it to the app. Prove refunds work before you pocket a real deposit.
Match tools to rental volume
A 10-hire pop-up and a 100-unlock trailhead should not share a checkout plan. Thing is, fees and hardware both follow that count, not the tire tread.
A pop-up gravel stand doing 10 to 50 hourly hires can live on a phone reader. High-volume app fleets, the ones clearing 100+ unlocks, need a gateway that posts on unlock and settles on return without a staffer at the rack. Staff still handle the odd exception.
| Daily gravel hires | Checkout that usually fits | Main limit |
|---|---|---|
| 10-50 walk-up hours | Mobile reader or phone tap | Quick start, awkward once bookings go fully in-app |
| 100+ app unlocks | Gateway tied to fleet software | More setup, cleaner micro-hires |
Those bands are planning aids, not a rule. One festival weekend can outgrow a reader.
Watch the fixed fee on short gravel hires
U.S. card-not-present menus usually mix a percentage with a small fixed fee. Public Stripe-style pricing often reads 2.9% plus $0.30 on a domestic online card. Other processors sit nearby. PayPal publishes separate U.S. business rates by product, so don't copy one brand's number onto another.
A $12 gravel hour at 2.9% plus $0.30 costs about $0.65 to process. That's over 5% of the hire, before any refund. The same schedule on an $80 day rental lands closer to 3.3%. Short trail hours pay those 30 cents again and again.
Last month's tickets won't match a homepage fee table. If you line up the actual 15-minute top-ups mixed with half-day gravel loops and those deposits you authorized then never captured because the bike came back fine, the blended rate jumps around in a way a homepage fee table never shows.
International cards and currency conversion stack on the same charge, and refunds often leave the original processing cost with you. High returns lift the real rate. Skip mobility-blog averages. Open each processor's current pricing page and run your average ticket through it.
Connect a gateway to fleet software
The gateway sits between your bank and the card a rider saved in the app. Fleet platforms such as greenmoov.app call that gateway when a booking starts or a lock opens. Confirm supported processors in the operator help center before you sign a merchant account you can't attach.
- Choose a processor with a documented API and a sandbox. Stripe and PayPal are common examples, not a ranked pair.
- Open the merchant dashboard and copy the publishable and secret keys.
- Paste the keys into your fleet software's payments fields, or ask the vendor the exact label they expect.
- Map unlock to an authorization or capture. Map a clean return to a refund or a voided hold.
Custom mapping helps when you hold a damage deposit on bikes that leave the lot. Pre-built connectors save calendar days. You'll still decide that "GPS says returned" means "release the hold."
Gravel bikes don't need special readers
No gravel-only payment hardware shows up in processor or lock-vendor docs. Use the same app wallet or mobile reader you'd use for any bike rental, and keep the lock and GPS stack you already run.
Design holds, unlocks, and refunds
Sandbox first. Always.
Run a fake $10 unlock, a partial capture, a full refund, and a declined card before a real gravel bike leaves the rack. Have the rider add a card on first login. Place an authorization, not a capture, if you want a deposit sitting in reserve. A 20% hold is your policy, not a card-network rule.
Turns out most failed rentals aren't the gateway. They're a lock that opened on an auth that later dropped, or a refund that posted while the bike was still out. Put velocity limits on very short hires so one card can't spray unlocks (the quiet first week is exactly when people skip this, and it's a bad time to skip it). Watch disputes in the processor dashboard. Tokenization keeps raw card numbers off your disks, which is why you use a gateway instead of a swipe box wired to a spreadsheet.
If your gateway offers 3-D Secure, use it on remote app checkouts, knowing some claims will still land. PCI still applies to you as the merchant, even with tokenization. The PCI Security Standards Council merchant resources explain which self-assessment matches how you take cards.
Time-box damage holds so a clean return releases the rider's bank hold. Capture extra only after you have a reason, not because the gravel loop left pavement.
Taxes and local rental reporting
Bicycle rental tax follows the state, sometimes the city. Check the revenue department where the bikes actually leave. Multi-state fleets need a location-by-location answer, not one national rate.
- Ask the state (and city, if they levy a local tax) whether bicycle rentals are taxable, then enable tax in the gateway only if that tool can remit or report what you need.
- If you operate in more than one state, confirm collection rules in each place you hand out bikes. A payment dashboard is not your tax return.
Launch checks before live charges
Work through this before you swap sandbox keys for production keys:
- Confirm your fleet tool, including greenmoov.app if that's what you run, lists the gateway you just signed.
- Read the processor's live terms for volume tiers, international cards, and whether refunds return the processing fee.
- Complete 10 end-to-end sandbox rentals: save card, hold, unlock, return, refund.
- After production keys, run one real $1 charge and an immediate refund.
- Store insurance proof with that bike's payment record.
- Write down who files the sales tax return, you or the gateway.
FAQ
What do operators usually pay per gravel hire?
There's no gravel rate. U.S. online cards often price as a percent plus a fixed fee, so a cheap hourly hire carries a higher effective rate than a full-day rental. Check the processor's current page.
How do I keep short-hire fees from eating the ticket?
Lift the minimum paid time, or sell half-day packages so the fixed fee sits on a larger ticket. Shop processors on the fixed cents, not just the headline percent.
Where do I find greenmoov.app payment settings?
Use the operator help center and the payments area of the dashboard. Supported gateways are listed there; don't assume every processor you like will already be wired in.
Pull last month's hire amounts into a spreadsheet and run them through one processor's public calculator. Finish those 10 sandbox rentals in the fleet app next. To be honest, that calculator hour saves more money than swapping brands after you're live.