--- title: SNAP Introduction slug: en/nicepay-api-snap-introduction description: Information about SNAP API introduction provided by NICEPAY icon: {"faIcon":"fa-solid fa-book"} createdAt: 2026-10-30T07:55:34.309Z --- # SNAP Overview SNAP (*Standar Nasional Open API Pembayaran) *is the standard payment API in Indonesia that established by Bank Indonesia and developed together with ASPI (*Asosiasi Sisten Pembayaran Indonesia*). This standard aim for the payment gateway provider like NICEPAY can communicate in the similar way. Based on [Bank Indonesia dev portal](https://apidevportal.bi.go.id/snap), SNAP regulate three main things: - **Standard format and URL API**. Endpoint path, field name, and response structure follow the similar specification for every provider. - **Security standard**. Every request need Access Token and digital Signature. - **Structured response code**. Every code contain status information, service, and case. # SNAP API Request Component The following is some component that contain in every SNAP API request. | **Component** | **Function** | | -------------------- | ------------------------------------------------------------------------------------------- | | **Endpoint** | Standard URL `/nicepay/v1.0/access-token/b2b` for request token. | | **Access Token** | Access authorization, valid for 15 minutes, sent as Authorization: Bearer \{`accessToken`}. | | **Signature** | Digital signature on `X-SIGNATURE` header to ensure integrity and non-repudiation. | | **Timestamp** | Header `X-TIMESTAMP` with format ISO-8601, also sign to prevent reuse of old request. | | **Partner Identity** | `Client ID` from NICEPAY, sent on `X-CLIENT-KEY` header | | **Body** | Transaction data in JSON format with field name based on SNAP standard. | | **Response code** | 7 code number explain request result. | :::hint{type="info"} Detail to grain Access Token and create Signature could be seen on page. ::: ## Common Used General | **Header** | **Used on** | **Remark** | | --------------- | -------------------- | ---------------------------------------------------------------------------------- | | `Content-Type` | All request | `application/json` | | `X-TIMESTAMP` | All request | Request time, `ISO-8601` with timezone GMT+7, example `2024-12-31T10:11:40+07:00` | | `X-CLIENT-KEY` | Request Access Token | `Client ID` from NICEPAY | | `X-SIGNATURE` | All request | Digital signature created by Merchant | | `Authorization` | Request service | Bearer \{`accessToken`} | | `X-PARTNER-ID` | Request service | `Client ID` from NICEPAY | | `X-EXTERNAL-ID` | Request service | Unique reference number for every request created | | `CHANNEL-ID` | Request service | `Client ID` add with `01` | # Understanding SNAP Response Code SNAP response code consist of **7 number digit** with three parts: | **BPart** | **Total Digit** | **Definition** | | ------------ | --------------- | ---------------------------------------------------------------------------- | | SHTT status | 3 | Example:
`200` Success
`400` Wrong Request
`401` Unauthorized | | Service code | 2 | MShowing the called service | | Case code | 2 | Explain detail result | CExample: `2007300` - `200` is status HTTP success. - `73` is service code for Access Token. - `00` is success case. :::hint{type="info"} Please visit page to view service code list and page to view the complete list of response code ::: # NICEPAY Service's SNAP Support | **Service** | **Availability API** | | --------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Virtual Account** | - [Registration - API Virtual Account SNAP](docId\:Rfwa2zCRE7TNjXWKr-j0-)
- [Notification - API Virtual Account SNAP](docId\:oljzaxWvjeIdvPPtpFwes)
- [Check Status Transaction - API Virtual Account SNAP](docId\:QDN7CGVv26s2XEibfWg1U)
- [Cancel - API Virtual Account SNAP](docId\:i-K2pbXQYAmba7zW0aYJM) | | **E-Wallet (Direct Debit)** | - [Account Binding - API E-Wallet (Direct Debit) SNAP](docId:9xl2y9tokXGTMZsU8v8l0)
- [Registration - API E-Wallet (Direct Debit) SNAP](docId\:U__7u4PnTx3_eSWeZ-94m)
- [Check Status Transaction - API E-Wallet (Direct Debit) SNAP](docId\:za7aN0HE8C3-2OiXvdlNa)
- [Refund Transaction - API E-Wallet (Direct Debit) SNAP](docId\:Y-cGH6ylEK9h3FgMdXuqZ)
- [Notification Transaction - API E-Wallet (Direct Debit) SNAP](docId\:Xc8PGDMhNmNjivIZ4Vm8V) | | **QRIS** | - [Registration - API QRIS SNAP](docId\:FsuuZk9ZHP7pRzFCi32fm)
- [Check Status Transaction - API QRIS SNAP](docId\:a0i6Lo4dvBo6Ih5Ql6nDA)
- [Refund Transaction - API QRIS SNAP](docId\:uZpKssMvaM0skERr1Fn9B)
- [Notification - API QRIS SNAP](docId\:LF56SFpVT2uVqyISimjRF) | | **Payout (Disbursement)** | - [Registration - API Payout (Disbursement) SNAP](docId\:eonRZaDi86qH4vIEcXRrs)
- [Approve Transaction - API Payout (Disbursement) SNAP](docId:75T6p-QRSteur4iECzRJe)
- [Reject Transaction - API Payout (Disbursement) SNAP](docId\:ralDhY1OmjyJYEy_J1xll)
- [Cancel Transaction - API Payout (Disbursement) SNAP](docId\:CedmfUI42mOyU8_Iy9j2q)
- [Inquiry - API Payout (Disbursement) SNAP](docId\:Ge22wm18E02qRwDgBWMz_)
- [Balance Inquiry - API Payout (Disbursement) SNAP](docId\:LFT65B6bexNuG9__o_evu)
- [Notification - API Payout (Disbursement) SNAP](docId\:pAfKxCNZk_EeO2ZVZGDwD) | # Difference with Non-SNAP NICEPAY API Difference between API NICEPAY SNAP with Non-SNAP is on the authentication and response format. Every SNAP request use Access Token and digital Signature also SNAP response have parameter in Bank Indonesia standard (like `responseCode` parameter owned by Bank Indonesia with `responseCd` parameter owned by NICEPAY). :::hint{type="info"} Please check [Implementasi SNAP](docId:9NC4zMt_CIYOOoQ3RweUm) for the complete guide of implementation and migration. :::