Work with Sow.

Section 8. Chargebacks, disputed fares and evidence.

(a) Carrier payments. Rides are direct charges on the carrier's connected Stripe account. The carrier provides transportation as merchant of record and maintains its correct DBA, support details and statement descriptor in Stripe. The carrier bears the disputed fare, including gratuity and pass-through amounts. Stripe attempts to debit the connected account first; Stripe account settings and agreements determine fee collection and ultimate negative-balance responsibility. These terms do not change Stripe's rights or eliminate Sow's legal obligations.

(b) Stripe dispute fees. The carrier bears actual applicable Stripe dispute fees, including any fee to counter a dispute. No fixed $15 fee is promised. Sow reimburses a verified fee caused by Sow charging the wrong amount, capturing twice, or charging after a cancellation recorded by the platform. Staff document the error and actual fee before reimbursement.

(c) Sow commission. Sow returns its full application fee on every lost dispute and full fare refund, regardless of the dispute reason or carrier fault. Sow retains the agreed commission if the dispute is won, unless the fare is fully refunded. Sow does not retain commission as a penalty for carrier misconduct or noncooperation. A partial fare refund requires separate reconciliation; it is not treated as a full refund.

(d) Evidence. Carrier authorizes Sow to assemble and submit available booking and payment records to Stripe to respond to disputes. These can include an actual supplied signed waybill, recorded prearranged-service acceptance and policy version, recorded alcohol/under-21 answers, recorded trip times, accepted cancellation terms, receipt and actual statement descriptor. Sow does not invent missing records, signatures or GPS logs. Carrier must monitor its private portal and answer Sow's questions within 48 hours, or sooner if Stripe's deadline requires it. Staff must monitor Stripe and failed submissions. Submission does not guarantee a dispute will be won. Cancellation-fee disputes use the same allocation and the accepted cancellation policy.

(e) Network review. Three lost disputes closed in a rolling 90-day period, or more than 0.75% disputed payments in a rolling 90-day period, pauses new Sow network dispatch pending human review. The rate is distinct disputed payments opened in the period divided by successful Stripe payments created in the same period, including later-refunded payments. There is no minimum-volume exemption. A carrier's separate hosted website remains available. A later dispute or outcome can require another review after dispatch resumes.

(f) Reserve. No reserve is collected at launch. Sow may propose a reserve for a carrier above these thresholds, capped at 10% for 30 days. Collection would require a separate notice, applicable agreement and implementation; accepting this section does not start a reserve.