QR Code Donation Best Practices
Twelve rules that separate a donation QR code that quietly raises money from one that quietly fails. Cover all twelve and the channel pays for itself.
A donation QR code works when it scans the first time and the page that loads is fast, mobile-friendly, and asks for nothing the donor does not need to give. The twelve rules below cover generation, printing, landing page design, tracking, and follow up.
- 01 — Generation rules
- 02 — Print rules
- 03 — Landing page rules
- 04 — Tracking and iteration
- 05 — After the donation
Generation rules
The first three best practices live in the generator before any ink hits paper. Skip them and every later step is wasted work.
Rule 1. Test before printing. Generate the code, scan it with two phones, then scan it again from the proof. A code that works on screen can still fail on paper because of resolution loss or compression. The five-minute test scan is the cheapest insurance you will ever buy.
Rule 2. Use error correction level H. The QR standard offers four error correction levels: L, M, Q, and H. Level H restores up to thirty percent of a damaged code, which is the right setting for any donation use case. Print smudges, fold creases, fingerprints, and weather all degrade a code over time. Level H survives them.
Rule 3. Use a branded short URL. A short, readable URL printed under the code does two jobs. It tells skeptical donors where they are being sent, and it gives a fallback for anyone whose phone cannot scan. Custom short URLs are part of the dynamic QR code generator.
Print rules
The next three rules live in the printer. Get them right and a paper flyer becomes a working donation channel.
Rule 4. Minimum one inch square. Anything smaller risks scan failures, especially on older phones or in low light. For codes scanned from a distance, use the ten to one rule: the code should be at least one tenth the distance from which it will be scanned. Three feet means three inches. Six feet means seven.
Rule 5. High contrast, dark on light. Black ink on white paper is the safest pick. If you want brand color, keep the dark modules genuinely dark and the background genuinely light. Inverted codes (light on dark) often fail on stock scanner apps.
Rule 6. Clear call to action above the code. A bare QR code makes donors hesitate because they do not know what will happen when they scan. Four words solve it: scan to give now. Place the line directly above the code in a font large enough to read at the same distance.
For background on how the QR standard handles damage and error correction, see the Wikipedia QR code article.
Landing page rules
The page the QR code points to does more for conversion than the code itself. A clean code pointing at a slow, cluttered page loses every donor that scans. Three rules apply.
Rule 7. Mobile optimized. Almost every QR scan happens on a phone. The page must load in under three seconds, render without horizontal scrolling, use tappable buttons at least 44 pixels tall, and accept Apple Pay or Google Pay. Anything that breaks on a phone breaks the donation.
Rule 8. Suggested amounts. Give donors three preset amounts plus an other field. Decision fatigue kills small dollar gifts. Three numbers anchor the choice and let donors decide in seconds. Pick the numbers based on your average gift, not on what you wish people would give.
Rule 9. Strip every non-essential field. Name, email, amount, payment. That is the minimum. Everything else, including phone number, mailing address, employer, and how you heard about us, can come later in the thank you flow. Each extra field costs donors. The web.dev forms guide has a deeper treatment of form friction.
Tracking and iteration
The next two rules turn a one-time campaign into a learning loop.
Rule 10. Use scan tracking and editable destinations. A dynamic QR code records each scan with timestamp, device, city, and country. It also lets you change the destination later without reprinting the code. That means you can launch a poster pointing at a fall campaign, then update the same code to point at a winter campaign in November. The print run keeps working. See dynamic QR code with tracking.
Rule 11. A/B test the landing page. The QR code is a constant. The page is the variable. Try two headlines, two suggested amount sets, two hero images. Send half of the scans to each version using two short URLs. After two weeks, the winner is obvious. Keep the winner, kill the loser, run the next test. Small lifts compound across a year.
After the donation
The last rule lives outside the QR code itself but is the one that turns first time donors into repeat donors.
Rule 12. Follow up with a thank you within 48 hours. An automatic email confirmation is the floor. The ceiling is a personal email or letter from a real person at the organization. Donors who feel seen renew at far higher rates than donors who feel processed. Make the thank you specific to what their gift will do, not generic gratitude.
Putting all twelve rules together gives you a working channel. The code scans the first time. The page loads fast and asks little. The data tells you what worked. The follow up brings the donor back. Read the cluster pillar at dynamic QR code for donations, the broader template at QR code for nonprofits, and event specifics at QR code for fundraising events.
Test, error correction H, branded short URL.
One inch minimum, dark on light, call to action.
Mobile fast, suggested amounts, minimum fields.
Dynamic destination, scan logs, A/B test the page.
Personal thank you within forty-eight hours.
Reuse the same code for the next campaign.
Frequently asked questions
What is the most important best practice for a donation QR code?
Test a printed proof before the full run. A single test scan catches almost every problem before you commit ink to paper.
What error correction level should a donation QR code use?
Level H, the highest. It restores up to thirty percent of a damaged code, which protects against print smudges, creases, and wear.
How small can a donation QR code be?
One inch square is the safe minimum for handheld reading. Larger sizes are needed for codes scanned from a distance.
Does the landing page matter?
Yes. The page should load fast on a phone, name the cause, suggest amounts, and remove every field that is not strictly required.
Should I track scans?
Yes. Use a dynamic QR code so each scan records timestamp, device, and location. The data tells you which channel actually delivered donors.
Build a code that follows all twelve rules
Generate a dynamic donation QR code with high error correction, a branded short URL, and a tracking dashboard.
Create your QR code →