APPOSLASH PRACTICAL GUIDES

UPI QR codes: colour, printing and a scan checklist

By AppoSlash · Published 5 October 2026 · Product guidance, not financial advice

A QR code can hold the same payment instructions as a UPI link. It is useful at a counter, on a flyer or when a payer is viewing your page on a computer. A scan is a handoff to the payment app, not proof that money moved.

Create a QR from your own UPI ID

Use the UPI QR generator, add your authorised ID and display name, and choose an optional amount. Generate the code and choose deep purple, maroon or midnight. The QR is made in your browser and embeds the UPI intent directly. It does not need AppoSlash to track or redirect the scan.

Keep the white space

Our codes use square modules on white and a border of four modules. Keep that border when cropping or designing a poster. Do not place a logo across the code, stretch it into a rectangle, add a busy background or invert the colours. We offer three dark palettes so the modules remain distinct from white.

The implementation uses Kazuhiko Arase’s open-source QR generator. The SVG retains sharp module edges when enlarged. A PNG is easier to paste into many editors; enlarge the SVG for print rather than repeatedly resizing a screenshot.

A practical scan checklist

1. Download the PNG or SVG and inspect it for a complete white border.
2. Scan the original file with your intended UPI app. Check the resolved recipient name and ID, amount and note before cancelling.
3. Test the final printed size under the lighting where people will use it. Glossy surfaces, small modules or poor contrast can cause scan failures.
4. Check the code after adding it to a design or sending it through a chat app. Compression or cropping can change readability.
5. Inspect a publicly displayed code regularly. A replaced sticker can redirect a payer to someone else.

What can a QR prove?

It can carry an address and requested amount. It cannot prove who printed it, who owns the address or that a payment settled. Payers should check the actual recipient in their UPI app and recipients should review the bank or payment-service record. Read the manual verification guide for the handoff after payment.

Our test boundary

Automated tests independently decode the generated module matrix and compare it with the intended UPI URI, including a non-English name and each palette. That catches data and generation mistakes. It does not certify every camera, payment app, printer or bank combination; a real-device scan is still needed before you distribute your code.

Explore all guides · Report an issue or suggest a correction