BI-SNAP Gateway

M‑SNAPEasy, Secure Integration Through Open Banking

M-SNAP is a BI-SNAP agent with a service provider for institutions that offer services and a service consumer for those that use them — covering the BI-SNAP ecosystem end to end.

Schedule a DemoSee How It Works

Collaboration and integration are the backbone of modern banking, but…

Integration isn’t easy.

Connecting banks, fintechs and other institutions the conventional way runs into the same four problems again and again.

  1. Difficult and slow

    Interconnection documentation is usually not published widely.

  2. Expensive

    A new communication channel often needs new infrastructure to be procured.

  3. Not standardized

    Each institution uses formats that only work inside that institution.

  4. Not secure

    Conventional connections rely on security at the infrastructure level only.

01 Difficult and slow

Interconnection documentation is usually not published widely.

02 Expensive

A new communication channel often needs new infrastructure to be procured.

03 Not standardized

Each institution uses formats that only work inside that institution.

04 Not secure

Conventional connections rely on security at the infrastructure level only.

The answer

What is open banking?

Open banking is a system where banks and financial institutions share their data and services securely with each other, using Open APIs.

Its role in the digital economy

  1. 01

    Speeds up economic digitalization

    Helps the economy adopt digital technology faster, making financial services more efficient and easier to reach.

  2. 02

    Widens access for MSMEs

    Makes financial services easier to access for micro, small and medium businesses, helping them grow.

  3. 03

    Increases financial inclusion

    Helps bring unbanked people into the formal economy and financial system.

  4. 04

    Drives innovation and competitiveness

    Encourages banks and fintechs to develop new products and services, making the market more competitive.

  5. 05

    Reduces shadow-banking risk

    Better integration between formal financial institutions and fintech reduces the risk of unregulated banking practices.

01 Speeds up economic digitalization

Helps the economy adopt digital technology faster, making financial services more efficient and easier to reach.

02 Widens access for MSMEs

Makes financial services easier to access for micro, small and medium businesses, helping them grow.

03 Increases financial inclusion

Helps bring unbanked people into the formal economy and financial system.

04 Drives innovation and competitiveness

Encourages banks and fintechs to develop new products and services, making the market more competitive.

05 Reduces shadow-banking risk

Better integration between formal financial institutions and fintech reduces the risk of unregulated banking practices.

Source: Indonesia Payment System Blueprint (BSPI) 2025.

Open banking in Indonesia

BI‑SNAP is now the standard for payment APIs.

Open banking is one of the five initiatives in Bank Indonesia’s 2025 payment system blueprint, and BI-SNAP is how it is put into practice.

2019

Consultative paper

Bank Indonesia publishes its consultative paper on open banking.

2020

Open API in digital payments

Open APIs start to be implemented in the digital payment ecosystem.

2021

PADG No. 23/15/PADG/2021

Bank Indonesia sets the BI-SNAP standard, mandatory for every payment Open API.

2021–2025

Wider rollout

Open API implementation expands, with BI-SNAP applied in stages until 2025.

  1. 2019

    Consultative paper

    Bank Indonesia publishes its consultative paper on open banking.

  2. 2020

    Open API in digital payments

    Open APIs start to be implemented in the digital payment ecosystem.

  3. 2021

    PADG No. 23/15/PADG/2021

    Bank Indonesia sets the BI-SNAP standard, mandatory for every payment Open API.

  4. 2021–2025

    Wider rollout

    Open API implementation expands, with BI-SNAP applied in stages until 2025.

Four open banking standards in the blueprint

  • 1Technical API standard
  • 2Security API standard
  • 3Open API contract standard
  • 4Data standard

The same move around the world

Australia
Competition and Consumer Act (2010)
Japan
Amendment of the Banking Act (2017)
Singapore
Finance as a Service: API Playbook (2016)
Hong Kong
Open API Framework
European Union
Payment Services Directive 2 (PSD2)
United Kingdom
Open Banking Standard

Source: Bank Indonesia.

Transactions

80+

different transactions supported today

M-SNAP currently supports more than 80 transactions, including:

  • Balance Inquiry
  • Transaction History
  • Account Binding
  • Card Registration
  • Direct Debit
  • Intrabank
  • Interbank
  • SKNBI
  • RTGS
  • Bulk Transfer
  • Virtual Account
  • QRIS MPM
  • Direct Debit BI-FAST
  • QRIS CPM

And more — ask us for the full list.

M-SNAP currently supports more than 80 transactions, including:

Account information

  • Balance Inquiry
  • Transaction History

Account & card

  • Account Binding
  • Card Registration
  • Direct Debit

Credit transfer

  • Intrabank
  • Interbank
  • SKNBI
  • RTGS
  • Bulk Transfer
  • Virtual Account
  • QRIS MPM

