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.
Saved, not chargedCharging 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. From the trip's money card, charge the saved card for 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.
Payment requests
No card on file, or a card that declined? Send a payment request: the client gets a private in-app prompt (and a push notification) to add or update their card — optionally approving a charge in the same step. It's private between you and the client; drivers never see billing.
Receipts
Every trip has a receipt in the app — itemized quote, every payment, and the balance — visible to you and the client.
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.