Dispute / Chargeback Policy
How a rider challenges a charge, what evidence SYIBE reviews, decision timelines, and how external chargebacks are handled.
- Dependency class
- B · Provider-dependent
- Needs final payment, KYC, maps, telecom or IoT provider details.
- Consent
- Not a consent document
- Not revocable while the account is active
Version 0.1-draft · v1 Working Draft — frozen
Draft clauses
Dispute / Chargeback Policy
- 01
A ride charge may be disputed in the application within the stated window, with a reason and optional evidence.
- 02
SYIBE reviews ride telemetry, route, duration, parking confirmation, fare breakdown and support history.
- 03
Outcomes: approved, partially approved, rejected with reasons, or escalated for further evidence.
- 04
A bank or provider chargeback is answered with the same evidence pack; the account may be restricted while an unpaid balance remains.
- 05
Repeated unfounded disputes may lead to restriction under the anti-fraud rules.
Open questions for legal review
- Dispute window length, decision SLA and provider chargeback timelines.
These documents are professional working drafts prepared for the SYIBE operating model. They are not legal advice and are not approved production legal language. Before public launch, every jurisdiction-sensitive document must be reviewed by qualified local legal counsel once the corporate entity, regulatory classification, municipal permissions, insurance structure, payment provider, KYC provider and hardware structure are finalised.