Setup intent versus QR product intent

This page owns the how-to task: creating, testing, printing, placing, and monitoring a donation QR code. For ScanRaise's printable per-person cards and 1-up, 2-up, and 4-up PDF layouts, use the product page. Scan-to-donate QR card product

For a broader explanation of QR fundraising use cases and planning, use the educational overview. QR code fundraising guide

Prerequisites before generating the code

  • An approved organization and campaign name that the donor can recognize.
  • A stable HTTPS giving-page URL that will remain valid for the life of the print piece.
  • A mobile giving page with the amount, payment, privacy, receipt, refund, and contact behavior your organization has approved.
  • A documented recipient and payout flow, including any platform fee and separate payment-processing cost.
  • One adult owner for test payments, printed materials, donor questions, refunds, and reconciliation.
  • Permission for each print and venue placement, plus a typed URL or descriptive clickable link as a fallback.

What donors see after a scan

The code encodes a destination, usually a web address. A donor opens a compatible camera or code scanner, positions the code in view, reviews the link shown by the phone, and taps it. The browser then loads the giving page, where the donor confirms the organization, campaign, amount, payment details, and any optional fee choice before submitting.

After payment, the donor should see a clear confirmation and receive the receipt promised by the giving page. The organizer should see a matching record with the amount and status needed for reconciliation. Test this entire path with a small real payment, then follow the approved refund process if the organization does not intend to retain the test gift.

A QR image posted online is not a complete path for someone viewing it on the same phone. Put a normal descriptive link beside the image so the destination is usable without a second device.

Generate and customize the QR file

Copy the final giving-page URL rather than a preview, editor, or temporary session URL. If the fundraising platform generates the code, confirm which campaign and participant it belongs to before downloading. If you use a standalone generator, verify that the service does not depend on a short-lived redirect you cannot maintain.

Use a vector file such as SVG when the workflow provides one, or a high-resolution raster file sized for the final print. Keep strong light-dark contrast. Put the organization name, a short instruction, and a typed fallback URL near the code without entering its required clear margin. Do not cover the code with a logo unless the exact final design passes every device and distance test.

Test on iPhone and Android

Apple documents scanning with the Camera app or Code Scanner, followed by tapping the displayed link. Test the final artwork with a current iPhone that your audience is likely to use. Apple QR scanning instructions

Google documents QR scanning in Camera from Google on selected devices. Android camera behavior varies by device and app, so test at least one current Android phone and keep a typed URL available. Google Camera QR scanning instructions

  • Scan the exact exported file before layout work begins.
  • Scan a proof at its final physical size, not only a large image on a monitor.
  • Test in the expected lighting and from the expected viewing distance.
  • Read the displayed domain before opening it and confirm the exact campaign after the page loads.
  • Complete the approved test-payment, confirmation, receipt, organizer-record, and refund checks on both paths.
  • Repeat after any change to the destination, code, logo, color, crop, print vendor, paper, or physical size.

Print size, quiet zone, and error correction

There is no universal print dimension that works at every distance, camera, URL length, paper, and lighting condition. DENSO WAVE recommends choosing module size for the printer and reader and printing as large as the available area permits, then testing the actual use case. DENSO WAVE module-size guidance

DENSO WAVE specifies a clear quiet zone four modules wide on every side of a standard QR Code. Text, borders, photos, or stickers must not enter that margin. DENSO WAVE quiet-zone guidance

Higher error correction can recover more damaged codewords, but it also makes the code denser. Choose the setting for the environment and available print area, then verify the exact final piece instead of assuming that a higher level fixes poor size, contrast, or printing. DENSO WAVE error-correction guidance

Placement by venue

School or community event

Use a staffed check-in table, concession area, approved lobby display, printed program, or closing slide. Keep the typed URL visible and do not block accessible routes.

Concert, theater, or gallery

Use programs, lobby signs, seat cards, or artwork labels with venue permission. Place the code where stopping to scan will not obstruct aisles or exits.

Sports venue

Use staffed ticket or concession areas, programs, and fixed signs protected from weather. Do not put the only code where distance or motion makes scanning impractical.

Restaurant or retail partner

Use only placements approved by the business. State the beneficiary and campaign clearly so the code does not look like the merchant's payment code.

Mail, flyer, or handout

Print one proof from the final PDF and scan it after folding, trimming, or lamination. Include the destination in readable text.

Email, social, or website

Provide a descriptive clickable link beside the QR image. W3C guidance says link purpose should be understandable from the text or its programmatic context.

Payment, privacy, and QR safety checks

