Integrasi SNAP

The National Standard for Open Payment API Indonesia (SNAP) is a national standard developed by Bank Indonesia to improve the efficiency, security, and interoperability of the payment system in Indonesia. SNAP is designed to provide convenience and maximum benefits for merchants using Espay, with the following main objectives:
  1. Simplifying payment integration, as it has a single standard for various payment methods.
  2. Ensuring security and compliance with regulations set by Bank Indonesia.
  3. Supporting innovation in payment services, enabling development and adaptation to new technologies.
For more information, visit the ASPI website at ASPI – Indonesia.

Procedure for Submitting the SNAP Recommendation Letter

The procedure that merchant must follow to obtain the SNAP recommendation letter from Bank Indonesia is as follows:

1. Testing the SNAP Developer Site
Testing the SNAP Developer Site is conducted to ensure that the developed services comply with technical and security standards, data standards, and the SNAP technical specifications.
2. Functional Testing
Functional Testing is performed to verify that the services you have developed operate by the SNAP specifications.
3. SOP Guide Document and Explanation Matrix
The SOP Guide Document and Explanation Matrix ensure that merchants SNAP service integration process is accurate, efficient, and secure.

The SNAP Developer Site Testing, Functional Testing, SOP Guide Document, and Explanation Matrix results can be submitted to the Espay team.

Learn the Procedures for Testing and Document Preparation.

Services to Be Tested for SNAP

Various services provided by Espay must be tested with SNAP. Before conducting SNAP Developer Site Testing, merchants must identify or determine which services must be tested. Merchants can also consult the technical team regarding the services required to be tested in the SNAP process.
Product Service
Code		 Service Name Flow Description
Payment Gateway
24
API Virtual Account - Inquiry
Lihat disini
Payment Gateway
25
API Virtual Account - Payment
Lihat disini
Payment Gateway
26
API Virtual Account - Inquiry Status
Lihat disini
Payment Gateway
31
API Virtual Account - Delete VA
Lihat disini
Payment Gateway
54
API Direct Debit Payment (Payment Host to Host)
Lihat disini
Payment Gateway
47
API Generate QR MPM
Lihat disini
Disbursement
11
API Balance Inquiry
Lihat disini
Disbursement
14
API Bank Statement
Lihat disini
Disbursement
15
API Internal Account Inquiry
Lihat disini
Disbursement
16
API External Account Inquiry
Lihat disini
Disbursement
17
API Trigger Intrabank Transfer
Lihat disini
Disbursement
18
API Trigger Interbank Transfer
Lihat disini
Disbursement
22
API Transfer RTGS
Lihat disini

Procedures for Testing and Document Preparation

1. Testing the SNAP Developer Site
Alur Pengujian Developer Site SNAP

The SNAP Developer Site is a portal the Indonesian Payment System Association (ASPI) provides to facilitate merchants’ testing of SNAP services in sandbox environment. This testing ensures that your developed services comply with technical and security standards, data standards, and SNAP technical specifications. The testing only involves interactions between the SNAP Developer Site and the merchant without direct connection to Espay.

Visit the Developer Site Management Guidelines at Developer Site Management Guidelines

Example:

Merchant A wants to accept payments using QRIS. Merchant A integrates its system with the Espay Payment Gateway to do this and uses the Espay payment page feature. In this integration, Merchant A uses three primary services:

  1. Inquiry
  2. Payment
  3. Payment Host to Host
Therefore, when testing on the SNAP Developer Site, Merchant A only tests the following three services:
  1. API Virtual Account – Inquiry
  2. API Virtual Account – Payment
  3. API Direct Debit Payment (Payment Host to Host)

Types of SNAP Developer Site Testing

When conducting testing on the SNAP Developer Site, merchants must understand the flow of each service being used. The differences in these flows determine which features should be used for testing. There are two types, which are:
  1. Client Simulator
The Client Simulator is a feature in the Bank Indonesia (BI) Developer Site used to test services that interact between the ASPI Portal and the Merchant. Merchants can identify which services use the Client Simulator feature by referring to the service flow from which is provided in the Services to Be Tested for SNAP.
  1. Pengujian Aplikasi
Pengujian Aplikasi is a feature in the Bank Indonesia (BI) Developer Site used to test services with a scenario where the merchant initiates interaction with the ASPI Portal. Merchants can identify which services use the Application Testing feature by referring to the service flow from which is provided in the Services to Be Tested for SNAP.
Please download the User Guide – Developer Site to learn the technical steps for testing.
2. Functional Testing

Functional Testing is the process of ensuring that the integration of SNAP (National Standard for Open API Payment) services from Bank Indonesia operates according to the established technical specifications. This testing aims to ensure that all functions and features available in SNAP services work properly and securely.

The Espay Payment Gateway team will provide you with test cases customized based on the services you use. You can perform the testing using tools such as Postman. Unlike SNAP Developer Site testing, the interaction in this testing process occurs between the Espay Payment Gateway and you (the Merchant). Please download the Functional Testing Example.

3. Create the SOP Guide and Explanation Matrix documents
SOP Guide
The SOP Guide is a document that contains procedures and documentation for the development, modification, and maintenance of the Open API Payment System (SOP). This document should cover at least 8 aspects, including:
  1. Needs analysis and impact analysis
  2. Design
  3. Development
  4. Internal functionality testing
  5. Functionality testing with collaborating parties
  6. System security testing
  7. Implementation
  8. Preventive and corrective maintenance
You can submit an existing SOP Guide (that your company already has) or follow the available template. The SOP Guide format consists of:
  1. A cover page with the title and company logo.
  2. An approval page signed or initialed by an authorized official.
  3. A content page covering the 8 aspects (Needs analysis and impact analysis; Design; Development; Internal functionality testing; Functionality testing with collaborating parties; System security testing; Implementation; Preventive and corrective maintenance).
Explanation Matrix

The Explanation Matrix contains a summary of the SOP Guide, complete with references to the chapters and pages of the document specifically related to the SOP.

Please download Template – SOP Guide and Template – Explanation Matrix.

Scroll to Top