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.
| Type | Description | Who raises it |
|---|---|---|
| A. Service disputes | Problems at pickup, during the journey or at drop-off, cancellations, wrong vehicle or driver, overcharging | Rider, or driver about a rider |
| B. Payment disputes and chargebacks | A cardholder disputes a payment with their bank, or the payment provider notifies Asambe of a chargeback | Cardholder through the bank |
| C. Driver payout and account disputes | Payout amount, held or recovered funds, rating, suspension | Driver |
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
| Channel | Details |
|---|---|
| In the app | A Report a problem button on every trip, available during the trip and after it |
| sethu@asamberides.co.za, with the booking reference | |
| Time limit | Service 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)
| Step | Action | Target |
|---|---|---|
| 1. Acknowledge | Automatic acknowledgement with a reference number | Immediate |
| 2. Triage | Safety issues go to the COO at once. Other cases go to the support queue. | Safety: immediate. Other: 1 business day |
| 3. Protect funds | The trip payment stays held, or the driver payout is paused if not yet released | At triage |
| 4. Investigate | Review the evidence in section 6. Contact both parties for their account. | Up to 3 business days |
| 5. Decide | Apply the outcome matrix in section 7 and tell both parties in writing, with reasons | Within 3 business days of starting the investigation |
| 6. Pay out | Refund the rider and/or release the driver's payment | Within 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:
| Situation | Typical outcome |
|---|---|
| Driver cancels, does not arrive or uses a different vehicle | Full refund. Driver may be penalised. |
| Safety incident | Full refund. Driver suspended pending review. |
| Trip ends early for a reason attributable to the driver | Refund for the unused distance, and possibly more depending on the complaint. |
| Service below the standard shown at booking | Partial refund based on the nature of the complaint. |
| Rider cancels or does not show | Refund according to the cancellation schedule. |
| Complaint not supported by evidence | No refund. Written reasons given. Appeal available. |
| Complaint found to be false or abusive | No refund, and account action for the abusive party. |
8. Chargeback process (Type B)
| Step | Action | Target |
|---|---|---|
| 1. Receive | Chargeback notice arrives from the payment provider and is logged with the booking | Within 1 business day of receipt |
| 2. Review | Check whether the case is a genuine fraud, a service dispute, a duplicate or a processing error | 1 business day |
| 3. Refund early where right | If the rider is clearly owed money, refund or accept the chargeback | At review |
| 4. Build the evidence pack | Compile the records in section 6 plus the payment record, acceptance of terms, and IP and device data | Ready 2 business days before the deadline |
| 5. Respond | Submit through the payment provider before the card scheme deadline | Always before the deadline |
| 6. Follow up | Record the outcome, handle any further stage, learn from the case | Within 5 business days |
Evidence required by chargeback reason:
| Chargeback reason | Main evidence |
|---|---|
| Cardholder says they did not make the payment | Device, IP, 3-D Secure result, account history, trip PIN, GPS trace |
| Service not provided or not as described | Trip PIN, GPS trace, both confirmations, messages, refund policy acceptance |
| Duplicate charge or wrong amount | Payment reference records and fare breakdown |
| Cancelled or refunded but still charged | Cancellation 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
| Measure | Target |
|---|---|
| First human response | 1 business day |
| Service disputes resolved within target | At least 90% |
| Disputes resolved without a chargeback | At least 95% |
| Chargeback ratio | Below 0.5% |
| Chargeback responses submitted on time | 100% |
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.
