Payment Pages and QR Codes for Small Businesses

Small businesses need to collect money. That sounds simple until you consider how it actually happens: a PDF invoice, a phone call to read a card number aloud, or a text saying “just Venmo me” followed by a week of confusion. Falaah replaces that friction with token-based payment pages — shareable by link for remote collection, or by QR code for in-person payment.

Payment Page

Every payment page is accessed through a token-based URL:

https://muin.falaah.ai/go/{your-org-slug}/pay/{token}

The {token} is a PaymentPageToken — a unique, secure identifier tied to a specific payment request. Each token resolves to a page showing what the payment is for and the amount due. The customer opens the link, sees the details, and pays.

What the customer sees. A clean, branded page displaying your organization’s identity, a description of the payment (invoice number, service rendered), the amount due, and a Stripe-powered payment form. After successful payment, a confirmation with a reference number. No account creation. No app download.

Token-based security. Each link contains a unique token tied to a specific payment request — a specific amount, description, and payer context. The token cannot be reused or manipulated to change the payment amount. Every link is purpose-built for a specific transaction.

Use Cases

Invoice payment. A consultant sends an invoice for $3,500. The email includes the payment link. The client clicks, pays by card, and both parties have a digital record.
Order deposits. A contractor collects a 50% deposit before starting work. The payment page shows the project description and deposit amount.
Service fees. A property manager sends monthly maintenance fees to tenants, each with a unique payment link for their specific amount.
One-time charges. A nonprofit collects a program registration fee without building a full e-commerce checkout.

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 nothing. The customer scans it with their phone camera, the payment page opens in their browser, and they pay. No hardware on the vendor’s side. No app download on the customer’s side.

The flow:

Create a payment page in Falaah with a fixed or variable amount
Generate a QR code via Falaah’s qr_code_service — the QRCodeDisplay component renders it as a downloadable image
Print and display the QR code: counter card, table tent, register sticker, or menu
Customer scans with their phone camera — modern phones recognize QR codes natively
Customer pays on the branded Stripe-powered payment page
Confirmation appears on the customer’s phone; the business receives the payment in Falaah

Where QR-to-payment works:

Market and festival vendors — print the code on a card next to the product display
Service providers — display the code in the workspace for post-service payment
Food service — place codes on tables, at the counter, or on the menu
Donation collection — nonprofits display QR codes linking to giving pages at events and physical locations

QR for giving pages. The same mechanism works with Falaah’s kiosk donation page:

https://muin.falaah.ai/go/{your-org-slug}/kiosk/donate

Print this code on event materials, table tents at a gala, or posters in a community center.

The Economics

A printed QR code costs pennies. The payment page is included in Falaah. The only per-transaction cost is Stripe’s processing fee. For a business collecting a few hundred dollars a day at a market booth, this replaces a card reader subscription and its monthly fees with a piece of printed cardstock.

The trade-off is speed at high volume. A dedicated card terminal processes tap-to-pay in two seconds. A QR scan, page load, and form submission takes fifteen to thirty seconds. For a coffee shop processing 200 transactions a day, that difference matters. For a vendor processing 20, it does not.

How Payments Connect

Every payment processed through a payment page flows into Falaah’s payment records. The transaction is tied to the payer’s contact record (if they exist in your CRM) or creates a minimal record for new contacts. Payment history, amounts, and dates are tracked — no manual reconciliation against bank statements.

For recurring payments, see subscription billing. Payment pages handle the specific case of “someone owes you money for a specific thing, and you need a clean way to collect it.”