Monetization Models
3 flexible models to generate revenue with your mobility platform.
Wallet Recharge
Drivers recharge their wallet and a commission is automatically deducted for each completed trip.
Driver recharges
Top up wallet via gateway
Payment gateway
Stripe, MercadoPago, PayPal, Transbank
Available balance
Credited to driver wallet
Auto commission
Deducted per completed trip
Client Payment
Clients pay through the gateway, the platform commission is deducted and the rest is credited to the driver's wallet.
Client pays
Pays for trip via app
Gateway processes
Secure payment processing
Platform commission
Configurable % deducted
Driver wallet
Rest credited instantly
Withdrawals
Drivers request withdrawals from their wallet. The administrator approves and the bank transfer is processed.
Request withdrawal
Driver requests from wallet
Admin approves
Review and approval
Bank transfer
Sent to driver's bank
Configurable commission
Define the per-trip commission percentage your platform charges. Configurable per company.
Integrated Gateways
Connect with leading payment providers to offer maximum flexibility.
Stripe
International
Checkout + Payment Intents
Mercado Pago
Latin America
Checkout Pro
PayPal
Global
Orders API v2
Transbank
Chile
WebPay Plus
Culqi
Perú
Cards + Yape rail
PayPhone
Ecuador
Card + QR
dLocal
Latin America
Local methods aggregator
Pagadito
Central America
Card + local rails
Kontigo
Venezuela
Cards + local methods
Cash
Universal fallback
Driver collects + reports
Marketplace flows: money lands in your account, not ours
Operators connect their own merchant account; Cabgo orchestrates the charge but never holds the funds. Two Connect-style integrations are live today.
Stripe Connect
Express + Standard accounts
- • Operator onboards via a Stripe-hosted flow; ID + bank verification happens entirely on Stripe.
- • Every charge is created on the operator's connected account using application_fee_amount for Cabgo's platform fee.
- • Payouts to the operator's bank account follow Stripe's default schedule (T+2 or daily, depending on country).
Mercado Pago Marketplace
OAuth + split payments
- • Operator connects their Mercado Pago account via OAuth from the Cabgo dashboard — no API keys to copy.
- • Charges use the application_fee + collector_id pattern so funds land in the operator's wallet on the first payment.
- • Withdrawals to the operator's bank follow Mercado Pago's local payout cycle (varies by country: instant in AR/BR, T+1 in MX).
Frequently asked questions
- The operator charges riders the trip price (a tariff the operator sets) and keeps 100%. Cabgo never touches that money. Cabgo only charges the operator the flat monthly subscription and the one-time app fee — every payment from end users goes straight to the operator's bank account.
- Through the payment gateway the operator configures on their tenant — Stripe, MercadoPago, Culqi (Peru), Transbank (Chile), Pagadito, dLocal, or cash. Each operator connects their own gateway account and payments land directly in that account, not in Cabgo.
- Yes — full flexibility: base fare, per-kilometer fare, per-minute fare, trip minimum, demand surge, surcharges by time/day/zone, tariffs per vehicle type, discount coupons, loyalty programs. All configured in the dashboard without code.
- The rider can tip after the trip ends (suggested percentage or custom amount). 100% of the tip is credited to the driver's Cabgo wallet — no operator or Cabgo cut. The driver withdraws their balance on the schedule the operator configures.
- No. Cabgo applies no additional commission on payments. Gateway commissions (Stripe, MercadoPago, etc.) are negotiated directly between the operator and the gateway provider — Cabgo only exposes the integration.
- Yes. Cabgo supports the driver-subscription model (the driver pays the operator a monthly membership to operate) and the per-trip commission model (a percentage of every trip goes to the operator). Both can be combined per tenant.