Premium in-person services and healthcare

    The healthcare POS system that runs inside Salesforce

    Build the order on the patient's Salesforce record, apply the agreed pricing, take payment and send the receipt in one flow, without a separate POS to keep in sync.

    Try the interactive demo
    A physiotherapy package on a patient's order in Eposly on iPad
    Order and payment on the patient record

    Eposly is a Salesforce-native healthcare POS system for the patient-paid side of a clinic: point of sale and payments built into Salesforce. Front-desk staff build the order for a consultation, treatment course or programme, take payment at the desk or by payment link, and send the receipt, with the order and payments recorded on the patient record. Eposly runs on core Salesforce alongside Agentforce Health (Health Cloud), and card details stay with the connected payment gateway.

    • Order, payment and receipt in one flow on the patient record.
    • Treatment courses with deposits, payment links and scheduled card payments.
    • No middleware. No second POS database. No reconciling your POS against Salesforce.

    At the front desk

    What makes taking payment in a clinic different?

    The patient is known before they reach the desk.

    The patient is already known

    Their record, history and follow-ups live in Salesforce, not in the payment tool.

    Care happens across channels

    Patients pay at the desk, after telehealth consultations and between visits.

    Treatments come in packages

    Courses of treatment are paid upfront, in parts or over time.

    Patient data needs care

    Every extra system that holds patient and payment data adds compliance work.

    Finance needs a clean trail

    Payments taken outside the patient record have to be matched back by hand.

    Integrations need upkeep

    A connector between a separate POS and Salesforce needs fixing with every Salesforce release and every new clinic.

    A treatment package

    How does Eposly handle a treatment package at the front desk?

    One order against the patient, from booking the package to the last payment.

    1. 01

      Open the patient

      Start the order against the patient's record and find the service or package.

    2. 02

      Build the order

    3. 03

      Take the deposit

    4. 04

      Collect the balance

    5. 05

      Keep the history

    Try the interactive demo →
    The Eposly screen for the selected step

    How payments connect to the patient in Salesforce

    In-clinic, telehealth and follow-up payments, recorded against the patient in Salesforce.

    Healthcare POS on Salesforce: in-clinic, telehealth and follow-up payments recorded against the patient in Salesforce

    What does a clinic need from a healthcare POS system?

    A clinic needs to
    How Eposly handles it
    Capability
    Take payment wherever care happens
    At the front desk and by payment link, through one transaction flow
    Keep payments on the patient record
    Orders and transactions are created in Salesforce against the existing patient record
    Sell treatment packages
    Deposits, split payments and scheduled card payments on one order
    Keep card data out of Salesforce
    The connected PCI-compliant payment provider tokenizes card details
    Work within your access controls
    Records use your Salesforce access controls, permissions and audit capabilities
    Act on every payment
    Flows, Apex and Agentforce can act on each payment as it's recorded, for example booking the follow-up
    Report across locations
    Transaction reporting by location, service and staff member in Salesforce

    What changes for your clinic?

    Staff see what each patient has bought and still owes, so the next session or follow-up doesn't slip. The order, payment and receipt are done once, in Salesforce, so finance stops matching a POS export. And patient and transaction data stay in the org you already secure and audit.

    Payments

    How do clinics take payment in person, by telehealth and by payment link?

    • At the front deskCard, contactless, HSA/FSA card or a split, in one step
    • Treatment packageDeposit at booking, balance at a later visit.
    • Not in the clinicA payment link for part or all of the amount due, after a telehealth consultation or between visits.
    • Scheduled card payments on a treatment planNewA recurring schedule on the patient's saved card that stops once the plan is paid off. Each payment is recorded against the order.
    Setting up scheduled card payments on a patient's saved card in EposlySchedule details: frequency, start date and amount per paymentConfirmation that the payment schedule is active
    100% rental and sales inventory accuracy. 8.5% sales increase year to year.
    Omring, site-reported results
    Omring

    A Dutch senior-care provider running mobility-aid retail and rental on Eposly, on Salesforce Sales and Service Cloud.

    5.0 on Salesforce AppExchange
    Read the Omring story →

    Where do clinics fit within premium in-person services and healthcare?

    Clinics follow the premium in-person services pattern: a known client, an assisted service and payments that can span visits.

    Main industry pagePremium in-person services and healthcareBack to services →Aesthetic treatmentsMed spasLearn more →Memberships and classesGyms and fitnessLearn more →Care equipment sales and rentalMedical equipment and mobility aid retailLearn more →

    Healthcare POS one-pager

    Take this page to your team

    The key points from this page in one document to share with your team.

    By downloading, you agree to our privacy policy.

    Questions buyers ask

    Does Eposly handle insurance billing or claims?

    No. Eposly handles patient-paid transactions: services, packages, products and balances. Insurance billing and EHR-integrated reimbursement stay in the systems built for them.

    How are card details handled?

    The connected PCI-compliant payment provider handles and tokenizes card details, so raw card data is not stored on the patient record. Salesforce keeps the transaction record the workflow needs.

    Can our clinic keep its existing payment processor?

    In most cases, yes. Eposly connects to PCI-compliant payment providers including Stripe, Adyen, Square, CardConnect and Cybersource, so many clinics keep the processor and rates they already have. Eposly doesn't take a fee on each transaction. If you use another provider, ask us and we'll confirm whether it's supported.

    Does Eposly work with our practice and clinical systems?

    Yes. Eposly handles the patient-paid side of the visit: consultations, treatment courses, products, deposits and balances, recorded on the patient's Salesforce record. Scheduling, clinical notes, consent and insurance billing stay in your practice's own systems. If that data is already in Salesforce, for example in Health Cloud, it sits alongside Eposly orders and payments on the same patient record. Systems that aren't connected to Salesforce yet can be integrated as part of the project.

    Can orders and payments be tied to a patient's Agentforce Health (Health Cloud) record?

    Yes. Eposly runs on core Salesforce alongside Agentforce Health (Health Cloud), and your Salesforce setup can record the order and payment against the existing patient record rather than in a separate POS customer database.

    How is a healthcare POS different from a retail POS?

    Retail checkout focuses on products. In a clinic, staff take payment for services and treatment packages, often over several visits, and each payment has to sit with the patient's record and its access controls.

    Do we need middleware to connect a POS to Salesforce?

    No. Eposly runs inside your Salesforce org, so there's no connector between a separate POS and Salesforce to maintain through Salesforce releases or new clinic openings. Card payments are authorised through the connected PCI-compliant payment gateway.

    Bring your clinic payments into Salesforce

    Consultations, treatment courses and payments on the patient record, not in a separate POS.

    Try the interactive demoRead the Omring story →Talk to us →