All policies

Dispute & Chargeback Policy

Reporting service problems, payment disputes and driver payout complaints.

Riders and driversASB-POL-03
Read the policy
Document details

ASAMBE Ride together. Pay less. Go further. Kagisano MG (Pty) Ltd t/a Asambe · Reg. No. 2025/116497/07 27 Kilimanjaro Crescent, Blue Hills, 1685, South Africa Dispute & Chargeback Policy ASB-POL-03 · Item Detail Entity Kagisano MG (Pty) Ltd t/a Asambe, Reg. No. 2025/116497/07 Policy owner Sethu Adande, Chief Operating Officer Approver Mantsho Matoane, Chief Executive Officer Review cycle Annually, and after any change to refund rules or a spike in disputes

1. Purpose and principles

When something goes wrong on a trip, riders and drivers should know exactly what happens next, and should get a fair answer quickly. Asambe takes responsibility for the end-to-end transaction. It secures and transfers customer payments, applies its refund policy, and finances approved refunds as a money-back guarantee. This policy follows four principles:

Resolve it before it becomes a chargeback. A fast refund or clear explanation is better for the rider, the driver and the card system than a bank dispute.

Safety first. Any safety concern is handled before any money question.

Decide on evidence. Every trip leaves a record. Decisions rest on that record, not on who complains loudest.

Fair to both sides. Riders can expect a refund where service standards were not met. Drivers can expect to be paid for services delivered to the required standard.

2. Scope

This policy covers three types of dispute.

TypeDescriptionWho raises it
A. Service disputesProblems at pickup, during the journey or at drop-off, cancellations, wrong vehicle or driver, overchargingRider, or driver about a rider
B. Payment disputes and chargebacksA cardholder disputes a payment with their bank, or the payment provider notifies Asambe of a chargebackCardholder through the bank
C. Driver payout and account disputesPayout amount, held or recovered funds, rating, suspensionDriver

3. Liability in summary

Asambe is financially responsible to the payment provider and to riders for disputes and chargebacks on transactions processed through the platform. Asambe finances approved refunds, which may be full or partial depending on the circumstances and the Passenger Cancellation and Refund Policy (ASB-POL-07). Where a driver is at fault, Asambe may recover the cost from that driver under the Driver Terms, as set out in ASB-POL-06. Riders are shown the refund policy before they pay. Acceptance is recorded with a date and time.

4. How to raise a dispute

ChannelDetails
In the appA Report a problem button on every trip, available during the trip and after it
Emailsethu@asamberides.co.za, with the booking reference
Time limitService disputes are best raised within 72 hours of the trip ending. Late reports are still reviewed. Nothing in this policy limits a person's legal rights.

The payment statement shows the name ASAMBE so riders can recognise the charge. Riders are encouraged to contact Asambe before contacting their bank, and the app and receipts say so.

5. Service dispute process (Type A)

StepActionTarget
1. AcknowledgeAutomatic acknowledgement with a reference numberImmediate
2. TriageSafety issues go to the COO at once. Other cases go to the support queue.Safety: immediate. Other: 1 business day
3. Protect fundsThe trip payment stays held, or the driver payout is paused if not yet releasedAt triage
4. InvestigateReview the evidence in section 6. Contact both parties for their account.Up to 3 business days
5. DecideApply the outcome matrix in section 7 and tell both parties in writing, with reasonsWithin 3 business days of starting the investigation
6. Pay outRefund the rider and/or release the driver's paymentWithin 2 business days of the decision

Card refunds reach the rider's account according to their bank's processing times. The app shows the refund status. Safety incidents. Where a rider or driver reports harm, threat, harassment or unsafe driving, Asambe contacts the reporter promptly, pauses the other party's account, preserves all trip data, offers support in contacting SAPS, and refunds the trip in full. Asambe cooperates with SAPS and with court orders.

6. Evidence Asambe relies on

Booking record, fare and seat details, and the time the rider accepted the terms and the refund policy.

Trip PIN verification at pickup.

GPS trace, route, distance travelled, and live-share records.

