Accept Payments Anywhere: POS, QR Codes, and Subscriptions
How small businesses use Muin's standalone payment pages, QR-to-payment flows, and subscription widgets to accept payments in-store, online, and on the go.
A small business owner wants three things from a payment system: accept cards at the counter, let customers pay from their phones, and offer recurring subscriptions for regulars. Today, that often requires three separate tools.
Muin handles all three with the same platform that powers nonprofit donations and event tickets. The payment infrastructure is the same — what changes is the configuration and the context. Here are the three small business payment combinations.
1. Standalone Payment Page
A branded page at /go/{slug}/pay/{token} for accepting one-time payments. No shopping cart — just a clean page where a customer confirms an amount and pays via Stripe. Each link carries a unique, secure token tied to one specific payment request (a specific amount, description, and payer), so it can’t be reused or altered to change the amount. The customer sees your branding, what the payment is for, and the amount due; after paying, a confirmation with a reference number. No account creation, no app download.
Embed it on any website:
<script src="https://muin-api.falaah.ai/embed/widget.js" data-tenant="your-biz" data-type="button"></script>
Where it fits:
- Invoice payment — a consultant emails a $3,500 invoice with the payment link; the client clicks, pays by card, and both have a digital record.
- Order deposits — a contractor collects a 50% deposit before starting, on a page showing the project and deposit amount.
- Service fees — a property manager sends each tenant a unique link for their specific monthly amount.
- One-time charges — a nonprofit collects a program registration fee without building a full checkout.
2. QR Code to Payment
The same payment-page URL can be encoded as a QR code for in-person collection. A printed QR code costs pennies and needs no hardware on your side and no app on the customer’s. Create the payment page with a fixed or open amount, generate its QR code as a downloadable image, and print and display it — counter card, table tent, register sticker, or menu. The customer scans with their phone camera and pays on the branded Stripe page. The amount can be fixed (for a specific invoice) or open (for tips and variable services).
Where QR-to-payment works: market and festival vendors, service providers collecting after the job, food service (tables, counter, or menu), and nonprofits displaying codes that link to a giving or kiosk-donate page at events.
The economics. A printed QR code replaces a card-reader subscription with a piece of cardstock — the only per-transaction cost is Stripe’s fee. The trade-off is speed at volume: a dedicated terminal taps in about two seconds, while a QR scan, page load, and form submission takes fifteen to thirty. For a booth doing 20 transactions a day that’s fine; for a coffee shop doing 200, a terminal still wins.
3. Subscription Recurring Payment
An embeddable widget at /go/{slug}/subscribe/{plan} for recurring payment plans. Customers select a plan, enter payment details, and subscribe. Billing is automatic via Stripe. Customers manage their subscription — upgrade, downgrade, cancel, update payment method — through a self-service portal.
Embed the subscription widget on your pricing page:
<script src="https://muin-api.falaah.ai/embed/widget.js" data-tenant="your-biz" data-type="form"></script>
The Unified Payment Layer
All three combinations share the same infrastructure as Muin’s donation pages, event tickets, and form payments. The Stripe account is the same. The reporting is the same. The contact records are the same.
A business that also hosts community events and accepts donations for a local cause through a counter QR code manages all of it from one dashboard. The customer who buys a subscription, registers for an event, and donates to the fundraiser has one contact record showing all three interactions. Every payment ties to its payer’s contact record (or creates a minimal one for a new customer), with history, amounts, and dates tracked automatically — no manual reconciliation against bank statements.
For the complete matrix of all 26 embedding combinations, see 26 Ways to Accept Payments, Donations, and Registrations with Muin.
Related Reading
- Smart Payments: Accept Cards, NFC, ACH, and More — The full Smart Payments overview, including the 0.5% platform fee advantage
- Why Your iPhone May Be the Only POS System You Need — Turn a phone into a full point of sale with zero hardware cost
- Smart Payments docs and Point of Sale docs — Configuration and setup references in the Muin documentation