Med spa payment dependency register
Separate payment records, customer balances and clinical systems before comparing providers.
No signup. Enter reference codes, add records and download a CSV. Entries stay in the browser tab. Filled fields do not establish completion, approval or compliance.
| Nonclinical payment workflow | Current product and version | Required record reference | Migration or export evidence | Compatibility proof | Responsible staff role | Unresolved question |
|---|---|---|---|---|---|---|
| Package purchase and remaining credit | Booking-platform-example | Package-ledger-test | Export procedure requested | Office-role | Verify package balance after migration |
- Starting rows are fictional. Use internal references, not personal or confidential records.
- Missing required fields stay visible. Filled fields do not prove approval, compatibility or legal compliance.
- Download the CSV to approved business storage. Reloading clears your browser edits.
- No health information, personal contacts or card credentials. Confirm provider eligibility for the actual services.
A med spa comparing Square alternatives should map software dependencies before moving payments. Your appointment calendar, deposits, package balances and stored-payment arrangements might rely on the current account. A lower processing quote is incomplete if replacing payments also changes how staff book visits or retrieve financial records. Identify the affected workflows before selecting another provider.
Start with business eligibility. Describe the services and payment activity accurately to the prospective processor. Square's payment terms identify unsupported business activity and account conditions. Those terms are not proof every medical spa is unsupported, and another provider's approval is not automatic. Request written acceptance for your actual business model instead of relying on a general healthcare label.
Use with this guide
recurring-payment migration cost
Include recurring-payment migration cost when comparing a replacement processor.
marketing and clinical record separation
Keep marketing and clinical record separation intact during the dependency review.
Browse the complete medical spa guides and worksheets.
Verify services and nonclinical dependencies
Use the payment dependency register to list the workflow, current service, required record, proposed destination and unresolved test. The missing-field output flags incomplete decisions. Its example records are fictional. Keep patient names, treatment histories and payment credentials out of the public worksheet. The register is an operational planning aid, not a clinical record system or protected patient-data repository.
Separate financial records from clinical information. Your staff need the payment amount, transaction reference, account balance and approved business contact process. They do not need to copy symptoms, diagnoses or treatment notes into a processor comparison spreadsheet. Review the data permissions and agreements appropriate to your business before changing systems. This article makes no determination about your practice's specific healthcare privacy obligations. Include recurring-payment migration cost when comparing a replacement processor.
Separate payment records from clinical systems
List deposits and prepaid packages independently. A customer might hold an existing package balance while booking a new appointment requiring a deposit. Confirm where the balance lives and who adjusts it after a refund or cancellation. A transaction export does not necessarily recreate an unused-package ledger. Match the financial records to the underlying service system before closing access.
Stored card information and recurring payment information for customers should also be compared. Exporting a list of customers does not transfer payment methods and permission to process recurring payments for example. Ask the provider if they support migration of such information and what action customers need to take. Also ask what authorizations will remain in place. Do not tell staff to manually re-enter card information into a new account.
Match package and recurring workflows
Square's fee schedule distinguishes in-person, online or invoice, and manually entered or stored-card channels. Check your actual plan and account rates. Price the proposed provider against the same collection pattern and required software. Include retained subscriptions during the transition. A replacement counter terminal covers only part of the comparison if your booking service still processes remote deposits.
For a fictional dependency register, the appointment calendar remains with the current software, counter payments move to a proposed account and the prepaid balance export is unresolved. The worksheet highlights the empty export evidence. The next action is to test the permitted balance transfer or retain access, not to assume the new terminal reconstructs every customer's package entitlement.
Sources for this section: Square: payment terms, settlement and reserves · Square: current payment fees and plan differences
Test migration evidence before switching
Test out nonclinical test cases with fake data in a test environment to test out functions such as to record a deposit, final balance, cancelled appointment, partial refund for a package. Make sure all payments go into settlement and that staff can view correct financial information for each customer. Note that a scheduled appointment does not mean that you are able to treat that patient for their scheduled appointment, and that payment of an invoice does not guarantee of a particular outcome for a treatment.
The communication tool and appointment reminders should be separate to the payment processing and have different purposes to the messages sent as marketing. Ensure that all contact information and restrictions are recorded on the system that you are migrating across and that person is responsible for the transition. Keep marketing and clinical record separation intact during the dependency review.
Retain verified product scope
BlueFinch's toolkit pages describe the available business products and their activation requirements. Customer loyalty is an optional paid addition, not a clinical membership ledger or electronic health record. BlueFinch does not promise a direct connection to Square or every medical-spa platform. Ask for the specific supported payment arrangement before changing software your staff depend on.
Your comparison is ready to be used when all workflows have a destination that is supported by the alternative, you have observed the test case work and noted any outstanding rows, captured the retained monthly subscription for each provider on the comparison, who is the contact for any old refunds or disputes, reviewed the first statement from each provider and then the first few months of financial statements from the provider that you chose.
Sources for this section: Square: payment terms, settlement and reserves · Square: current payment fees and plan differences · BlueFinch: customer loyalty scope and terms
Primary sources
BlueFinch last reviewed these sources on October 4, 2026. Payment rules and state requirements can change.
- Square: payment terms, settlement and reserves
- Square: current payment fees and plan differences
- BlueFinch: customer loyalty scope and terms
Use this page for general business information. It is not legal, tax, or accounting advice.