QuickPay Setup · Android donation kiosk
Turn a certified SUNMI kiosk or any Android tablet with NFC into an unattended QuickPay donation kiosk: hardware checklist, Device Owner provisioning, campaign assignment, and receipt setup.
QuickPay is a terminal collection mode: one fixed amount, one pre-assigned campaign, contactless armed and no picker. The donor confirms the amount and taps. It is the simplest station Muin ships, and this guide takes a tablet from a box to a working one.
When you’d use this
- A fixed suggested gift at an entrance, where the point is speed rather than choice.
- A sadaqah or offering station that runs all day with nobody staffing it.
- An event booth with one price, for example a ticket or a meal.
- A second tablet beside a kiosk, so a queue has somewhere else to tap.
QuickPay is one of three modes
A terminal config carries a collection mode, and the mode decides what the device shows:
| Mode | What the donor sees |
|---|---|
| QuickPay | One fixed amount. Requires that amount on the config. |
| QuickSelect | A short list of preset amounts to choose from. Requires the presets. |
| Open entry | A keypad. This is the default for a new config. |
So “QuickPay” means specifically the fixed-amount mode. If you want several amounts on the tile grid, you want QuickSelect, and if you want a donor-facing campaign screen with impact wording, you want a kiosk campaign instead.
Hardware checklist
Before starting, confirm your tablet meets the minimums.
| Requirement | Why |
|---|---|
| Android 13 or later | The Tap to Pay minimum set by Stripe. On an older version the app refuses Tap to Pay and says so by name. |
| A security update from the past 12 months, Developer options off, not rooted | Stripe refuses Tap to Pay on a device that fails any of these, and the app explains the cause |
| NFC-capable (contactless reader built in) | Required for Tap to Pay, and it must be switched on in Android settings |
| Google Play Services installed | The Stripe Terminal SDK uses Play Services |
| A reliable Wi-Fi or cellular connection | Card capture needs connectivity. A tablet that loses its connection shows Card payments are offline and stops charging until it is back. |
| 2 GB RAM or more | Ensures kiosk mode runs reliably for multi-hour sessions |
| A power outlet or charging dock at the deploy location | A QuickPay tablet runs unattended all day; 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. Tap to Pay on iPhone requires an iPhone, and the app says so rather than letting you set up a station that cannot take a card. Android has no equivalent restriction, which is why QuickPay is an Android station.
- Phones. Technically possible, but NFC antenna placement and small screens make for a poor donor experience.
- Tablets without NFC. The app refuses Tap to Pay with This device does not have NFC and cannot accept contactless payments. Pair an external card reader instead.
Two things to turn on before the tablet
Tap to Pay has two switches that are separate on purpose, and a station fails with an unhelpful silence if either is missed.
- Your organization accepts the terms, once. An owner or admin with finance configuration rights does this on the Stripe Connect onboarding screen, where a Tap to Pay card sits alongside the rest of the setup. It is unchecked by default and is not a condition of getting paid.
- Each device enrolls, once per tablet. That happens on the tablet itself, in the Pay module’s Tap to Pay setup, and it needs payment-processing rights rather than full Pay access, because it is a per-device act.
Keeping them separate is deliberate: a tablet can be enrolled while the organization has not accepted, and the readiness check then tells you which of the two is missing rather than reporting one green light for both.
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. This is the cleanest path. Skip it if the tablet is new out of the box.
- During the Android setup wizard, reach the QR scanner.
- In the Muin web app, go to Devices & Kiosk > Device Registry and generate the Android enrollment QR, choosing the kiosk policy the screen will live on.
- Scan the QR with the tablet. Android installs Muin Go under that policy automatically, and the enrollment survives a later factory reset.
- Confirm the prompts on the tablet and sign in to Muin Go.
Pick the kiosk policy before you mint the code. Android fixes a device’s mode at enrollment: a tablet enrolled under a non-kiosk policy never enters kiosk lockdown, however many times you reassign it afterwards, and it keeps reporting itself as compliant while it does. The only fix is a factory reset and a fresh enrollment.
If you embed the venue Wi-Fi in the QR so the tablet joins by itself, that QR is a credential: it is single-use and expires in fifteen minutes, so generate it while you are standing at the device.
Setup-code path (works on any platform):
- Install Muin Go as described in Step 1.
- In the Muin web app, open Devices & Kiosk > Device Registry and run the pairing wizard: name the device, pick its location, pick its security level, and generate a six-digit setup code.
- On the tablet, enter the code or scan the code’s QR. The web panel flips from Waiting for device… to Paired on its own.
Muin Go’s own entry point for this is Settings > Kiosk Mode, and the sign-in screen also carries Set up this device as a screen so a wall tablet can be brought up without signing a person in first.
With kiosk lockdown applied, Muin Go holds the screen: home, recent apps and the notification shade do nothing. Three things release a stranded device: the kill-switch gesture on the device, the kiosk staff panel behind its PIN, and the turn off kiosk command from the console.
Step 3 · Create the config and assign it
The device reads its behavior from a terminal config. Create one in the web app:
- Go to Payments > Terminals and click New Config.
- Name it, and choose QuickPay as the collection mode.
- Enter the fixed amount, in dollars. It must be greater than zero; the form refuses a blank or a zero.
- Optionally set the rest:
- Default fund and the funds available
- Campaign or event the gifts belong to
- Allow custom amount
- Require receipt email
- Tipping, and the tip percentages offered
- A custom message for the screen
- Save, and assign the config to the terminal record for your tablet.
Config changes are pushed to the device live, so the tablet moves to the QuickPay screen without being touched.
Fee covering and tipping on a kiosk are kiosk-config settings, under Devices & Kiosk > Kiosk Configs, not terminal-config ones. Both are donor choices and both are off unless you turn them on.
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 |
The idle screen
What the tablet shows between donors is a kiosk config setting, under Devices & Kiosk > Kiosk Configs: how long the attract screen holds each item, when the device returns to the board after a donor walks away, and how long it pauses after somebody interacts. The donor wall is one of the attract options, and donors appear on it only if they opted in while giving.
Deploying more devices
Each additional tablet is quicker than the first, because the organization-level terms are already accepted and the config already exists:
- Enroll or pair the tablet as in Step 2.
- Enroll that device for Tap to Pay on the tablet.
- Assign the existing config to its terminal record.
To run different amounts in different places, create one config per amount and assign each to its own terminal.
Switching a device to a different amount or campaign
You do not reprovision. Change the config the terminal is assigned to, or edit the config’s fixed amount and campaign. The change is pushed live and the tablet moves to the new screen.
When the connection drops
QuickPay needs connectivity to take a card. A tablet that loses its connection shows Card payments are offline and stops charging until it is back, rather than taking a gift it cannot complete.
Treat the network as part of the installation: prefer a wired or strong signal at the mounting position, and keep the tablet on mains power so it is not also fighting a flat battery.
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.
- Kiosk lockdown prevents navigation away, Settings access and notification shade pulls. A donor cannot reach anything outside the donation flow.
- Lost or stolen device: revoke it from the console. A revoked device can no longer process transactions even if it reconnects.
What it affects
- Gifts taken here are gifts. A QuickPay donation receipts as a charitable gift, and the fact it came through a tablet does not change that.
- Attribution follows the config’s campaign, event and fund settings.
- Your reports and donor records carry a QuickPay gift like any other, so a station’s takings are visible without a separate reconciliation.
- Nothing on your other tablets. A terminal config applies to the terminals you assign it to.
When it goes wrong
| What you see | What it means | What to do |
|---|---|---|
| Card payments are offline on the tablet | No connectivity, so the card cannot be captured. | Fix the network at the mounting position. |
| Turn on NFC to use Tap to Pay. | NFC is switched off in Android settings. | Enable it before locking the device down, because afterwards you cannot reach Settings. |
| Developer Options is turned on, which blocks Tap to Pay. | Android developer options or USB debugging is on. | Turn both off in Android settings, then restart Muin Go. |
| This device does not support Tap to Pay. | The tablet has no NFC, or is below the Android floor. | Use a different tablet, or pair an external card reader. |
| Update Android to version 11 or later to use Tap to Pay. | This device’s own floor is higher than the general minimum. | Update Android, or use another tablet. |
| This device cannot be used for Tap to Pay because it has been modified or rooted. | The tablet fails Stripe’s integrity check. | Use an unmodified device. |
| Tap to Pay is not available for this account. Please contact support. | An account-level block. | Contact support; nothing on the tablet will fix it. |
| The readiness check says the organization has not accepted | The Tap to Pay terms card on the Stripe Connect screen was never ticked. | An owner or admin with finance configuration rights ticks it once. |
| The tablet never enters kiosk lockdown but reports itself healthy | It was enrolled under a policy that is not a kiosk policy. | Factory reset and enroll again against the kiosk policy. |
| The enrollment QR has stopped working | A QR carrying Wi-Fi is single-use and lasts fifteen minutes. | Generate a fresh one at the device. |
Next step
- Tap to Pay troubleshooting, when taps are being missed
- Card readers and hardware, when a mounted tablet needs a dedicated reader
- Device Management: the console side of a paired tablet
Related
- Kiosks + QuickPay product page: marketing overview, every operating mode including Menu, and a 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