QuickPay Setup — Android donation kiosk
Turn any Android tablet into an always-on QuickPay donation kiosk: hardware checklist, Device Owner provisioning, campaign assignment, and receipt setup.
QuickPay is Muin’s single-tap, fixed-amount kiosk mode for Android tablets — the fastest possible donor experience (one pre-set amount, NFC auto-active, no picker). This guide walks through the full setup — from “I have a tablet” to “donors are tapping and giving” — in about ten minutes for the first device and three to five minutes for each additional device. For broader payment kiosks (amount picker, fund picker, attract modes), see the Kiosks + QuickPay product page.
Hardware checklist
Before starting, confirm your tablet meets the minimums.
| Requirement | Why |
|---|---|
| Android 8.0 (Oreo / SDK 26) or later | Device Owner mode and Stripe Terminal SDK minimums |
| NFC-capable (contactless reader built in) | Required for Tap-to-Pay |
| Google Play Services installed | Stripe Terminal SDK uses Play Services |
| Wi-Fi or cellular data | Offline queue handles up to 24 hours; steady connection recommended |
| 2 GB RAM or more | Ensures kiosk mode runs reliably for multi-hour sessions |
| A power outlet or charging dock at the deploy location | QuickPay is always-on; you want it on AC power |
Optional but useful:
- A kiosk floor stand or lockable counter mount ($15–$40 on Amazon)
- A Bluetooth or USB ESC/POS receipt printer (if printing receipts on-site)
What doesn’t work:
- iPads — no iOS equivalent for Device Owner always-on mode. Use Tap-to-Pay on iPhone (separate product) for iOS.
- Phones — technically possible, but NFC antenna placement and small screens make for a poor donor experience.
- Tablets without NFC — Muin Go POS mode may still work for card-only giving, but Tap-to-Pay is off the table.
Step 1 — Install Muin Go
- On the tablet, open the Google Play Store
- Search for Muin Go and install
- Open the app and sign in with your Muin admin credentials
You’ll land on the app home screen with the standard module menu.
Step 2 — Enable Kiosk Mode (Device Owner provisioning)
Device Owner is an Android primitive that lets one app fully lock the device to its own screen. Provisioning differs slightly by Android version and device vendor.
Easy path — QR enrollment (most modern tablets):
- Reboot the tablet to factory settings (Settings → System → Reset). This is the cleanest path. Skip this step if the tablet is new out-of-box.
- During the setup wizard, tap the clock six times on the welcome screen. You’ll see a QR scanner.
- In the Muin web admin, go to Payments → Terminals → Add kiosk, select the campaign, and click Generate enrollment QR.
- Scan the QR with the tablet. Android installs Muin Go as Device Owner automatically.
- Confirm prompts on the tablet; sign in to Muin Go.
Manual path (fallback):
- Install Muin Go as described in Step 1
- In Muin Go, navigate to Settings → Kiosk Mode
- Tap Enable Kiosk Mode. The app prompts for Device Owner enablement.
- Follow the on-screen instructions — typically “enable USB debugging, run a shell command from a connected computer” on older tablets. The app shows the exact command.
After Device Owner is enabled, Muin Go becomes the home screen. Pressing home, recent apps, or notifications does nothing — the device is locked to the app.
Step 3 — Assign a campaign
From the Muin web admin:
- Navigate to Payments → Terminals
- Find your newly provisioned device in the list (it appears as “online”)
- Click the device and configure:
- Campaign — which campaign or fund this device will collect for
- Preset amounts — the buttons donors tap (e.g., $5 / $20 / $50 / custom)
- Receipt delivery — email, SMS, WhatsApp, printed (if printer attached), or QR code for donor-scan
- Attract screen (optional) — idle display between taps; options include a static graphic, a live thermometer, or a donor-wall
- Fee-covering prompt (optional) — ask the donor if they’d like to cover the Stripe processing fee
- Click Push to device
Configuration updates within a few seconds. The tablet transitions to the live QuickPay screen.
Step 4 — First tap
Hand a card, phone, or watch to a colleague and ask them to tap the NFC region (usually the back center of the tablet). The Stripe Terminal SDK tokenizes the payment, QuickPay processes the charge, and the receipt fires via the chosen channel.
At this point the device is production-ready.
Receipt channel details
| Channel | Requires | Donor experience |
|---|---|---|
| Donor types or has an email on file | Standard HTML receipt email; auto-arrival within a minute | |
| SMS | Donor’s phone number on file or entered on device | Text message with link to full receipt |
| Donor’s WhatsApp number on file (Twilio-enabled) | WhatsApp message with receipt link | |
| ESC/POS receipt printer (USB or Bluetooth) | Instant printed slip; good for events | |
| QR | None; device generates a QR on-screen | Donor scans with their phone; receipt opens on their browser |
Attract screen modes
When no donor is tapping, QuickPay can display:
- Static branding — your logo + campaign name
- Live thermometer — real-time fundraising progress
- Donor wall — recent donors’ first names + amounts (opt-in per donor)
- Impact counter — total raised today / this week / this campaign
All configurable from Payments → Terminals → [device] → Attract screen.
Deploying multiple devices
After the first device, subsequent tablets take ~3 minutes each because you re-use the enrollment QR:
- Reboot each new tablet to factory (if needed)
- Scan the same campaign’s enrollment QR during setup
- Device auto-enrolls as a second QuickPay kiosk under the same campaign
To split devices across campaigns, generate a separate enrollment QR per campaign.
Switching a device to a different campaign
You don’t reprovision. From the web admin:
- Navigate to Payments → Terminals
- Click the device
- Change the assigned campaign
- Click Push to device
Updates within a few seconds. The tablet transitions to the new campaign’s screen.
Offline behavior
QuickPay’s offline queue holds up to 24 hours of transactions. When connectivity is lost:
- New transactions are confirmed on-device with the donor; the tablet shows a subtle “offline queue” indicator
- Receipts fire as soon as the device regains connectivity
- The ledger posts the transactions with their original timestamps
If the tablet is offline for more than 24 hours, it will refuse new tap-to-pay charges until connectivity is restored — the Stripe Terminal SDK requires periodic sync for security.
Security model
- Card data never touches the tablet or Muin’s servers. The NFC read goes directly to Stripe Terminal, which returns a tokenized payment intent.
- No PCI scope expansion for your organization — you’re using Stripe’s certified Terminal flow.
- Device Owner mode prevents navigation away, Settings access, or notification shade pulls. A donor cannot reach anything outside the donation flow.
- Lost or stolen device: unassign it from the web admin; the tablet can no longer process transactions even if reconnected.
Troubleshooting
| Issue | Cause | Resolution |
|---|---|---|
| QR enrollment not scanning | Tablet’s camera in low-light or clock-tap not registered | Use manual path (Step 2, fallback); reboot to factory and retry |
| ”NFC not available” message | Tablet lacks NFC, or NFC disabled in Settings | Check hardware spec; if NFC exists, re-enable via Settings before locking to kiosk |
| Device shows offline in web admin | Wi-Fi dropped or IP changed | Check Wi-Fi on the tablet; reconnecting restores web-admin visibility |
| Receipts not arriving | Channel misconfigured or delivery blocked | In Payments → Terminals → [device] → Receipt Delivery, run Test receipt; check delivery logs |
| Donor typed wrong email; can’t resend receipt | Post-tap workflow | From the admin transaction detail page, click Resend receipt and edit the email |
| Device Owner provisioning failed | Tablet already enrolled to another manager | Factory reset the tablet; re-provision fresh |
| Printed receipts not printing | Printer paired but offline, or paper jam | Check printer power + pairing; clear jam; Test print from admin |
Related
- Kiosks + QuickPay product page — marketing overview + seven operating modes + comparison against vendor-bundled kiosk providers
- Smart Payments — the broader payment platform QuickPay sits on
- Reconciliation — where QuickPay transactions land in your books
- Muin Go mobile app — the app QuickPay runs inside
- Blog: Turn the Android tablet you already own into a donation kiosk