Both parties' trip confirmations, or the absence of one.

In-app messages and support tickets.

Verification record for the driver, rider and vehicle at the time of booking.

Ratings, prior complaints and prior disputes for each party.

7. Outcome matrix

Outcomes follow ASB-POL-07. Refund percentages are set out there. In short:

SituationTypical outcome
Driver cancels, does not arrive or uses a different vehicleFull refund. Driver may be penalised.
Safety incidentFull refund. Driver suspended pending review.
Trip ends early for a reason attributable to the driverRefund for the unused distance, and possibly more depending on the complaint.
Service below the standard shown at bookingPartial refund based on the nature of the complaint.
Rider cancels or does not showRefund according to the cancellation schedule.
Complaint not supported by evidenceNo refund. Written reasons given. Appeal available.
Complaint found to be false or abusiveNo refund, and account action for the abusive party.

8. Chargeback process (Type B)

StepActionTarget
1. ReceiveChargeback notice arrives from the payment provider and is logged with the bookingWithin 1 business day of receipt
2. ReviewCheck whether the case is a genuine fraud, a service dispute, a duplicate or a processing error1 business day
3. Refund early where rightIf the rider is clearly owed money, refund or accept the chargebackAt review
4. Build the evidence packCompile the records in section 6 plus the payment record, acceptance of terms, and IP and device dataReady 2 business days before the deadline
5. RespondSubmit through the payment provider before the card scheme deadlineAlways before the deadline
6. Follow upRecord the outcome, handle any further stage, learn from the caseWithin 5 business days

Evidence required by chargeback reason:

Chargeback reasonMain evidence
Cardholder says they did not make the paymentDevice, IP, 3-D Secure result, account history, trip PIN, GPS trace
Service not provided or not as describedTrip PIN, GPS trace, both confirmations, messages, refund policy acceptance
Duplicate charge or wrong amountPayment reference records and fare breakdown
Cancelled or refunded but still chargedCancellation record, refund reference

Decisions to accept or contest a case above R5,000, or to proceed beyond the first response stage, are made by the COO and CEO together.

9. Funds during a dispute and recovery

A disputed trip's payout is paused. Other trips for the same driver are not affected unless there is a safety or fraud concern.

If the driver has already been paid and the rider is refunded or charged back, Asambe pays the rider first and then recovers from the driver where the driver was at fault. Recovery is by deduction from future earnings, from the driver's reserve if one applies, or by demand.

Asambe bears the loss where the cause is card fraud that it should have detected, a platform error or an unsupported complaint that it chose to refund. Full liability mechanics are in ASB-POL-06.

10. Driver disputes (Type C)

Drivers can challenge a payout amount, a hold, a recovery, a rating or a suspension in the app or by email. Asambe replies within 1 business day and decides within 5 business days. A person who was not involved in the original decision reviews the matter. Drivers receive written reasons.

11. Escalation and appeals

1. First-level support handles the dispute.

2. COO review applies if either party appeals. A decision follows within 5 business days.

3. CEO review is the final internal step for unresolved or high-value matters. Riders keep the right to approach the National Consumer Commission, an appropriate ombud, or a court. Riders also keep their right to dispute a card payment with their bank.

12. Learning and prevention

The COO reviews every dispute category monthly. Repeated causes are fixed at the source, through driver coaching, clearer booking information, better route data or changes to monitoring rules (ASB-POL-02). Drivers with repeated avoidable disputes lose access to the platform under ASB-POL-01.

13. Performance measures

MeasureTarget
First human response1 business day
Service disputes resolved within targetAt least 90%
Disputes resolved without a chargebackAt least 95%
Chargeback ratioBelow 0.5%
Chargeback responses submitted on time100%

14. Records, privacy and training

Dispute files are kept for at least five years in secure storage, with access limited to named staff and every access logged. Personal information is handled under the Protection of Personal Information Act, 2013, and ASB-POL-04. Support and risk staff are trained at joining and annually on this policy, on handling distressed users, and on evidence preservation. This policy is reviewed at least annually.