Qris Id QRIS Indonesian Payment API
48
AI ReadinessFoundational (D+)48/100
Official vendor OpenAPI document · agent-readyPaymentsPayment ProcessingapiKey2 EndpointsREST
For Agents
Programmatically create qris invoice, check invoice payment status. Covers 2 operations with apiKey authentication.
Use for: I need to qris invoice, I want to check invoice payment status, I want to integrate QRIS Indonesian Payment API into my workflow, Search for available QRIS Indonesian Payment API operations
Not supported: Does not handle communications, crm, or developer tools - use for payments only.
QRIS provides Indonesian QR code-based payment processing. The API allows creating and checking invoice statuses for QR payments. The API exposes 2 endpoints secured with apiKey authentication.
Install Jentic One Beta
Connect the QRIS Indonesian Payment API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the QRIS Indonesian Payment API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fqris.id%2Fqris-id" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fqris.id%2Fqris-id" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with QRIS Indonesian Payment API.
Create QRIS invoice
Check invoice payment status
Access QRIS Indonesian Payment API payments resources via REST API
Use Cases
Patterns agents use QRIS Indonesian Payment API for, with concrete tasks.
★ Payments Operations
Use the QRIS Indonesian Payment API to perform payments operations programmatically. The API provides 2 endpoints covering core functionality including create qris invoice, check invoice payment status.
Call POST /show_qris.php to create qris invoice
Data Retrieval and Monitoring
Query QRIS Indonesian Payment API endpoints to retrieve structured data for monitoring, reporting, or downstream processing. The API returns JSON responses that agents can parse directly, enabling automated data collection workflows.
Query the QRIS Indonesian Payment API API to retrieve current data and verify the response structure
AI Agent Integration via Jentic
AI agents discover and call QRIS Indonesian Payment API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.
Search Jentic for 'create qris invoice', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
2 endpoints — qris provides indonesian qr code-based payment processing.
METHOD
PATH
DESCRIPTION
POST
/show_qris.php
Create QRIS invoice
POST
/checkpaid_qris.php
Check invoice payment status
POST
/show_qris.php
Create QRIS invoice
POST
/checkpaid_qris.php
Check invoice payment status
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Q
QRIS Indonesian Payment API
- Foundational (D+)48/100
100
Foundational Compliance63
Developer Experience & Jentic Compatibility44
AI-Readiness & Agent Experience94
Agent Usability15
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
100
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
99%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
44
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: DSignals: 4
27%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
50%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
15
Security
Trust, risk posture, and security compliance.
Grade: FSignals: 1
15%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the QRIS Indonesian Payment API by hand means appending its apikey query parameter to each call to qris.interactive.co.id and handling the PHP endpoint responses yourself. Through Jentic you install once, import the QRIS Indonesian Payment API from the API Directory, store the API key once, and your agent calls it.
Permission scoping
The QRIS Indonesian Payment API works through operations like show_qris and checkpaid_qris rather than a resource id in the path, so scope by operations: limit the agent to the operations it needs, such as showing a QRIS payment. You choose which operations are in that set, and the agent can call only those.
Credential isolation
Your QRIS API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create a QRIS payment' or 'check whether a payment is paid', and Jentic returns the matching QRIS operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Stripe
Alternative payments API
Choose Stripe when you need a different approach to payments operations
FAQs
Specific to using QRIS Indonesian Payment API through Jentic.
What authentication does the QRIS Indonesian Payment API use?
The QRIS Indonesian Payment API uses an API key passed in the `apikey` query. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I create qris invoice with the QRIS Indonesian Payment API?
Yes. Use the POST /show_qris.php endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the QRIS Indonesian Payment API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I create qris invoice through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create qris invoice'. Jentic returns the matching QRIS Indonesian Payment API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the QRIS Indonesian Payment API have?
The QRIS Indonesian Payment API exposes 2 endpoints covering invoices operations.
Can I limit what my agent is allowed to do with the QRIS Indonesian Payment API?
Yes. Because you run Jentic One yourself, your own rules decide which QRIS operations and credentials the agent may use. The QRIS Indonesian Payment API is scoped by operation rather than by a resource id in the path, so you can allow only the calls the agent needs, such as creating a QRIS invoice with show_qris while withholding checkpaid_qris, or the reverse. The agent can call only the operations you place in that set, and your stored API key is injected at execution time rather than exposed to the agent.
GET STARTED