QRIS QR codes
QRIS, the Quick Response Code Indonesian Standard, is the national QR payment standard introduced by Bank Indonesia for QR code payments in Indonesia. It lets customers scan one standardized QR payment code from participating payment applications and funding sources.
A QRIS code used for settlement is not just a generic QR image. Merchant-presented QRIS codes are normally issued through a licensed payment service provider, acquirer, bank, wallet, EDC, POS, or QRIS provider workflow that can identify the merchant and handle transaction processing.
Use QR Code Crafter for the surrounding static work: planning QRIS signage, checking print size and quiet zone, preparing fallback instructions, linking to provider setup pages, exporting labels, and documenting whether the merchant uses static MPM or dynamic MPM.
QRIS QR codes Generator
Plan QRIS QR codes workflows with guidance on static QR destinations, export formats, scan testing, and print or digital rollout. Static QR code.
Key decisions
Static MPM QRIS for reusable signs
Static Merchant Presented Mode usually uses one merchant QRIS sticker or printout. The customer scans, enters the payment amount, reviews the recipient, and confirms in their payment app.
Dynamic MPM QRIS for transaction-specific codes
Dynamic Merchant Presented Mode is generated by a device, POS, EDC, mobile app, or provider API after the merchant enters the transaction value.
Provider-issued merchant identity
Official QRIS payment codes should come from a licensed PSP or acquirer so the merchant identity, settlement account, limits, and transaction status are handled correctly.
Print and instruction support
QR Code Crafter can help create static instruction signs, labels, fallback URLs, print proofs, and QRIS setup handoff materials without claiming to replace provider QRIS issuance.
QRIS workflow choices
| QRIS need | Use this workflow | Check before publishing |
|---|---|---|
| Reusable counter sticker | Provider-issued static MPM QRIS code placed on printed signage | Scan the final sticker and confirm merchant name, amount entry, and payment app behavior. |
| Order-specific checkout | Dynamic MPM QRIS generated by POS, EDC, mobile app, or provider API | Confirm the amount is embedded or locked according to the provider workflow. |
| Remote invoice or catalogue payment | QRIS Tanpa Tatap Muka or provider-supported remote payment flow | Make sure the provider permits the QRIS code to be shared in that channel. |
| Customer-presented payments | Consumer Presented Mode where the customer shows a QRIS barcode for the merchant to scan | Use the merchant scanner or POS flow supplied by the payment provider. |
| International traveller acceptance | Existing QRIS merchant code if the PSP supports QRIS Cross-Border | Ask the merchant PSP whether cross-border acceptance is enabled. |
| Marketing and analytics | A clear landing page or instruction page before the provider payment step | Do not alter an official payment QRIS payload with tracking parameters. |
| Print production | Provider QRIS code placed into SVG, PDF, or EPS artwork with readable instructions | Protect the quiet zone, contrast, size, and fallback payment guidance. |
Use QRIS without misrepresenting the payment flow
QRIS helps standardize Indonesian QR payments, but transaction acceptance still depends on the payment provider and merchant registration.
Get the official QRIS code from the provider
Start in the merchant bank, wallet, PSP, acquirer, EDC, POS, or QRIS provider that controls the settlement account. Use their QRIS output for real payment collection.
Label static and dynamic flows clearly
Tell staff whether the printed code is reusable static MPM or whether each checkout requires a new dynamic QRIS code from a device or app.
Show readable merchant context
Place business name, branch, counter, invoice, or table information beside the QRIS artwork so customers can verify the payment screen before confirming.
Keep QRIS payloads intact
Do not modify a provider-issued QRIS payload for styling, analytics, or redirects. Put tracking and explanatory content on separate static QR codes or landing pages.
Prepare QRIS signage for reliable scans
Payment QR signage must work under real counter, invoice, delivery, and event conditions.
Use production-safe artwork
Place the provider QRIS image in print artwork with enough size, contrast, and quiet zone. Export signs and labels as SVG, PDF, or EPS when possible.
Test in Indonesian payment apps
Scan the final printed or digital proof in the payment apps customers actually use, then confirm merchant name, amount entry or amount lock, and payment confirmation steps.
Add fallback instructions
Include what the customer should do after scanning, who to ask for help, and whether the payment amount is entered by the customer or generated by the merchant.
Replace stale provider codes
Regenerate and reprint QRIS signage if the merchant account, branch, PSP, provider app, settlement details, or provider-issued QRIS code changes.
QRIS signage checklist
- Confirm the QRIS code was issued by the correct licensed PSP, acquirer, bank, wallet, POS, or provider.
- Identify whether the flow is static MPM, dynamic MPM, remote QRIS, or customer-presented QRIS.
- Show the business name, branch, table, order, or invoice context beside the QR code.
- Keep the official QRIS payload unchanged; use separate QR codes for tracking or setup instructions.
- Scan the final artwork in real payment apps before printing or publishing.
- Use SVG, PDF, or EPS for production artwork when placing QRIS on signs, stickers, menus, receipts, or invoices.
- Reprint the asset when the provider-issued QRIS code or merchant setup changes.
Guides: print
QRIS QR codes should be treated as a publishing workflow, not only a generated image. Confirm the destination, choose the export format, test the finished asset, and assign an owner before it appears in public material.
Before using QRIS QR codes in print, packaging, signage, email, documents, apps, or automation, keep a release note with the encoded value, file name, export format, placement, owner, and test result. That record makes later corrections possible.
URL QR code: HTTPS
For QRIS QR codes, verify that the encoded URL, contact detail, payment instruction, file, or app action is accurate, controlled by the right team, available on mobile, and appropriate for the people who may scan it.
Select format
Keep SVG, PDF, or EPS masters for print, packaging, signs, and design tools. Use PNG, JPG, WebP, or SVG for websites, email, documents, and digital placements, and avoid unexpected compression of the final code.
scan
Scan the browser preview, downloaded file, placed layout, exported PDF, CMS upload, email preview, and physical proof from realistic distances, angles, lighting, and devices before release.
Company
Record the QR owner, destination, source file, export format, placement, publish date, test devices, review date, and replacement trigger so long-lived static codes remain trustworthy.
QR code API
When many QR files are needed, use consistent names, manifest checks, OpenAPI or WebMCP parameters, and output-format validation before handing assets to design, print, or content teams.
static vs dynamic QR codes
Review QRIS QR codes after campaign changes, rebrands, domain moves, payment-detail updates, app-store changes, document migrations, or analytics changes so public QR codes do not point to stale or unsafe destinations.
Feedback
Add readable destination text, a short URL, support contact, or printed instruction where scanning is business-critical, accessibility-sensitive, or likely to happen with poor connectivity.
Accessibility
Place nearby text that explains the scan action, keep contrast high, avoid tiny placements, and ensure the destination works with mobile browsers, screen readers, reduced-motion settings, and keyboard navigation.
How to prepare QRIS QR code signage
- 1
Get the provider-issued QRIS code
Export or download the official QRIS asset from the merchant PSP, bank, wallet, POS, EDC, acquirer, or provider system.
- 2
Place it into clear signage
Add merchant context, amount instructions, fallback text, and enough white space around the QRIS code for reliable scanning.
- 3
Proof, scan, and publish
Test the final print or digital proof in payment apps, confirm the displayed merchant and amount behavior, then publish the approved asset.
Frequently asked questions
Can QR Code Crafter generate an official QRIS payment code?
No. Official QRIS payment codes should be issued through a licensed PSP, acquirer, bank, wallet, EDC, POS, or QRIS provider. QR Code Crafter helps prepare supporting static signs, print assets, and customer instructions.
What is the difference between static and dynamic QRIS?
Static MPM usually reuses one merchant QRIS printout and the customer enters the amount. Dynamic MPM is generated for a transaction by a device, POS, app, or provider workflow, usually after the merchant enters the amount.
What is QRIS CPM?
Consumer Presented Mode means the customer displays a QRIS barcode in their payment app and the merchant scans it. This requires the merchant scanner or POS workflow supplied by the provider.
Can I add tracking to a QRIS payment code?
Do not alter an official QRIS payment payload with tracking parameters. If measurement is required, use a separate landing page or instruction QR code before the provider payment step.
Which file format should I use for QRIS signs?
Use provider-approved source artwork where available. For surrounding signs, labels, menus, receipts, and invoice layouts, SVG, PDF, or EPS usually stay sharp through production.