Skip to main content

How to Set Up Fleet Payments

Fleet Payments on MeterApp allow you to seamlessly manage payouts to drivers and your fleet’s Stripe account. Follow this guide to enable and configure Fleet Payments for your fleet

Written by Jonathan Osacky
Updated this week

1. Connecting Your Stripe Account

Before you can set up Fleet Payments, ensure your fleet’s Stripe account is connected. If not:

2. Configuring Payments

On the Fleet Payments page, you’ll find the following options:

Payments Toggle

  • Enable Fleet Wide Payments: When this toggle is enabled, all trip payments conducted by drivers in your fleet will be automatically paid out to the fleet owner’s connected Stripe account. This simplifies payroll and ensures faster fund distribution.

Driver Payouts Toggle

  • Enable Driver Payouts: When this option is enabled, trip payments are automatically split between the fleet’s connected Stripe account and the driver’s Stripe account.

    • Example: A driver receives their share directly without additional payroll tasks.

  • If disabled, all payments will go to the fleet’s Stripe account, requiring manual payroll processing by the fleet owner.

Driver Payout Percentage

  • Use the slider to set the percentage of each fare that drivers will receive as their payout. The remaining percentage will go to the fleet’s Stripe account.

    • For example, if set to 90%, on a $100 fare, the driver receives $90, and the fleet account gets $10.

  • After configuring the percentage, click Submit to save your settings.

3. Payout Distribution

The Payout Distribution section shows how each fare is divided between the driver, the fleet, and the platform. Here’s how it works:

  • Credit Card Platform Fee (3.5% + $0.30): A 3.5% + $0.30 USD platform fee is deducted first. This fee covers credit card processing, customer support, and ongoing improvements to the app.

  • Fleet & Driver Split (e.g., 90% / 10%): After the platform fee is deducted, the remaining amount is split between the driver and the fleet. For example, if the fleet is set to take 10%, the driver receives 90% of what’s left.

Example Breakdown (on a $100 Fare with 10% Fleet Share)

Component

Amount

Fare Total

$100.00

Credit Card Platform Fee (3.5% + $0.30)

$3.80

Remaining Amount

$96.20

Driver Share (90%)

$84.78

Fleet Share (10%)

$9.42

4. Drivers Stripe Status

At the bottom of the Fleet Payments page, you’ll see the Drivers Stripe Status section:

  • This table lists all drivers associated with your fleet, their email addresses, and their Stripe connection status.

  • A green Connected indicator means the driver’s Stripe account is successfully linked. If not, prompt drivers to connect their Stripe account to receive payouts automatically.

5. Additional Notes

  • Read More: Click the Read More link in the Payments section for detailed explanations about payment processes and payout management.

  • Ensure all drivers in your fleet have their Stripe accounts connected to enable automatic payouts.

Can I use my own Stripe checkout instead of Stripe Connect?

At this time, Meter’s fleet payment flow requires a connected Stripe account through Stripe Connect.

Using a separate custom Stripe checkout flow instead of Stripe Connect is not currently supported for fleet booking payments.

If your team needs a custom payment setup, contact support and we can review your use case and share available options.

Can I use my own Stripe Checkout instead of Stripe Connect?

At the moment, Meter payments run through the Stripe account you connect inside Meter.

  • Custom external Stripe Checkout flows are not supported for Meter bookings or Rider Hub payments.

  • To accept digital payments, connect Stripe in Meter and complete the setup flow.

If your team has a special billing workflow, contact support and we can recommend the best available setup.

Troubleshooting: "An error occurred in the server components render" in Fleet web tabs

If Fleet Management tabs (Bookings/Dispatch/etc.) show "something went wrong" with a server components render error, this indicates a web rendering/backend issue. Please contact support with your fleet account email, timestamp, and affected tabs so engineering can investigate immediately.

Did this answer your question?