PromptPay QR codes
PromptPay QR codes are common across Thai mobile banking workflows. QR Code Crafter creates a static payment payload from the identifier and optional THB amount you provide; it does not connect to your bank, verify recipients, process payments, or track scans.
Use this workflow when you need printed or digital payment artwork for a shop counter, market stall, cafe, donation display, invoice, event booth, or service payment handoff. Always scan the finished code in the banking apps your audience uses before relying on it for real payments.
Create a PromptPay QR code
Enter a registered PromptPay identifier, add an optional THB amount, and export a static payment QR code.
Key decisions
Start with a registered PromptPay ID
Use a mobile number, 13-digit citizen or tax ID, or 15-digit e-wallet ID that is already registered for PromptPay receiving.
Static code, direct payment payload
The QR code stores the PromptPay payment payload directly, without a QR Code Crafter account, redirect, expiry, or scan limit.
Print-ready Thai payment assets
Export SVG, PDF, or EPS for signs, receipts, table tents, invoice inserts, and counter cards. Use PNG, JPG, or WebP for digital payment instructions.
PromptPay QR code workflow choices
| Use case | Best payload choice | Check before publishing |
|---|---|---|
| Variable payments | PromptPay identifier without an amount | Make sure payers know the expected total before they scan. |
| Fixed invoice or order amount | PromptPay identifier plus fixed THB amount | Regenerate the static QR code if the amount changes. |
| Public counters and stalls | QR code plus readable business name or identifier | Ask payers to confirm recipient and amount inside their banking app. |
| Donations or community payments | Blank-amount PromptPay QR code with clear surrounding instructions | Use a recipient identifier you are comfortable publishing publicly. |
| Campaign measurement | A landing page you control before payment when analytics are required | Do not add tracking data inside a bank payment payload. |
| Print production | SVG, PDF, or EPS master artwork | Protect the quiet zone and scan the final proof before printing. |
Build a safer PromptPay QR destination
Payment QR codes need visible verification details so scanners can confirm where money is going.
Verify the receiving account first
Scan the QR code in a Thai banking app and confirm the displayed recipient before printing or sharing the artwork.
Show readable payment context
Place the business name, recipient name, identifier, invoice reference, or expected amount beside the QR code.
Avoid private identifiers when unsuitable
Do not publish a personal ID in public materials when a business identifier, e-wallet ID, or payment instruction page is safer.
Separate analytics from payment
Use a landing page before the payment step if measurement is required; keep the PromptPay payload focused on payment details.
Prepare PromptPay QR codes for print and mobile scans
PromptPay QR codes often live on counters, signs, receipts, and table cards where distance, light, and fallback details matter.
Choose production-safe exports
Use SVG, PDF, or EPS for stickers, table tents, invoices, and counter cards. Use PNG, JPG, or WebP for messages and digital payment instructions.
Keep contrast high
Use dark foreground modules on a light background, leave a clear quiet zone, and avoid placing decoration close to the QR code.
Test multiple banking apps
Scan with the banking apps your customers are likely to use, then confirm recipient display, amount behavior, and fallback instructions.
Replace stale printed codes
A static QR code cannot update itself. Regenerate and reprint if the identifier, amount, recipient, or payment instructions change.
PromptPay QR code checklist
- Confirm the PromptPay identifier is registered and controlled by the intended recipient.
- Decide whether the amount should be blank or fixed in THB.
- Show the recipient name or readable payment context beside the QR code.
- Scan the QR code in real Thai banking apps before printing or publishing.
- Use SVG, PDF, or EPS for signs, stickers, invoice inserts, table tents, and receipts.
- Keep sensitive personal identifiers out of public materials unless publishing them is appropriate.
- Regenerate the QR code if the identifier, amount, or printed payment instructions change.
Guides: print
PromptPay 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 PromptPay 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 PromptPay 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 PromptPay 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 make a PromptPay QR code
- 1
Enter the registered PromptPay ID
Use the mobile number, citizen or tax ID, or e-wallet ID that should receive the payment.
- 2
Choose whether to include an amount
Leave the amount blank for variable payments, or add a fixed Thai baht amount for invoice and checkout handoffs.
- 3
Export and test the final asset
Download the right file format, scan the final artwork in banking apps, and confirm recipient and amount before sharing.
Frequently asked questions
Can QR Code Crafter create or verify my PromptPay account?
No. QR Code Crafter only creates a QR image from the PromptPay identifier and amount you enter. Your bank or wallet handles registration, recipient lookup, payment approval, fees, and status.
Can I create a PromptPay QR code without an amount?
Yes. Leave the amount blank when the payer should enter the amount in their banking app.
Is it safe to publish a PromptPay QR code with a personal ID?
Only publish identifiers you are comfortable sharing in that context. For public signage, consider whether a business identifier, e-wallet ID, or hosted payment page is more appropriate.
Can I track PromptPay QR code scans?
QR Code Crafter creates static QR files without scan analytics. Use a landing page you control before payment if measurement is required.
Which format should I use for PromptPay signs or stickers?
Use SVG, PDF, or EPS for print production because they stay sharp when resized. Use PNG, JPG, or WebP for digital payment instructions.