Debit transfer

  • Direct Debit BI-FAST
  • QRIS CPM

And more — ask us for the full list.

Two roles, one platform

Provide services, consume them, or both.

M-SNAP covers both sides of BI-SNAP. Switch between the two roles to see how each one works.

M-SNAP as a service provider

Bank Transaction API (BTA) opens your services as APIs for many consumers to use.

  • One provider can serve many consumers.
  • Every incoming request passes the security layer before it reaches the service layer.
  • A developer portal for your consumers.
  • A back office for your own teams.

Who are the providers?

  • Banks
  • E-wallet providers
  • Other institutions that manage funds

Example: BI-SNAP provider in a bank

Inside the bank’s environment, BTA opens data and services securely for many BI-SNAP consumers. Registering a new consumer takes minimal configuration.

Architecture

One API management layer in front of your systems.

Every request passes through Matajari API Management, layer by layer, before it reaches your core banking and other systems.

Matajari API Management

  1. 1 Load balancer
  2. 2 Security adaptor 2
    M-SNAP Auth Service (OAuth 2.0)Other OAuth 2.0 / security module
  3. 3 M-SNAP services BI-SNAP 4
    API GatewayDeveloper PortalAdmin PortalAnalytics
  4. 4 Communication interface 5
    ISO8583ISO 20022JSONXMLOther formats

Your systems

Core bankingCard managementFraud detectionOther services

Matajari API Management

  1. Load balancer

  2. Security adaptor

    M-SNAP Auth Service (OAuth 2.0)Other OAuth 2.0 / security module

  3. M-SNAP services

    BI-SNAP
    API GatewayDeveloper PortalAdmin PortalAnalytics

  4. Communication interface

    ISO8583ISO 20022JSONXMLOther formats

Your systems

Core bankingCard managementFraud detectionOther services

Security

Security that complies with BI‑SNAP.

Choose a standard to see where it protects a request.

  1. POST /v1.0/balance-inquiry HTTP/1.1
  2. Host api.yourbank.example
  3. Authorization Bearer eyJhbGciOiJSUzI1NiJ9…
  4. X-TIMESTAMP 2025-05-15T10:00:00+07:00
  5. X-SIGNATURE 9f2c4e…d81b7e
  6. Content-Type application/json
  7. { "partnerReferenceNo": "2025051500001", "accountNo": "••••••7788" }
  8. Extra verification: one-time code confirmed (2FA)
  9. Sent over a TLS 1.3 channel
POST /v1.0/balance-inquiry HTTP/1.1Host: api.yourbank.exampleAuthorization: Bearer eyJhbGciOiJSUzI1NiJ9…X-TIMESTAMP: 2025-05-15T10:00:00+07:00X-SIGNATURE: 9f2c4e…d81b7eContent-Type: application/json { "partnerReferenceNo": "2025051500001", "accountNo": "••••••7788"} # Extra verification: one-time code confirmed (2FA)# Sent over a TLS 1.3 channel
Illustration with sample values.

Back office

Manage everything in one place.

M-SNAP comes with the tools your team needs to run BI-SNAP services day to day.

Service management

Monitor, create, manage and modify services.

  • api-card-registration M‑SNAP
  • api-verify-otp-direct-integration M‑SNAP
  • api-balance-inquiry M‑SNAP
  • api-bank-statement M‑SNAP
  • api-internal-account-inquiry M‑SNAP
ServiceTag
api-card-registrationM‑SNAP
api-verify-otp-direct-integrationM‑SNAP
api-balance-inquiryM‑SNAP
api-bank-statementM‑SNAP
api-internal-account-inquiryM‑SNAP
Illustration of the back office with sample data.

Frequently Asked Questions

Everything you need to know about M-SNAP.

SNAP is the national Open API payment standard set by Bank Indonesia. Through PADG BI No. 23/15/PADG/2021, Bank Indonesia requires it to be applied in stages (until 2025) to every payment Open API.
Either, or both. Institutions that manage funds — banks, e-wallet providers and others — open their services as a provider (BTA). Fintechs, airlines, hotels and others use those services as a consumer (CTA).
Not hard. As a provider, a new consumer can be registered with minimal configuration. As a consumer, a connection to a new BI-SNAP provider can be added with minimal configuration.
Consumers get a developer portal. Your own IT, admin and business teams get a back office to manage services, routes, microservice connections and transactions, plus analytics.
Core banking, card management, fraud detection and other services, through a communication interface that handles ISO8583, ISO 20022, JSON, XML and other formats.

Ready to Open Your Services with BI‑SNAP?

Tell us whether you want to provide or consume BI-SNAP services, and we will show you how M-SNAP fits.

Contact Us Chat on WhatsApp