Falaah Falaah AI
product

Accept Payments Anywhere: POS, QR Codes, and Recurring Billing

How businesses use Muin's standalone payment pages, QR-to-payment flows, and recurring invoices to accept payments in-store, online, and on the go.

FT
Falaah Team
· · 5 min read
Accept Payments Anywhere: POS, QR Codes, and Recurring Billing

A business wants three things from a payment system, whether it is a 12-person agency or a 400-person distributor with a showroom: accept cards at the counter, let customers pay from their phones, and bill regulars on a recurring schedule. 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 four 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.

Share the payment link by email or text, or print its QR code (see below).

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 on a 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 costs are card processing and the 0.5% platform 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. Recurring Billing

For regulars on a weekly or monthly arrangement, set up a recurring customer invoice. Muin creates each invoice on the schedule you choose (weekly, monthly, or custom) and can send it automatically, and your customer pays from the payment link on the invoice. See Recurring customer invoices.

4. Cards at the Counter

For a customer standing in front of you, Muin Go turns your phone into a card reader. Enter the amount and the customer taps their card or phone on yours. Tap to Pay works on an Android phone with NFC or an iPhone XS or later, with no reader to buy. See the Point of Sale docs for setup.

The Unified Payment Layer

All four 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 pays a recurring invoice, 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: card payments arrive already tied to their payer, and bank transfers and checks are matched for you rather than retyped from a statement. Confident matches confirm on their own, and you review the rest.

For the complete matrix of all 26 embedding combinations, see 26 Ways to Accept Payments, Donations, and Registrations with Muin.