What changes in med spas operations
Med spa groups coordinate locations, service programs, staff access, and recurring operational reporting. A central team benefits from a location-first record that keeps quantities and pricing understandable without mixing clinical notes into business administration. Use the workspace for operational counts, access ownership, period status, and document follow-up while keeping sensitive service details out of broad reporting views.
Watch for these gaps
- Putting client or treatment details into a shared billing note
- Using a recurring business unit for a one-time promotion
- Leaving sensitive operational access broader than the role requires
A repeatable payment destination setup workflow
- 01
Open Billing setup and review the organization's configured payment destinations.
- 02
Confirm the standard or fallback destination used by the applicable billing rule.
- 03
Add or update an allowed Stripe account when the current role permits it.
- 04
Confirm the destination status and return to readiness or the rule before processing.
Bring the industry records into the review
For med spas, use location roster with operating state and accountable manager; business service-unit quantities submitted for each cycle; access changes and operational document requests by location as the evidence packet. Keep the franchise and reporting period attached to each record so a reviewer can follow the source without reconstructing the conversation.
What to do when the review finds a problem
More than one organization or Stripe account is in view.
Confirm the destination belongs to the intended organization before adding or editing its routing record.
A new or rotated provider credential is being prepared.
Use the approved key mode and keep the full credential out of notes, screenshots, and worksheets.
The saved destination is not in a ready state.
Resolve verification or webhook setup issues before assigning the destination to a billing rule.
The provider status and organization setup are confirmed.
Recheck the fallback or standard route after the destination is ready.
A common mistake to avoid
Copying a full Stripe key into an operational record while trying to prove that routing is configured.
Before you mark the work complete
A routing readiness record naming the organization destination, non-secret key metadata, verification state, and rules that use it.
- The destination belongs to the intended organization.
- Its provider status is configured and readable.
- Rules and readiness point to the intended route.
Begin with location ownership and role access, then verify that each quantity is a business count rather than a client detail. Check the rule, period, price source, and blank-versus-zero state. Review document requests for unnecessary sensitive content, and confirm that a correction or reopened entry has an accountable reviewer and a clear reason.
Download the med spas review worksheet →A situation to work through
A med spa operator can review location-level service counts without exposing client details, filter to one cycle, and see the organization and effective price beside the quantity. A location manager receives a focused follow-up for an incomplete row, while corporate staff retain the business change history. The workflow keeps operational review separate from confidential service information.
Apply the payment destination setup steps above to this situation. Record the original evidence, the unresolved question, and the person who can answer it before treating the item as complete. This is a planning example, not a customer result.
How are invoice payment destinations prepared?
Review the organization's configured Stripe destinations and the fallback or standard route used by billing. Add or update an allowed account, confirm its status, and return to billing readiness or the rule before processing invoices.
Put the workflow into practice
Granite's payment destinations workspace connects permitted Stripe accounts to billing rules and readiness.
Use this guide to organize your process, then configure the applicable franchises, reporting periods, and billing rules in Granite.