--- title: "Salesforce Health Cloud Payments for Med Spas | Eposly" description: "Execute the patient-paid transaction inside Salesforce so payment, packages, and history stay connected to the patient record. Assisted payment execution, not clinical billing." lang: en json-ld: | [ { "@context": "https://schema.org", "@type": "BreadcrumbList", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://eposly.io" }, { "@type": "ListItem", "position": 2, "name": "Industry", "item": "https://eposly.io/industry" }, { "@type": "ListItem", "position": 3, "name": "Premium in-person services", "item": "https://eposly.io/industry/services" }, { "@type": "ListItem", "position": 4, "name": "Med spas", "item": "https://eposly.io/industry/services/med-spas" } ] }, { "@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [ { "@type": "Question", "name": "How do packages and deposits stay on the patient record?", "acceptedAnswer": { "@type": "Answer", "text": "Treatment packages and deposits are executed on the patient record inside Salesforce, so what was purchased and paid stays connected to the record instead of a separate system." } }, { "@type": "Question", "name": "Can you take deposits and split payments for treatments?", "acceptedAnswer": { "@type": "Answer", "text": "Yes. Deposit, split, and partial patient payments run natively on the patient record, which is common for treatment packages and staged courses of care." } }, { "@type": "Question", "name": "How does running the transaction in Salesforce affect governance?", "acceptedAnswer": { "@type": "Answer", "text": "Reducing unnecessary data duplication can simplify governance, access control, and auditability. HIPAA, PCI, privacy, and data-handling requirements are easier to comply with when the whole transaction execution from sales process to payments and customer and patient data handling happens in Salesforce." } }, { "@type": "Question", "name": "What is out of scope?", "acceptedAnswer": { "@type": "Answer", "text": "Eposly handles the commercial, patient-paid transaction. It is not clinical billing, not insurance adjudication, and not a practice-management replacement." } }, { "@type": "Question", "name": "Is it genuinely native to Salesforce?", "acceptedAnswer": { "@type": "Answer", "text": "Yes, 100% native. Same objects, security, and audit model. No middleware, no separate database, no sync." } }, { "@type": "Question", "name": "Can Eposly run med spa payments on Salesforce Health Cloud?", "acceptedAnswer": { "@type": "Answer", "text": "Yes. Eposly executes the transaction inside Salesforce, on the patient record, so medical spa payment, packages, and deposits stay connected to the record as care becomes revenue." } }, { "@type": "Question", "name": "Can it take deposits and split payments for medical spa treatment packages?", "acceptedAnswer": { "@type": "Answer", "text": "Yes. Deposit, split, and partial patient payments run natively on the patient record." } }, { "@type": "Question", "name": "How does this affect compliance?", "acceptedAnswer": { "@type": "Answer", "text": "Executing the commercial transaction in Salesforce can reduce the need to duplicate patient and transaction context into a separate POS database. HIPAA, PCI, privacy, and data-handling requirements are easier to comply with when the whole transaction execution from sales process to payments and customer and patient data handling happens in Salesforce." } }, { "@type": "Question", "name": "Do you handle insurance billing?", "acceptedAnswer": { "@type": "Answer", "text": "No. Eposly handles the commercial, patient-paid transaction, payment processing and medical spa customer intelligence all in Salesforce." } }, { "@type": "Question", "name": "We already use Zenoti or Mindbody. Why Eposly?", "acceptedAnswer": { "@type": "Answer", "text": "Those often run scheduling and operations in their own platforms. Eposly is for providers whose system of action is Salesforce." } }, { "@type": "Question", "name": "Is it genuinely native?", "acceptedAnswer": { "@type": "Answer", "text": "Yes. Same objects, security, and audit model. No middleware, no external database." } } ] } ] --- [![Eposly](/assets/eposly-logo-BB9N99PW.svg)](/) Product By Industry [Customers](/customers)[Partners](/partners) Resources Company [Contact us](/contact) [Home](/)/ [Industry](/industry)/ [Premium in-person services](/industry/services)/ Med spas Services # Salesforce-native payments and POS for med spas When a patient pays, that payment should be connected to their record before they reach the door. Eposly executes the medical spa transaction inside Salesforce, so treatments, packages, and deposits stay on the patient record. [Book a demo](/contact)[Contact us](/contact) ## Can a med spa run payments and POS on Salesforce Health Cloud? Yes. With a Salesforce-native point of sale for medical spas, the transaction executes on the patient record inside Salesforce, so payment, packages, and deposits stay connected to the record as care becomes revenue, without a separate POS database. ## How Eposly fits medical spas Eposly executes the transaction inside Salesforce, on the patient record of medical spas. The consultation is captured in Salesforce, services and packages are selected, payment is executed, and the transaction is connected to the patient record in one flow with no system switch. The Salesforce transaction record stays in Salesforce and uses the org's roles, permissions, field security, and audit controls, while sensitive card data is handled through the connected payment gateway and only the permitted reference or token is retained. Eposly completes the Salesforce stack at the point of care rather than adding a disconnected POS beside it. ## How medical spa payments connect to the Salesforce patient record ![Medical spa POS for Salesforce showing patient payments, treatment packages, deposits, and appointment rebooking captured directly in the Salesforce patient record for Patient 360 reporting.](/images/salesforce-med-spas-pos-patient-record.webp) Eposly's medical spa POS processes in-treatment payments, packages, deposits, and follow-up bookings directly within Salesforce. By capturing every transaction on the patient record, clinics gain a complete Patient 360 view, real-time reporting, and unified customer data for personalized care that drives loyalty. ## What you get and how Eposly works on Salesforce for medical spas - ### Payments on the med spa's patient record Eposly executes the patient-paid transaction inside Salesforce, often Health Cloud, so payment and packages stay on the patient record as care becomes revenue. - ### Medical spa treatment packages and deposits Deposit, split, and partial patient payments run natively on the patient record, suited to treatment packages and staged courses of care. - ### Reduced data duplication Running the transaction in Salesforce cuts duplication, simplifying governance and audit. HIPAA, PCI, privacy, and data-handling requirements are easier to comply with when the whole transaction execution from sales process to payments and customer and patient data handling happens in Salesforce. - ### Salesforce security and audit controls The transaction record uses the org's roles, permissions, field-level security, and audit controls; connected payment services keep their own compliance responsibilities. - ### Tokenized card handling Card data is handled by the connected payment gateway, and only the permitted token is retained in Salesforce. Gateways include Adyen, Stripe, Square, CardConnect, and TSYS. - ### A clear commercial scope Eposly handles the commercial, patient-paid transaction, from pricing and package configuration to compliant payment processing.  ## Salesforce-native by design Every element of the transaction is executed inside Salesforce. No parallel POS system, no reconciliation back from a separate database. - ### Same objects, automations, security, and audit model The transaction lives on the standard Salesforce record with the org's roles, permissions, field security, and audit controls. - ### No middleware, no separate database, no sync The sale is created in Salesforce as it happens, so there is no external POS dataset to reconcile back. - ### PCI-compliant payment gateways connected natively The Salesforce transaction flow connects to gateways including Adyen, Stripe, Square, CardConnect, and TSYS. ![Salesforce AppExchange partner badge](data:image/svg+xml,%3c?xml%20version='1.0'%20encoding='UTF-8'?%3e%3csvg%20id='Layer_1'%20data-name='Layer%201'%20xmlns='http://www.w3.org/2000/svg'%20viewBox='0%200%2032%2032'%3e%3cdefs%3e%3cstyle%3e%20.cls-1%20{%20fill:%20none;%20stroke:%20%233B82F6;%20stroke-miterlimit:%2010;%20stroke-width:%201.5px;%20}%20%3c/style%3e%3c/defs%3e%3cpath%20class='cls-1'%20d='M24.24,9.04c-.83,0-1.62.18-2.33.49-.82-1.76-2.61-2.99-4.69-2.99-1.4,0-2.67.56-3.6,1.46-1.06-1.25-2.63-2.04-4.4-2.04-3.18,0-5.76,2.58-5.76,5.76,0,.58.09,1.14.25,1.67-1.05,1.04-1.71,2.49-1.71,4.09,0,3.01,2.31,5.48,5.25,5.74,1,1.69,2.85,2.82,4.95,2.82,2.28,0,4.26-1.33,5.19-3.26.47.23,1,.35,1.56.35,1.73,0,3.18-1.22,3.53-2.85.55.18,1.15.27,1.76.27,3.18,0,5.76-2.58,5.76-5.76s-2.58-5.76-5.76-5.76Z'/%3e%3c/svg%3e) AppExchange 5.0 [See what Eposly customers say on AppExchange](https://appexchange.salesforce.com/appxListingDetail?listingId=a0N30000000qD0GEAU&tab=r) ## Questions buyers ask ### How do packages and deposits stay on the patient record? Treatment packages and deposits are executed on the patient record inside Salesforce, so what was purchased and paid stays connected to the record instead of a separate system. ### Can you take deposits and split payments for treatments? Yes. Deposit, split, and partial patient payments run natively on the patient record, which is common for treatment packages and staged courses of care. ### How does running the transaction in Salesforce affect governance? Reducing unnecessary data duplication can simplify governance, access control, and auditability. HIPAA, PCI, privacy, and data-handling requirements are easier to comply with when the whole transaction execution from sales process to payments and customer and patient data handling happens in Salesforce. ### What is out of scope? Eposly handles the commercial, patient-paid transaction. It is not clinical billing, not insurance adjudication, and not a practice-management replacement. ### Is it genuinely native to Salesforce? Yes, 100% native. Same objects, security, and audit model. No middleware, no separate database, no sync. ### Can Eposly run med spa payments on Salesforce Health Cloud? Yes. Eposly executes the transaction inside Salesforce, on the patient record, so medical spa payment, packages, and deposits stay connected to the record as care becomes revenue. ### Can it take deposits and split payments for medical spa treatment packages? Yes. Deposit, split, and partial patient payments run natively on the patient record. ### How does this affect compliance? Executing the commercial transaction in Salesforce can reduce the need to duplicate patient and transaction context into a separate POS database. HIPAA, PCI, privacy, and data-handling requirements are easier to comply with when the whole transaction execution from sales process to payments and customer and patient data handling happens in Salesforce. ### Do you handle insurance billing? No. Eposly handles the commercial, patient-paid transaction, payment processing and medical spa customer intelligence all in Salesforce. ### We already use Zenoti or Mindbody. Why Eposly? Those often run scheduling and operations in their own platforms. Eposly is for providers whose system of action is Salesforce. ### Is it genuinely native? Yes. Same objects, security, and audit model. No middleware, no external database. ## Explore capabilities and use cases - [ ### Transaction Execution Learn more ](/product/capabilities/transaction-execution) - [ ### Payments Learn more ](/product/capabilities/payments) - [ ### Assisted Sales Learn more ](/product/capabilities/assisted-sales) ## Ready to run the whole sales process inside Salesforce? See how this would work in your Salesforce setup. [Book a demo](/contact)[Explore capabilities](/product/capabilities) ![Eposly](/assets/eposly-logo-BB9N99PW.svg) ![Salesforce Native app](/assets/salesforce-logo-BiJiXbuA.svg)native #### Product - [Overview](/product) - [Capabilities](/product/capabilities) - [Transaction Execution](/product/capabilities/transaction-execution) - [Assisted Sales & Checkout](/product/capabilities/assisted-sales) - [Configuration & Pricing](/product/capabilities/configuration-pricing) - [Payments](/product/capabilities/payments) - [Flexible payment methods](/product/capabilities/flexible-payments) - [Intelligence](/product/capabilities/intelligence) - [Feature List](/product/features) #### Industries - [Industries](/industry) - [Retail](/industry/retail) - [Services](/industry/services) - [Public sector](/industry/public-sector) - [Manufacturing](/industry/manufacturing) #### Company - [About](/about) - [Customers](/customers) - [Ascendx approach](/ascendx-approach) - [Partners](/partners) - [Contact](/contact) #### Resources - [Blog](/blog) © 2026 Eposly. All rights reserved. [Privacy policy](/privacy)[Terms of service](/terms)