BI-FAST: shared 24/7 transfer rails do not remove the integration work inside each bank
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
BI-FAST is Bank Indonesia infrastructure and was not built by MarkasDev. This page draws on BI press releases and publications. BI-FAST (Bank Indonesia Fast Payment) is retail payment-system infrastructure provided by Bank Indonesia. This page is not our portfolio. We read BI press releases and reports, plus media that quotes BI, to show what happens when many banks and non-bank institutions must use the same payment rails.
According to BI press release No. 23/270/DKom (22 October 2021), BI-FAST would launch in December 2021 with individual credit transfer as the first priority. BI describes BI-FAST as the backbone of retail payment infrastructure going forward: secure, convenient, real time, and operating 24/7. The stated vision is CEMUMUAH services (fast, easy, cheap, secure, reliable) under the Indonesia Payment System Blueprint.
BI press release No. 26/279/DKom (21 December 2024) confirms the Phase I Stage 1 go-live date: 21 December 2021 for individual credit transfers. On the same calendar day three years later, BI opened Phase I Stage 2: bulk transfer, request for payment, and direct debit.
The case matters to leaders in commercial banks, rural banks (BPR), fintechs and finance operations teams. The challenge is not “buying a transfer app”. It is connecting core systems and customer channels to a shared standard, holding a real-time SLA, and monitoring failures after go-live.
Problem
Before shared real-time, 24/7 retail rails existed, interbank transfers in the retail segment depended on different paths. BI used the national clearing system (SKNBI) as a price benchmark: at launch, the maximum customer fee for BI-FAST was “slightly lower” than SKNBI (press release 23/270/DKom). Historically SKNBI did not behave like an always-on instant service. For customers and corporate finance teams that meant waiting time, fees that varied across banks, and longer reconciliation.
The operational burden sits with banks and BPRs. Each institution must run its own channels, limits, reconciliation and complaint handling when funds have “not arrived yet”. Without a shared standard, each bank pair can behave differently and keep different service hours. That raises support cost and the risk of booking errors.
BI positions BI-FAST as a response to digitalisation: consumption is shifting to digital platforms that demand mobile, fast, convenient, affordable and secure payments (press release 23/270/DKom). The root problem we read in that document is fragmented retail infrastructure, not merely “customers want a prettier app”.
In daily life the impact shows up when paying vendors, sending interbank payroll, or receiving urgent funds outside banking hours. When shared rails are missing or not widely used, people and businesses absorb delay and costs that are hard to compare across providers.
Constraints
- Participation is open to banks, non-banks and other parties that meet institutional, financial and information-system criteria, plus the 3C and Champion in Readiness tests (people, process, technology) — BI press release 23/270/DKom
- Participants may provide infrastructure independently, through an affiliate (sub-independent), or by sharing with a third party under BI rules — same source
- Initial maximum value is Rp250 million per transaction, reviewed periodically; participants may set lower customer limits to match their risk appetite — BI press releases 23/270/DKom and 26/279/DKom
- A two-tier price scheme applies: BI to participant, and participant to customer, with BI-set caps reviewed over time
- Services expand in stages: Stage 1 (2021) individual credit transfer; Stage 2 (21 December 2024) bulk, request for payment and direct debit — only for ready participants
- 24/7 real-time operation requires monitoring, failure handling and system capacity that does not stop at the end of the banking day
Approach
Diagnose
This section is analysis: how a Diagnose phase would show up in a case like BI-FAST. It is not a claim that MarkasDev worked on BI-FAST.
A paid Diagnose is useful before an institution chooses how to onboard. The questions are concrete. Will the bank or BPR join as an independent, affiliate or sharing participant? Which core systems and channels (mobile, internet banking, branch) must send and receive instructions? Who owns daily reconciliation and customer complaint handling when a transaction fails or stays pending?
In 2021 BI named Batch 1 and Batch 2 candidates after readiness assessments, with final confirmation after checkpoints and an industrial test (press release 23/270/DKom). That pattern is Diagnose in practice: inventory people–process–technology readiness first, then commit to a go-live date. For a BPR or fintech that is not yet a participant, Diagnose also maps options: join directly if the criteria are met, or rely on a partner or aggregator — without inventing a path that public sources do not describe.
Deliver
This is analysis too. The Deliver phase splits the work into milestones with acceptance criteria that can be tested.
The sequence visible in BI documents suits example milestones. First, a secure connection to BI-FAST infrastructure and a passed industrial test. Second, individual credit transfer on one or more customer channels. Third, expansion to bulk transfer, request for payment or direct debit after 21 December 2024, only when the participant is ready (press release 26/279/DKom says nine participants offered the new services at the initial stage).
Acceptance criteria must be measurable, for example: test payments succeed within an internally agreed real-time window; customer fees stay within BI caps; daily reconciliation matches internal logs and rail status; failure cases (timeout, invalid account) have a written handling path. These criteria are our analytical examples. They are not an official BI SLA quoted in seconds — in the releases we opened, BI stresses real time and 24/7 without publishing an “X seconds” figure in the same texts.
Operate
Also analysis. After go-live, the shared rail can stay healthy on BI’s side while a bank channel fails: expired certificates, traffic spikes, limit changes, or a mobile-banking bug. Operate answers who watches 24/7, which threshold triggers escalation, and which report reaches risk and operations leadership.
Antara (21 December 2024), quoting BI, says BI-FAST had processed 6 billion financial transactions by 15 December 2024 with a nominal value of more than Rp16 thousand trillion, and a 78.8% share in November 2024 for the segment up to Rp250 million. Volume at that scale only makes sense if participants run continuous monitoring and operating capacity — not a project that ends on launch day.
Under the Operate framework, transaction logs, failed-delivery queues and incident runbooks become routine work. Integration into core banking or a company’s finance systems also needs an owner after release; see our system integration and API service.
High-level architecture
This diagram is our simplification of BI's public descriptions, not an official BI-FAST architecture diagram. In Stage 1 the main service is individual credit transfer (one to one). In Stage 2 (21 December 2024) bulk transfer, request for payment and direct debit were added. BI allows participants to provide infrastructure independently, through an affiliate, or by sharing. Value limits and fee caps are set by BI and may be reviewed periodically.
Typical outcomes
Every figure below comes from a source we opened. Their scopes differ (calendar year, cumulative since go-live, or a single quarter), so they must not be merged into one metric.
Go-live. BI press release 26/279/DKom sets 21 December 2021 as Phase I Stage 1 (individual credit transfer). The earlier launch announcement (23/270/DKom, 22 October 2021) named 22 Batch 1 candidates; coverage of the launch-day release commonly cites 21 Batch 1 participants going live — we did not re-open the participant-list PDF appendix in this session, so we record 21 as the figure widely cited from the 21 December 2021 launch release.
Fees (initial 2021 policy). BI to participant Rp19 per transaction; maximum participant to customer Rp2,500 per transaction (23/270/DKom). For Stage 2 services (26/279/DKom): bulk Rp16 to the sending participant and maximum Rp2,100 to the customer; request for payment Rp19 / maximum Rp2,500; direct debit Rp19 to the receiving participant / maximum Rp2,500 to the receiving customer. Maximum value Rp250 million per transaction.
2024 volume (January 2025 Board of Governors meeting release). BI press release No. 27/8/DKom (15 January 2025) states that retail volume processed through BI-FAST reached 3.4 billion transactions, up 62.4% year on year, with a value of Rp8.9 trillion in 2024. The same release projects 34.1% volume growth for BI-FAST in 2025.
Important note on the Rp8.9 trillion value. That figure is written in the BI release. Yet other BI sources and media quoting BI give a much larger value scale: the Monetary Policy Report for Q4 2025 states BI-FAST value in Q4 2025 alone at Rp3,442.26 trillion for 1,358.65 million transactions. Antara (21 December 2024), quoting BI, cites a cumulative value through 15 December 2024 of more than Rp16 thousand trillion for 6 billion transactions. We therefore quote Rp8.9 trillion as printed in the January 2025 RDG release, and flag a likely unit or drafting inconsistency. We do not “correct” the official figure with our own estimate.
Participants and share (Antara reporting of BI remarks, 21 December 2024). Total participants were given as 127 at that time; BI-FAST’s share was 78.8% in November 2024 for the ≤ Rp250 million segment (October 2024: 77.3%). The official 26/279/DKom release body we read does not include the 127 and 6 billion figures; we cite those as Antara’s report.
What we did not find in the primary sources we opened: bank-level operating-cost savings in rupiah, a percentage drop in customer complaints, or an official SLA stated in seconds per transaction. We did not invent those numbers.
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 Bank Indonesia press releases (October 2021, December 2024, January 2025 Board of Governors meeting), an excerpt of the Monetary Policy Report for Q4 2025, and Antara and Bisnis.com coverage that quotes BI. Every figure on this page comes from a source we opened, with the scope we state.
Why this case matters to your organisation
Local finance teams, regional state enterprises, logistics operators and public services often depend on interbank transfers for payroll, vendors and collections. Once national retail rails are widely used, the leadership question is no longer “does instant transfer exist in Indonesia?” but “is our system connected reliably, monitored, and owned after go-live?”. The same pattern appears in other national integrations — including the separate case study on SATUSEHAT.
Reading the case through Diagnose, Deliver, Operate
Three questions in order. What is the state of the core systems, the participation model and reconciliation ownership? That is the ground of Diagnose. How do you connect channels to a shared standard with tests and acceptance criteria? See system integration and APIs and Deliver. Who keeps a 24/7 service healthy when volume rises? That is Operate.
If you are weighing an up-front mapping before a large integration budget, we discuss it in When an organisation needs a paid Diagnose before building a system.
Limits of this analysis
We did not interview Bank Indonesia or participant banks. We did not audit participant transaction logs. We did not fully download every participant-list PDF appendix in this session. The figures of 127 participants and a cumulative 6 billion transactions / more than Rp16 thousand trillion come from Antara quoting BI, not from the main body of press release 26/279/DKom that we read. Treat this page as material for leadership discussion, not as an audit report.
Sources
Accessed on 30 September 2026 (Jakarta time).
- Bank Indonesia, Bank Indonesia Launching BI-FAST in December 2021, No. 23/270/DKom, 22 October 2021.
- Bank Indonesia, Bank Indonesia Sediakan Tiga Layanan Baru BI-FAST, No. 26/279/DKom, 21 December 2024.
- Bank Indonesia, BI-Rate Turun 25 bps Menjadi 5,75%..., No. 27/8/DKom, 15 January 2025 (2024 BI-FAST performance).
- Bank Indonesia, Laporan Kebijakan Moneter Triwulan IV 2025 (Q4 2025 BI-FAST volume and value).
- ANTARA, BI hadirkan tiga layanan baru BI-Fast mulai 21 Desember 2024, 21 December 2024 (quoting BI on participants, cumulative transactions, share).
- Bisnis.com, Transaksi QRIS dan BI-Fast Tumbuh Pesat sepanjang 2024, 15 January 2025 (media corroboration of the RDG figures).
- Bank Indonesia launch release 21 December 2021 (No. 23/334/DKom) — title and the 21 Batch 1 go-live participants figure cited from BI release search results; the full EN page body could not be re-downloaded in this session.