Skip to main content

How Local Pass Delivery, Pickup, and Vendor’s Own Delivery affect wallet fields and payouts.

Overview

Local Pass supports three fulfilment modes. The mode determines which wallet fields are populated when an order completes, which in turn affects the net transfer amount at payout time.
The delivery mode does not change the payout transfer formula — it determines which fee fields (particularly merchantSubsidy) are present in the wallet at settlement time.

Mode comparison

Local Pass Delivery

A customer places an order and selects standard delivery. Local Pass dispatches a driver from its network to collect the order from the vendor and deliver it to the customer.How it works:
  • Customer pays for delivery at checkout
  • Local Pass assigns a driver from its network
  • Driver collects from the vendor’s location
  • Vendor is not involved in the logistics
Wallet impact:
Merchant subsidyis deducted after the Stripe transfer completes, not from the transfer amount itself. It is tracked separately for driver cost accounting purposes.

Fee summary by mode


Merchant subsidy explained

The Merchant subsidyfield appears in the vendor wallet only for Local Pass Delivery orders where the vendor contributes toward driver costs.
When a merchant uses their own fleet of drivers and offers free delivery, the customer pays $0 at checkout. In this case, Local Pass covers any outstanding balance owed to the driver at the end of the billing cycle, and the amount is then deducted from the merchant’s wallet.
Merchant subsidyis not subtracted from the Stripe transfer amount. It is instead decremented from the wallet balance fields after a successful transfer. This keeps the driver cost accounting separate from the money-in-transit calculation and ensures the Stripe transfer record reflects only the vendor net.
Yes. When Merchant subsidy > 0, a “Driver payouts: −$X.XX” line item is shown in the Payment Breakdown section of the Wallet page, along with an info button explaining the subsidy.