Getting paid

Your money goes to you

Client payments run through your own Stripe account, connected from the app in a few minutes. Charges go straight to you — RideBits takes no cut of your fares, ever. Payouts, statements, and card fees are between you and Stripe, managed from your own Stripe Dashboard.

Cards at booking

With Stripe connected and card payments on, clients add a card to book. The card is saved, not charged — securely stored with Stripe against your account, ready for you to charge on your terms. When you book on a client's behalf, the card can wait until later.

Charging the card

You're always in control — nothing is charged automatically, and when to charge is your call: a deposit up front, the full fare after the trip, or anything between. Tap the trip's money row and charge the saved card from there — the full amount or any partial amount (deposits, top-ups, and adjustments all work) — and taking a payment on a not-yet-confirmed request confirms it in the same stroke. Prefer cash, Zelle, or a check? Record the payment instead and the books stay right — no Stripe required for that.

No-shows and $0 trips

A no-show ends as a finished trip, so its price stands and it waits in Unpaid like any other: charge all of it, part of it or none, pointing to the booking terms your client accepted — they're kept on the trip. RideBits never charges on its own. To charge nothing, set the price to $0: $0 means nothing owed, for any trip, and it leaves Unpaid; a card request still waiting on the client is withdrawn. Money already taken shows as overpaid, so you know to refund it. Price it above $0 again and it's owed again.

Card requests

No card on file, or one that declined? Tap Request a card on the trip's money sheet. Leave Charge it automatically on, with the amount (the trip's balance to start), and the client pays in one step — or switch it off to collect a card you charge later yourself.

A client in the app gets the request in their chat with you, with a notification. A client who hasn't joined yet gets nothing from us: the button reads Get the link, and you send it yourself with Share link or Copy link — by text, WhatsApp, email, whatever you use. Every request has a link, so clients in the app can get one too.

With an amount, the client sees Pay $148.00 — in the app or on the link's page — and one press saves their card and pays. If their bank wants them to confirm the payment, they do it right there as they pay; if their bank declines, the card stays saved for you to retry. And if a charge you make is refused because the bank wants the client to approve it, the money sheet offers Request payment instead of a retry — they approve as they pay. Until they answer, the trip shows Card request out with the link and Cancel. A link works for 7 days, then reads Link expired · Resend. Change the trip's price while a request for an amount is waiting and it's cancelled — the client's card reads Cancelled — and you're told to send a new one for the new amount. From any client's page — tap their card row — Request a card asks for a card for all their trips with you. Drivers never see any of it.

Typing in a client's card

When a client gives you their card — read out on a call, or handed over — tap Add their card: from the client's page (tap their card row), in the money sheet of a trip with no card, or on Review when you book for them. First you confirm they gave you the card and agreed you can keep it on file for their trips; then Stripe's card form, where the number goes straight to Stripe. Saving never charges — you still charge from the money sheet.

The card goes on that trip — or, from the client's page, on their open trips without a card — and the trips you book for them next start with it. A client with more than one card? The money sheet's card row has Change — pick which card the trip uses (nothing is charged), even after a decline — and so does Review when you book for them. If their bank wants them to approve the card, it can't be done from your screen: send them a card request instead. Their page shows each card with who added it and when; your team can remove the cards it added, never one the client added. A client in the app gets a line in their chat with you and sees the card as added by your company; a client who hasn't joined hears nothing from us.

Receipts

Every trip has a receipt in the app — itemized quote, every payment, and the balance — visible to you and the client. For a client who isn't in the app, or anyone you'd rather send a page, Share in the trip's ⋮ menu → The client makes a link with the trip's details, the fare and what's been paid — the summary and receipt in one. It keeps working after the trip, and you can turn it off from the same place.

Refunds and disputes

Refunds and disputes are handled in your own Stripe Dashboard — that's by design, since the money and the card relationship are yours, not ours. RideBits reflects what happened (receipts show refunded amounts) but never moves your money.