YORIDEMOVE WITH CLARITY

PAYMENTS & CANCELLATIONS

Cancellation & Refund Policy

Draft prepared 25 October 2026. Cancellation charges, refund timelines, and the responsible operator must be confirmed before publishing as binding policy.

No automatic refund, fee amount, or processing deadline is promised by this draft. The current system must be checked for each ride/payment before making a decision.

Cancel a ride

Use the cancellation control on the ride in the Customer app and review the status displayed. The backend supports ride cancellation workflows. A cancellation charge is not stated here because a public charge schedule was not verified in the project. The operator must publish any applicable conditions and amounts before charging customers.

Payment methods

The current API marks cash as supported and online payment as unavailable until a gateway is configured. Do not submit online payment details through this website. The project creates ride payment records for cash handling; a pending record alone does not mean payment was collected.

Failed, duplicate, pending, or disputed payment

Record the ride reference, date, amount shown, and relevant payment status. Do not send full card/bank credentials or OTPs. Contact YORIDE through the verified channel after it is configured. For cash disputes, describe the collection and receipt/status shown in the app.

Refund requests

Submit a request through the contact form with the ride reference and a short explanation. The support recipient must be configured for the request to be delivered. Eligibility, any evidence required, and processing times must be confirmed by the operator. If a payment provider is integrated later, any approved refund may depend on that provider's processes and timelines; no such online provider was identified in the inspected code.

Owner decisions required

  • Whether any cancellation charges apply, and exact conditions/amounts.
  • Who may approve a refund and the eligibility rules.
  • How cash, duplicate, and failed-payment disputes are resolved.
  • Support contact and response/processing timelines.
  • Any payment-provider-specific terms, if a gateway is added.

Last prepared: 25 October 2026. Effective date and final policy require operator and legal review.