Confirm the exact organization, campaign, fee presentation, payment processor, funds recipient, payout path, privacy notice, donor choices, receipt, refund contact, and organizer record before publishing. Do not place student personal information in a public code or fallback URL.

The FTC warns that a malicious QR code can lead to a spoofed site and recommends inspecting the displayed URL before opening it. For public displays, use protected or supervised placements and inspect for stickers or altered signs before and during the event. FTC consumer advice about harmful QR links

Troubleshooting common setup mistakes

The camera does not recognize the code

Increase light, clean the camera lens, change distance, confirm contrast, restore the full quiet zone, and print a larger proof. Re-export if the squares look blurred or distorted.

One phone works and another does not

Test the built-in camera and current supported scanner path, then provide the typed URL. Do not publish until the intended audience has a reliable alternate path.

The wrong campaign opens

Remove the material, correct the destination, generate a new code, and retest. Do not ask donors to navigate from an incorrect page.

The page is correct but payment fails

Check campaign status, processor setup, supported payment methods, required fields, error messages, and the organizer record. Escalate through the provider's documented support path.

The printed code stopped working

Inspect damage, glare, fading, folds, cropping, lamination, and replacement stickers. Replace the piece and keep the same typed fallback URL only if that URL remains correct.

The organizer cannot match the test gift

Stop distribution until the giving page, campaign attribution, receipt, payment status, organizer record, and refund procedure have been reconciled.

Step-by-step

Step 1: Approve the giving destination

Confirm the organization, campaign, stable HTTPS URL, payment and payout path, fees, privacy notice, receipt, refund contact, and adult owner.

Step 2: Create and verify the giving page

Open the final page on a phone, confirm the campaign identity and fields, and complete the organization's approved small test payment.

Step 3: Generate the QR code

Encode the final giving-page URL and export SVG when available or a high-resolution raster file suitable for the intended print.

Step 4: Design the print piece

Use strong contrast, preserve the four-module quiet zone, add the organization name and a short instruction, and print a typed fallback URL.

Step 5: Test iPhone and Android paths

Scan the exact exported file and the final-size proof on current iPhone and Android devices, then verify the domain, campaign, payment, confirmation, receipt, and organizer record.

Step 6: Print one final proof

Review size, contrast, quiet zone, paper, crop, fold, lamination, lighting, viewing distance, and the typed URL before ordering the full quantity.

Step 7: Place and monitor the code

Use approved, accessible, supervised or protected locations and inspect public materials for damage or replacement stickers.

Step 8: Reconcile and maintain

Monitor payment status and donor questions, follow the approved refund process for any test gift, and replace materials whenever the destination or design changes.

Downloads

Frequently asked questions

How do I create a QR code for donations?

Create and approve a stable mobile giving page, copy its final HTTPS URL, generate the code, preserve strong contrast and the clear quiet zone, add a typed fallback URL, and test the exact final-size print through payment, receipt, and organizer record.

What size should a donation QR code be?

There is no universal physical size. URL length, code density, printer, paper, lighting, viewing distance, and camera all matter. Print as large as the available design permits, preserve the four-module quiet zone, and test a final-size proof in the real setting.

Should I choose high error correction?

Choose error correction for the expected environment and print area. A higher level can restore more damaged data but also makes the code denser. It does not replace adequate size, contrast, a clear quiet zone, and final-device testing.

Why should a QR image online also have a link?

A person viewing the image on the same phone may not have a second camera available, and some users cannot use visual codes. A descriptive clickable link provides a direct, understandable path to the same giving page.

How can organizers reduce QR-code tampering risk?

Use protected or supervised placements, print the expected domain in text, inspect public materials before and during the event, teach donors to review the displayed URL, and remove any code that looks covered or altered.

Sources and review notes

Sources checked . External rules and product policies can change, so confirm them before launch.

  1. Apple Support: Scan a QR code with your iPhone or iPad. Current Apple camera and Code Scanner workflow.
  2. Google Camera Help: Scan QR codes. Current Camera from Google workflow and device caveat.
  3. DENSO WAVE: Point for determining the code area. Four-module quiet-zone requirement for standard QR Code.
  4. DENSO WAVE: Error correction feature. Tradeoff between error correction and code density.
  5. DENSO WAVE: Point for setting the module size. Printer, reader, and module-size considerations.
  6. FTC: Scammers hide harmful links in QR codes. Consumer guidance to inspect a QR destination and watch for spoofed links.
  7. W3C WAI: Understanding Link Purpose in Context. Accessibility guidance for descriptive link purpose.