Core Acceptance
Payment Processing
Start here when the business needs one payment layer that can support multiple channels and environments.
Explore Payment ProcessingPayment Paths
Compare how payment happens before you compare everything around it
Payment Paths focuses on the collection model: in-person acceptance, customer-initiated QR checkout, staff-sent paylinks, recurring billing, and web-led checkout routes that shape the rest of the setup.
Payment Routes
Start with who initiates the payment and where it finishes
This section is most useful when the business is choosing between transaction models, not when it is already locked into one route.
Customer-Initiated
QR Scan-to-Pay
Use QR-led collection when the customer should start payment from a sign, counter, waiting area, or service point.
Explore QR PaymentsFollow-Up Billing
SMS Paylink App
Use paylinks when the staff member needs to request payment remotely after the service interaction has already happened.
Explore PaylinksRecurring
Subscription Platform
Use recurring billing when the business relationship depends on ongoing charges, plans, or scheduled billing cycles.
View Subscription ToolsWeb Checkout
eCommerce Shopping Cart
Use website-led checkout when the customer completes the transaction through a web storefront or service bundle flow.
View eCommerce ToolsBest Starting Point
| If the payment needs to... | Start here | Usually connects to |
|---|---|---|
| Happen across online, remote, and in-person environments | Payment Processing | Hardware |
| Be initiated by the customer from signage or a counter | QR Scan-to-Pay | Self-Service Kiosk |
| Be requested by staff after the interaction | SMS Paylink App | Mobile Readers |
| Repeat over time | Subscription Platform | Security |
What This Page Clarifies
Use Payment Paths to reduce routing confusion early
- Who initiates the transaction.
- Whether payment happens in person, remotely, or inside a website flow.
- Whether the route needs hardware support, recurring billing, or a connected software layer.
FAQ
Should I start here or on Solutions?
Start here if the question is specifically about how money is collected. Start on Solutions if the business model is still broader than the payment event itself.
FAQ
When does hardware enter the decision?
Once it is clear that the payment route needs a physical checkout point, hardware becomes the next comparison layer.
FAQ
Does Payment Paths replace Payment Processing?
No. Payment Processing is one route inside the comparison. Payment Paths exists to help businesses compare it against other collection models.
FAQ
What if the business uses more than one payment route?
That is common. Start with the most important route, then review how adjacent paths connect to the same payment foundation or operating environment.
Next Step
Compare the payment route first, then move into the tools that support it
When you know how the transaction should start and where it should finish, the rest of the FoxPay stack becomes easier to sort into hardware, software, pricing, and operational review.