QR payments — practical implementation guide
This guide covers: rolling out QR payments for in-person and online sales. We focus on quick setup and a clear customer experience.
If you have questions, use the contact form or check the documents.
If you are comparing options (BLIK, terminals), see: QRTransfers vs BLIK — comparison, QRTransfers vs payment terminal, QR payments vs BLIK and QR payments vs payment terminal.
In short
Key points to keep in mind:
- You can launch QR payments without a terminal or extra hardware.
- Results are best when customers clearly see title, amount, and recipient.
- In practice, combine on-site QR with remote payment links.
- Consistent payment naming simplifies reconciliation and support.
How to start
The simplest start is to configure the basics and generate your first payment. Then you can expand settings (e.g. scenarios or shortcuts).
- Start with a simple scenario (one amount, one title).
- Check documents.
- If needed, use the contact form.
Where QR payments work best
QR payments work best where fast rollout and a simple customer flow matter: service points, seasonal sales, events, and remote orders.
In practice, most teams combine two channels: on-site QR (print or screen) and payment links shared with customers in messages.
- On-site: QR code at the counter, table, reception, or on a printout.
- Remote: payment link via SMS, email, or messenger.
- For services: use a title with service + context (e.g. date/booking).
- For sales: separate configurations for common amounts and scenarios.
How to prepare an effective payment screen
Clarity makes the biggest difference. Customers should instantly understand who they pay, what for, and what amount they confirm.
- Use a short, unambiguous title instead of a generic “payment”.
- Add a description only when it truly helps identify the transaction.
- Before publishing, test on multiple phones and under different lighting conditions.
- Show a clear post-payment message (what the customer should do next).
Step-by-step rollout checklist
The best approach is phased rollout: start simple, test, then expand with additional variants.
- 1) Set up the base configuration and one test payment.
- 2) Verify the payment flow from both customer and seller perspective.
- 3) Only then add more shortcuts/amounts/scenarios.
- 4) Regularly review transaction history and naming consistency.
- 5) If needed, use documentation and the contact form.
Related pages
- QR payments without a terminal
- How QR payments work (step by step)
- QR payment methods: BLIK, Apple Pay, Google Pay (and more)
- QR payment security