CRING! Indonesia payment facilitator for banking ecosystem powered by SPE is a modern payment facilitator that enables businesses, platforms, and merchants to accept and manage payments seamlessly — all through a single, secure API.

Our mission is to simplify digital payments across Indonesia by offering scalable and developer-friendly tools for accepting payments (e.g., QRIS, virtual accounts, fund transfer) and managing settlements, notifications, and more.

🎯 What CRING! Offers

CRING! provides a unified API platform for seamless access to multiple financial products and services from various banks in Indonesia.

Core Offerings

• 🔍 Bank Account Validator
  Instantly validate bank account numbers using connected partner banks.
• 📱 QRIS (Quick Response Code Indonesian Standard)
  Generate dynamic QR codes for payments, enabling standardized QR-based transactions across ecosystems.
• 🏦 Virtual Account (VA) Services
  Create, manage, and track Virtual Accounts integrated with banks.
• 💸 Fund Transfer
  Send money to bank accounts across all major Indonesian banks.
• 🔐 Secure API Gateway
  Token-based authentication, IP whitelisting, and centralized logging ensure secure and monitored communication between clients and banking partners.
• 📊 Centralized Logging
  All API requests and responses (including unauthorized attempts) are logged to database, enabling detailed analytics and auditing.

Integration Benefits

• One-time integration for multiple banks and services
• Simplified onboarding and credential management
• High availability and scalable API infrastructure
• Suitable for Payment Facilitators, Aggregators, and Institutional Clients
• Secure Transaction Processing

🔧 API

The CRING! API is built on REST, uses standard HTTP status codes, and returns JSON-formatted responses. We designed it with simplicity and flexibility in mind — enabling you to integrate quickly and focus on growing your business.

🧭 CRING! Context

CRING! acts as a centralized API gateway that connects clients (partners) with multiple banking services through a single integration point. The system enables clients to access various financial products—such as QRIS payments, Virtual Accounts (VA), Fund Transfer and Bank Account Validation— without needing to integrate separately with each bank.

In the context diagram:

• 👤 Client refers to third-party systems or merchants that use CRING! to perform financial operations.
• 🟣 CRING! is the platform that handles authentication, routing, logging, and service abstraction.
• 🏦 Banks represent various partner banks which serve as the financial backbone for each product type.

The client sends API requests to CRING! for specific services (e.g., generating a QRIS, creating a VA, creating a Fund Transfer or Validating a bank account). CRING! will then forward the request to the appropriate bank according to the product type and return the result back to the client.

Follow this step-by-step guideline to begin integrating with our API.

1️⃣ Merchant Onboarding

New merchants will be onboarded through our official onboarding process in https://partner.cring.id/ which includes:

• Submitting business information (company details, PIC, contact, etc.)
• Document verification (e.g., NIB, NPWP, legal documents)
• Whitelist IP in the CRING! system

Once onboarding is successful, a verification email will be sent to the merchant's registered PIC to activate their CRING! Portal account.

2️⃣ Email Verification

The merchant PIC must verify their email using the link provided in the onboarding email. After successful verification, they will be able to log in to the CRING Portal.

3️⃣ Getting API Credentials

API credentials (client_id and client_secret) can be obtained through:

• The CRING Portal integration section after login
• Or manually provided by the CRING admin via email (upon request)

These credentials must be stored securely, as they are used to authenticate with the CRING API.

4️⃣ Retrieve Access Token

Use your credentials to obtain an access token from our token endpoint Generate Access Token.

Upon successful onboarding, each client will receive a set of credentials for secure API access, consisting of:

• Client ID – Unique identifier for the client
• Client Secret – Secret used for API authentication
• Base URLs for each environment (Sandbox and Production) These credentials are used with the OAuth 2.0 Client Credentials Grant flow. Authentication is performed using Basic Auth, with the client_id as username and the client_secret as password.

⚠️ Never expose your credentials publicly. Store them securely and rotate them periodically.

Always match the credentials with the appropriate base URL based on your environment.

CRING! provides a simulation of payment processes for Virtual Account and QRIS. It allows users to test payment scenarios, verify integration workflows, and ensure system compatibility without interacting with live payment environments.

