JakLingko: a Rp10,000 fare cap only works when inter-operator clearing and tap-out work
Solution case studies are scenarios based on common industry problem patterns. They do not refer to any client and are not MarkasDev project portfolio items. Our client portfolio is published separately.
Industry context
JakLingko and Transjakarta are run by Jakarta regional entities; MarkasDev plays no part. We read the official FAQ, government portals, and news coverage. JakLingko and Transjakarta are operated by regional entities / joint ventures in Jakarta’s public-transport ecosystem. This page is not our portfolio. We read PT JakLingko Indonesia’s official site, the Jakarta.go.id (Dishub) Jaklingko page, Transjakarta’s 2024 performance release, and ANTARA reporting, to show what happens when several modal operators must share fare rules, cards, and clearing.
According to Jakarta.go.id (Jaklingko page, updated 24 July 2023), PT JakLingko Indonesia is a joint venture of four entities: PT MRT Jakarta (Perseroda), PT Jakarta Propertindo (Perseroda), PT TransJakarta, and PT Moda Integrasi Transportasi Jabodetabek (MITJ). Its focus is intermodal payment and fare systems through Elektronifikasi Integrasi Pembayaran Transportasi Umum Jakarta (EIPTJ). The concept was launched on 15 July 2020, under Governor Regulation of DKI Jakarta Number 63 of 2020.
Since August 2022, the Integrated Fare programme sets a maximum of Rp10,000 for journeys that use more than one mode among Transjakarta, MRT Jakarta, and LRT Jakarta (same source). JakLingko’s official FAQ describes the calculation: an initial Rp2,500 boarding fee plus Rp250 per kilometre, a 180-minute validity window, and settlement through a Central Clearing House System (CCHS).
The case matters to leaders in transport SOEs, local transport agencies, modal operators, and operations teams weighing cross-system payment integration. The challenge is not “shipping a prettier ticketing app”. It is agreeing shared fare rules, connecting gates and cards to clearing, and owning reconciliation and the passenger experience after go-live.
Problem
Before an integrated fare scheme was widely used, passengers who changed modes in Jakarta tended to pay the full fare at each operator. Jakarta.go.id lists example single-mode normal fares: Rp3,500 for Transjakarta, Rp5,000 for LRT Jakarta, and up to Rp14,000 for the longest MRT Jakarta route. Without a shared cap, a multimodal trip can cost far more than a single-mode ride — JakLingko’s FAQ shows a sample comparison of Rp22,500 accumulated normal fares versus an Rp9,250 integrated package on one MRT–Transjakarta–LRT example route.
Fragmentation also shows up in payment instruments. Passengers carry different bank e-money cards, or QR tickets in an app, while each operator runs its own gates and tap-in/tap-out rules. Without activating a JakLingko Transport Card (via Balance Check Terminal) and without central clearing, systems struggle to recognise two or three legs as one integrated journey.
The operational burden sits with each Public Transport Operator (PTO) and the clearing house. JakLingko’s FAQ says the CCHS collects journey data from each PTO, consolidates distance/time/fare, and returns overcharges as cashback through the app. That means every missed tap-out, card switch between modes, or breach of the 180-minute window becomes a support case — not merely a UI bug.
At city scale, fare integration also depends on the volume and quality of the largest mode. Transjakarta’s 2024 performance release (6 February 2025) reports 371.4 million customers over the year, averaging more than one million customers per day. At that scale, reconciliation errors or gate outages affect the city, not only a handful of early adopters.
Constraints
- Integrated fare applies when a passenger uses more than one mode among Transjakarta BRT, MRT Jakarta, and LRT Jakarta — JakLingko FAQ; a single mode keeps each operator’s normal fare
- Maximum Rp10,000 per integrated journey; Rp2,500 boarding fee + Rp250/km; 180-minute validity from first tap-out to final tap-out — JakLingko FAQ
- Per JakLingko’s official FAQ, Mikrotrans, non-BRT buses, and KCI are not yet in the integrated-fare scheme; using those modes can break the scheme. ANTARA (27 June 2026) quotes the Ministry of Transport including Mikrotrans — we note the discrepancy and prefer the operator FAQ for scheme detail
- Supported bank e-money cards after JakLingko Transport Card activation: Mandiri e-Money, BCA Flazz, BNI TapCash, BRI Brizzi, Bank DKI JakCard, plus QR tickets via the app — JakLingko FAQ and Jakarta.go.id
- Bank card activation at Balance Check Terminals (BCT) in MRT/LRT stations and Transjakarta stops; Jakarta.go.id states the status change is free of charge
- Clearing depends on correct tap-in and tap-out on each mode; overcharges are returned as cashback via the app per JakLingko FAQ
- The Rp10,000 cap policy was still described as in force by the Ministry of Transport (ANTARA, 27 June 2026); the scheme has run since 2022 per that source and Jakarta.go.id
Approach
Diagnose
This section is analysis: how a Diagnose phase would show up in a case like JakLingko. It is not a claim that MarkasDev worked on JakLingko or Transjakarta.
A paid Diagnose is useful before a city agency or SOE locks budget for a “ticketing app” or “one card for everything”. The questions are concrete. Which operators sit inside the shared fare cap, and which only share a payment instrument without the cap? Who owns fare rules (local government vs joint venture vs each PTO)? What data must leave the gate for clearing — tap time, distance, mode code — and who signs the daily reconciliation SLA?
The pattern visible in public sources is a separation that must be mapped first: (1) payment / electronification integration (EIPTJ, cards, app), (2) the integrated-fare scheme with a cap and time window, (3) each mode’s operational performance (fleet, routes, satisfaction). Mixing all three in one SOW without an inventory often produces the expectation that “Mikrotrans is inside the Rp10,000 cap” while the operator FAQ still excludes it.
For teams copying the pattern in other cities, Diagnose also tests people–process–technology readiness: tap-out SOPs, stop staff training, BCT capacity, and a cashback runbook. Without that, a political go-live only moves the queue to the contact centre.
Deliver
This is analysis too. The Deliver phase splits the work into milestones with acceptance criteria that can be tested.
A sequence that fits the public descriptions: first, connect PTO gates to clearing (CCHS) and test cross-mode tap-in/tap-out. Second, activate JakLingko Transport Cards on bank e-money via BCT and the QR path in the app. Third, apply fare rules (boarding, per-km, cap, 180-minute window) with boundary tests — for example two modes in 179 minutes versus 181 minutes. Fourth, cashback and reconciliation for overcharges.
Example acceptance criteria (our analysis, not an official SLA whose seconds we quoted from public docs): a multimodal test journey yields total fare ≤ Rp10,000 when mode and time conditions are met; a single mode still uses the normal fare; missed tap-out has a written handling path; daily CCHS reports match each PTO’s logs within an agreed tolerance. See the Deliver frame and system and API integration for similar interface-contract patterns.
What to avoid: shipping the passenger app first while inter-operator clearing rules are still untested. In this case, the core value sits in fare rules + clearing, not in the app home screen.
Operate
This is analysis too. After go-live, the fare cap can remain “alive” in policy while field failures appear: offline gates, cards not yet activated, passengers switching cards between modes, or the 180-minute window lapsing. Operate answers who watches failed-tap volume, who processes backlog cashback, and which reports finance leaders at each PTO and the joint venture receive.
Transjakarta’s 2024 scale clarifies why Operate is not optional. The official release (6 February 2025) cites 371.4 million customers, a 4,388-unit fleet, 242 routes, and the TJ: Transjakarta app with 540 thousand users in the latest five months plus live bus tracking. In parallel, ANTARA quotes the CEO on an Rp3.7 trillion APBD subsidy and subsidy per customer down to Rp9,831. Fare integration only helps if the primary mode stays reliable and digital channels have owners after release.
In the Operate frame, clearing monitoring, cashback queues, gate/BCT patching, and communicating fare-rule changes become routine work. Operator digital channels — including bus tracking apps — also need their own incident runbooks, separate from “a new feature in the app store”.
High-level architecture
This diagram is our simplification from public JakLingko FAQ and Jakarta.go.id descriptions, not an official architecture we audited. Multi-mode payment (including KRL in Jakarta.go.id’s narrative) is not automatically the same as the Rp10,000 integrated-fare scheme — the FAQ limits the cap to TJ BRT + MRTJ + LRTJ. We did not open internal CCHS technical docs. The CCHS name and cashback flow are quoted from the official FAQ. The TJ: Transjakarta app is Transjakarta’s digital channel (2024 performance release), separate from the JakLingko app even though both serve the same ecosystem.
Typical outcomes
Every figure below comes from a source we opened. Scopes differ (Transjakarta calendar year vs JakLingko fare rules vs Ministry of Transport policy statements), so do not merge them into one “JakLingko ROI” metric.
Integrated fare rules. Jakarta.go.id: since August 2022, the maximum integrated journey cost for Transjakarta, MRT Jakarta, and LRT Jakarta is Rp10,000 when more than one mode is used. JakLingko FAQ: Rp2,500 boarding + Rp250/km, Rp10,000 cap, 180-minute window; their on-site sample compares Rp22,500 accumulated normal fares versus Rp9,250 integrated (saving Rp13,250 / 59% on that example — a site example, not a city-wide average).
Policy status in 2026. ANTARA (27 June 2026) quotes Ministry of Transport official Dedy Cahyadi that the Rp10,000 integrated-fare policy in DKI Jakarta still applies. That quote’s mode list includes Mikrotrans; that differs from the JakLingko FAQ stating Mikrotrans is not yet in the scheme. We do not adjudicate policy — we flag the source difference.
Transjakarta 2024 performance (official release, 6 February 2025). 371.4 million customers; average more than 1 million per day; population coverage served 91.7%; Accident Rate 0.36 (from 0.50); Customer Satisfaction Index 4.40; NPS 70.1%; subsidy per customer Rp9,831; fleet 4,388 (+2% yoy); routes 242 (+3%); 300 electric buses by December 2024; non-farebox revenue Rp218.4 billion (described as 3.5× two years earlier); TJ app with 540 thousand users in the latest five months.
ANTARA corroboration (6 February 2025). Total customers 371 million (2024), 285 million (2023), 191 million (2022); satisfaction 4.4 (previously 4.2); NPS 70%; APBD subsidy Rp3.7 trillion; subsidy per customer Rp9,831 (2024), Rp11,400 (2023), Rp16,800 (2022).
What we did not find in primary sources we opened: annual integrated-fare transaction counts, the share of multimodal passengers using the Rp10,000 cap, a CCHS technical SLA in seconds, or PTO operating-cost savings in rupiah from clearing. We do not invent those figures. MRT Jakarta’s press page on the 7 October 2022 inauguration could not be fully downloaded (SPA site); we take August 2022 as the integrated-fare start date from Jakarta.go.id.
Typical or expected outcomes, not claims about MarkasDev project results.About this analysis
This page is compiled from open sources and is not a MarkasDev client project. We read the Integrated Fare FAQ on PT JakLingko Indonesia’s site, the Jaklingko page on Jakarta.go.id, Transjakarta’s 2024 performance release, and ANTARA coverage (February 2025 and June 2026). Every figure on this page comes from a source we opened, with the scope we state.
Why this case matters to your organisation
Transport SOEs, local transport agencies, passenger operators, and public-service digital teams often face the same question: how do you connect several ticketing/gate systems without forcing passengers to pay full fare at every hop? JakLingko’s pattern — a payment joint venture, a fare cap, central clearing, bank-card activation — is a public example you can dissect through Diagnose, system and API integration, and Operate.
Reading the case through Diagnose, Deliver, Operate
Three questions in order. Which operators sit inside the cap, what data must flow to clearing, and who owns reconciliation? That is Diagnose. How do you test gates, BCTs, QR, and 180-minute boundary cases with acceptance criteria? That is Deliver. Who owns cashback, validator outages, and fare-change communication once daily volume reaches city scale? That is Operate. If you are weighing an initial mapping, start with a paid Diagnose before large build budgets lock.
Limits of this analysis
We did not interview PT JakLingko Indonesia, Transjakarta, MRT, or LRT. We did not audit CCHS. MRT Jakarta’s October 2022 inauguration press page could not be fully read because the site is JavaScript-based. BPS DKI April 2025 figures are not cited because the page was blocked by bot protection when we accessed it. The Mikrotrans discrepancy between the JakLingko FAQ and the Ministry quote is left explicit. Treat this page as discussion material for leaders, not an audit report.
Sources
Accessed on 1 October 2026 (WIB / Asia/Jakarta).
- PT JakLingko Indonesia, Integrated Fare FAQ.
- DKI Jakarta Provincial Government / Dishub, Jaklingko, 24 July 2023.
- Transjakarta, 2024 Performance Report: Throughout 2024 Transjakarta Grew Strongly and Became More Efficient, 6 February 2025.
- ANTARA, Transjakarta customers reach 371 million in 2024, 6 February 2025.
- ANTARA, Ministry of Transport: Rp10,000 public-transport integration still applies, 27 June 2026.
- Search snippet of MRT Jakarta press on integrated-fare inauguration (7–8 October 2022) — full page body could not be downloaded in this session; August 2022 start date confirmed via Jakarta.go.id.