QuickPay allows you to seamlessly collect payments in PatientNow Go without creating a full ticket in PatientNow Essentials (PNE) beforehand. Designed for moments when the payment amount is known, it provides a swift and elegant solution for front desk rushes, pop-ups, and open houses.
Once a transaction is completed, a ticket is automatically generated in PNE using a QuickPay Service placeholder, allowing your team to update the exact items sold at their convenience. Please note that QuickPay is not a replacement for standard workflows if your practice requires item-level details prior to capturing payment.
ElevateNow LMS Training: PatientNow Go QuickPay
Before You Begin
Ensure the following requirements are met to experience a smooth checkout process:
QuickPay must be enabled for the practice. Navigate to Company Settings > Sales Register Options > General Options > Display to confirm.
You must be logged into PatientNow Go in the correct organization and location.
A supported payment method, such as Tap to Pay on iPhone or the Moby 5500 terminal, must be configured and ready.
Your mobile device must have a stable internet connection.
Reconciling staff must have access to the QuickPay Ticket Management report in PNE.
Starting a QuickPay Payment
Open PatientNow Go.
Navigate to the Tickets to Pay screen.
Tap QuickPay. If the option is missing, verify the feature is enabled in your practice settings.
Selecting a Customer
The intelligent flow allows you to choose an existing client or welcome a new one.
To select a recent customer: Review the recent list and tap the appropriate profile.
To search for an existing customer: Tap Search, enter at least three letters of the client's name, and select their profile.
To add a new customer: Tap Add, enter the required fields (First Name, Last Name, and Email), provide an optional Phone Number, and tap Submit.
Creating the QuickPay Ticket
Confirm the correct customer profile is selected.
Enter the payment amount, ensuring it is greater than $0.00. The system intelligently replaces prefilled amounts on the first keypad entry.
Review the calculated tax and total.
Wait for the pricing to load completely before proceeding.
Taking the Payment
Observe the payment readiness indicator. Wait until the system displays "Ready" rather than "Connecting" or "Not Ready".
Select your configured payment method.
Ask the patient to present their card or device.
Allow the app to remain open while the payment processes.
Payment Response
Once processed, the system provides a clear outcome.
Payment Successful: You may tap 'Another QuickPay' to serve the next patient, tap 'Email Receipt' to send a beautifully branded receipt to a saved or custom email, or tap 'Close' to return to Tickets to Pay. The QuickPay ticket is immediately created in PNE.
Payment Declined: Tap 'Try Again' to seamlessly reattempt the payment without losing your place in the flow. Declined attempts are not recorded as successful transactions.
Using the QuickPay Ticket Management Report in PNE
QuickPay is designed for speed in the app, giving you the flexibility to perfect your records later.
Open PNE, navigate to Sales Register, and select QuickPay Ticket Management.
Locate and restore the QuickPay ticket.
Replace the temporary QuickPay Service placeholder with the specific services or products sold.
Save or complete the ticket using your standard Sales Register workflow.
Exporting Payment Activity
Empower your practice with flexible CSV exports to review and reconcile activity effortlessly. Exports are available from the Payments, Tickets to Pay, and QuickPay screens. The exported file accurately reflects your active screen context, including any applied filters, search terms, sort orders, locations, and custom date ranges.
Exporting a CSV
Open your desired screen and apply any necessary filters or criteria.
Tap the Export icon and review your Applied Filters.
Confirm your timeframe and tap Export CSV.
Use your device's native share sheet to save or securely send the file.
Selecting a Timeframe or Date Range
Choose a preset (like Today or This Week) or select Custom Range.
Select a Start Date and End Date. The start date cannot fall after the end date.
Confirm the range and export.
CSV File Details
Structured fields provide precision for reconciliation. These include Merchant ID, Location, Client Name, Ticket Number, Source, Subtotal, Tax, Tips, Fees, Total, Payment Status, and Payment Method. The Source field clearly identifies if the payment originated from QuickPay.
For security and compliance, full card numbers, CVVs, raw token values, and other sensitive payment details are intentionally excluded from all exports.
Additional Mobile Payment Capabilities
Tap to Pay on iPhone: Turn your iPhone into a payment terminal. Accept contactless payments without any additional hardware, making it easier to collect payments wherever you are.
Built-In Tipping for a Seamless Checkout: Patients can now add a tip directly during the payment flow, making checkout smoother for everyone. Payments now clearly separate the base amount, discounts, and tips, giving both staff and clients better visibility into every transaction.
Built-In Refunds & Voids: Handle payment adjustments without leaving the app. You can now process voids before settlement and issue refunds after—all within PatientNow Go.
Multi-Location Payment Support: Easily switch between locations while on the go. Payment settings automatically adjust based on your selected location, ensuring everything is processed correctly.
Dedicated Mobile Payment Queue: Keep mobile payments organized and easy to manage. A new PatientNow Go button in PNE sends tickets directly to a dedicated mobile payment queue—no more relying on the On Hold queue.
Optimized for iPad & Tablets: A redesigned layout improves usability on larger devices, giving providers and staff a smoother experience throughout the day.
Role-Based Access & Security Controls: Payment access is limited to authorized users, helping ensure consistency and accountability across your team. PatientNow Go is designed to keep payment data secure while giving your team confidence at checkout; sensitive card details are never logged or exposed.
Troubleshooting
If QuickPay is not visible: Confirm it is enabled in Company Settings and you are viewing the Tickets to Pay screen.
If a customer cannot be found: Ensure your search contains at least three letters.
If the payment button is inactive: Verify the amount is greater than $0.00, pricing has loaded, and the system indicator says "Ready".
If a ticket shows "QuickPay Service" in PNE: This is normal. Use the QuickPay Ticket Management report to restore the ticket and update the exact items sold.
If an export looks incomplete: Check your active filters, date ranges, and locations, as the CSV only captures records matching your precise screen context.
Frequently Asked Questions (FAQs)
Q: Why does QuickPay use a default "QuickPay Service" placeholder instead of an "Other Item"? A: The system uses this temporary placeholder to prioritize rapid checkout in high-speed environments. To prevent business analytics (such as service-to-retail or service-to-client ratios) from being distorted, the best practice is to restore the ticket in PNE, add the actual products or services sold, and zero out the price of the QuickPay Service line rather than deleting it. Zeroing out the line preserves the history that the transaction originated as a QuickPay payment while keeping your quantity metrics clean. Looking ahead, future versions plan to allow practices to pre-configure up to 10 of their own selectable items for QuickPay.
Q: Does the "QuickPay Service" placeholder impact staff commission plans? A: The temporary placeholder is treated as distinct on the backend and does not trigger standard commission calculations. To ensure staff are compensated correctly, managers must remain vigilant about updating these placeholder tickets to reflect the actual services or products sold.
Q: Is a customer name required to process a QuickPay transaction, or can we bypass this step? A: Yes, a customer profile must be selected or created to proceed, as all payments must be associated with a specific profile to remain traceable. While you could theoretically create a "default customer" profile to speed up event sales, this is highly discouraged because mapping multiple payments to a single generic profile makes individual transaction histories nontraceable.
Q: Can we toggle tax on or off during the QuickPay checkout process? A: Tax cannot be toggled directly within the mobile flow; its application is determined by your location's tax settings in PNE. If tax is enabled for your location, it applies automatically. When selling preset packages with fixed total costs, enter the appropriate total amount during checkout; any final tax adjustments can be resolved when the ticket is restored and reconciled in PNE.
QuickPay Best Practices
Reconcile with Intention: Establish a standard routine—such as at the end of the day or immediately following an event—to restore QuickPay tickets, add the correct items, and zero out the placeholder. This maintains complete transparency for both inventory tracking and financial reporting.
Maintain Traceability: Always take a brief moment to search for or add the customer’s actual profile during the checkout flow rather than relying on a default "Event" client. Accurate customer matching ensures that treatment records and transaction histories remain secure and seamless.
Monitor Payment Readiness: Always verify that the payment readiness indicator in the top right corner of the screen displays "Ready" before asking the patient to present their card or device. This prevents card-reading delays and keeps the checkout flow fluid.