Features:

• Virtual Account Simulation: Check detail Virtual Account transactions, paid Virtual Account.
• QRIS Simulation: Simulate QRIS payments with transaction data.
• Secure Testing Environment: Operates in a sandbox environment, ensuring no real financial transactions are processed. Developers can use this simulator to validate their payment integration before moving to the production environment.

Link to Simulator Payment https://simulator-cring.spesandbox.com

When integrating with CRING!, you may encounter errors during your API requests. These errors can generally be grouped into the following categories:

Content errors occur when the data in the API request is invalid in some way. These errors typically return an HTTP response with a 4xx status code. For example:

• 401 Unauthorized: This error occurs if an invalid API key is provided.
• 400 Bad Request: This may appear if a required parameter is missing or if the request body is malformed.

Network errors occur due to communication issues between the client and the server. These errors can include low-level issues, such as socket timeouts or connection problems. For example:

• A client might experience a timeout while waiting for a response from CRING!'s servers.
• A response may never be received if the connection is prematurely closed. These types of errors may not indicate that the request would have been successful under normal circumstances, as they could mask another issue.

Server errors occur when there is a problem on CRING!'s servers. These errors return an HTTP response with a 5xx status code. While CRING! aims to minimize the occurrence of these errors, your integration should be prepared to handle them gracefully. For example:

• 500 Internal Server Error: A general error indicating that something went wrong on the server side.
• 502 Bad Gateway: Indicates that CRING!'s server is unavailable or misbehaving.

The appropriate error handling approach depends on the type of error encountered:

• For content errors, you should check the API documentation for required parameters and correct the request data accordingly.
• For network errors, consider implementing retry logic with exponential backoff to mitigate transient communication problems.
• For server errors, retrying the request with appropriate error handling mechanisms is recommended, as server errors may be temporary.

The following table summarizes the response codes you may encounter when using CRING!'s APIs. Each code includes a description of the error and its potential cause.

CRING provides a real-time Bank Account Validator API that allows clients to validate bank account numbers before initiating transactions. This feature is essential for ensuring that payment instructions are accurate, reducing failed transfers, and enhancing user confidence.

✅ Use Cases

• Validating destination account before fund disbursement
• Checking account status (e.g., Active, Dormant, Closed)
• Preventing human error and mistyped account numbers

CRING! supports QRIS (Quick Response Code Indonesian Standard) — a standardized QR code system mandated by Bank Indonesia to facilitate seamless and interoperable QR-based payments across Indonesia.

✅ Supported Acquirer Banks

CRING! currently supports QRIS acquiring via the following banks:

• Bank BTN (Bank Tabungan Negara)

This means that merchant QRIS issued via CRING! will be processed through these banks as acquirers, ensuring compatibility with a wide range of customer payment applications and wallets across Indonesia.

🔐 QRIS Features on CRING!

• Fully compliant with Bank Indonesia’s QRIS specification
• Supports static and dynamic QR generation
• Supports merchant-presented mode (MPM)
• Secure transaction processing through certified acquiring banks
• Fast settlement and reporting with acquirer bank partners

🔧 Integration Notes

You can request a QRIS via the POST {{baseUrl}}/qr endpoint using your access token. Merchants onboarded through CRING! will automatically be mapped to one of the supported acquiring banks depending on the onboarding configuration and location.

⚠️ Important

• Make sure your merchant is successfully onboarded before requesting QRIS.
• QRIS payments will only be routed through supported acquirer banks.

CRING provides a seamless Virtual Account Credit service that allows partners to disburse funds directly to a designated virtual account across supported banks. This is typically used for:

• Commission payouts
• Loan disbursements (P2P or cooperative)
• Salary or incentive distribution
• Top-up balance to closed-loop systems

✅ Supported Banks

CRING currently supports VA Credit to the following bank providers:

• Bank BNI
• Bank Permata
• Bank BTN
• Bank BRI

The following table summarizes the response codes you may encounter when using CRING!'s APIs. Each code includes a description of the error and its potential cause.