A long-time Dart user documented an unexpected fare discrepancy involving a familiar route between Batu Satu and Gadong. After comparing past ride history and contacting Dart Support, multiple explanations were provided, including peak-hour pricing and destination pin differences. Dart later reviewed the case, amended the fare from BND 5.90 to BND 5.00, refunded the balance and stated the matter would be investigated internally. The article reflects on pricing transparency, algorithm-driven services and the importance of clear customer communication.
Disclaimer This article is based on the writer’s personal experience and documented correspondence with Dart Support. The views expressed are observational and reflective in nature and should not be interpreted as allegations of fraud, misconduct or intentional wrongdoing by Dart, its drivers or staff. Ride-hailing fare calculations may involve operational and algorithmic factors not visible to end users.
The Missing 90 Cents
I've been using Dart for years. Long enough to know that while fares fluctuate, certain routes tend to settle into familiar ranges.
One of those routes is from Batu Satu area to Gadong.
Not exactly the same every single time, of course. Traffic changes. Demand changes. Timing matters. But after enough rides, you develop a rough instinct for what feels normal.
So when I opened the app one afternoon and saw BND 5.90 quoted for a familiar journey, something immediately felt different.
Not shocking.
Just unusual.
A Familiar Ride, An Unfamiliar Fare
The trip was simple:
- pickup from Batu Satu area,
- drop-off around The Mall Gadong area,
- approximately 3 PM.
Out of curiosity, I checked my ride history.
A previous trip from the same pickup location to Gadong, taken at almost the same time of day, had cost BND 5.00.
That caught my attention.
Not because 90 cents would make or break my day, but because it stood out from years of using the service.
Most regular commuters eventually develop a mental benchmark for familiar routes. You may not remember exact numbers, but you remember the range.
And this one felt outside the range.
Asking A Simple Question
So I contacted support with what I thought was a straightforward question:
“When did the price increase?”
The first explanation I received was:
peak hour pricing.
Fair enough.
Dynamic pricing exists everywhere now. Ride-hailing platforms adjust fares according to demand, traffic, driver availability and timing. Most people understand that.
But from my own experience, even peak fares on that route usually hovered around BND 5.50 rather than BND 5.90.
I pointed that out.
The Explanations Changed
As the conversation continued, the explanations evolved.
First:
peak hour pricing.
Then:
there had been no changes in the pricing system.
Later:
the fare differed depending on the destination pin location.
Technically, that could absolutely be true.
Algorithms do not think the way people do. They work with exact coordinates, mapping logic, zoning, routing behaviour and internal calculations users never see.
McDonald's Gadong and BIBD at The Mall are not literally the same point on a map.
But from the perspective of an ordinary commuter, both destinations feel practically side by side within the same immediate area.
So naturally, I asked:
“Tell me what's the difference.”
At that point, I was less interested in the fare itself and more interested in understanding how the system arrived at that number.
The Unexpected Outcome
Few days later, support followed up again.
This time, the tone changed.
They informed me that after reviewing the matter, they would be reassigning the trip to reflect the “correct fare” of BND 5.00 while they continued investigating the cause internally.
Shortly after, they confirmed:
- the amended trip had been applied,
- the balance would be refunded,
- and the original trip had been cancelled.
To Dart's credit, they eventually acknowledged the discrepancy and corrected it.
That matters.
Because at that point, the issue was no longer simply about perception or personal assumption. Something in the fare calculation or classification had apparently warranted adjustment.
One Last Question
Before ending the conversation, I asked one final thing:
“Is the driver's side affected with this amendment?”
Support replied that the driver would not be negatively affected, though they had informed him about the matter and he had acknowledged it.
I was relieved to hear that.
Because throughout the exchange, my concern was never about blaming the driver or getting anyone into trouble.
The driver simply accepted the fare generated by the system.
The support staff were responding with the information available to them.
What interested me was the gap between:
- the fare shown,
- the explanations given,
- and the eventual correction.
A Small Incident, A Bigger Reflection
In the end, this was never really about 90 cents.
It was about clarity.
Today, many of the services we rely on daily are powered by systems we cannot see:
- ride-hailing apps,
- food delivery platforms,
- online bookings,
- subscription pricing,
- algorithm-driven recommendations.
We are shown the final number.
But we are rarely shown how that number was produced.
Most of the time, we accept it without question.
Until one day, something feels unfamiliar.
And in those moments, trust depends less on the amount itself and more on whether the explanation makes sense.
Perhaps there was a perfectly valid technical reason for the discrepancy.
Perhaps the system calculated something I could not see.
But what stayed with me was not the fare difference itself.
It was how difficult it became to get a clear and consistent explanation for a very ordinary question.
Sometimes the smallest discrepancies reveal the biggest gaps in transparency.
No comments:
Post a Comment