CRMConnect v3.8 – Multi-Payment Sales Sync (Mindbody → HubSpot)
Multi-payment and split-tender sales now sync to HubSpot at full value: one deal per line item at the correct amount, all tenders (including account and membership balances) counted, and the payment method recorded on each deal.
Applies to CRMConnect: Mindbody → HubSpot v3.8 or higher.
Overview
This release fixes how sales paid with more than one payment method sync from Mindbody to HubSpot, and adds the payment method to every deal.
Before this version, a sale that was paid in more than one way, or partly from an account or membership balance, could arrive in HubSpot with only part of the amount. A sale where the client paid $8,400 might show a deal of $400. Everyday single-payment sales were unaffected, which is why the problem was easy to miss.
What changed in one line: every sale now creates one deal per line item at that item's correct amount, all payment types are counted (including account and membership balances), and each deal records the payment method(s) used.
How a sale becomes deals
CRMConnect creates one HubSpot deal per line item on a sale, not one deal per sale.
If a client buys three things in a single transaction, you get three deals in the Mindbody Sales pipeline. Each deal's Amount is that item's own total (price plus tax). The three deals add up to the sale total.
This is what keeps the numbers correct on mixed sales, where one line might be a membership and another a retail product.
Multi-payment and split-tender sales
Payments in Mindbody are recorded at the sale level, not the item level. When a client splits a payment (for example $50 cash and $80 on card), Mindbody does not tell us which dollars paid for which item, because that information does not exist.
CRMConnect handles this the only accurate way:
- Each deal's Amount comes from its own line item. This is exact and always reconciles to the sale total.
- Each deal also records the payment method(s) used on the whole sale, as context (for example
Cash, Check).
So on a three-item sale split across two payments, you get three deals with the correct per-item amounts, and each deal shows the full list of payment methods used on that sale.
Note: because payments are sale-level, the payment method shown on a deal describes how the sale was paid, not how that specific item was paid. The Amount is item-specific; the payment method is sale-wide.
Account and membership balance payments are now included
The previous version read sales from a report that did not include every tender. Payments taken from an account balance or a membership balance were dropped, which is what caused the missing amounts.
CRMConnect now reads the full sale record, so every payment on a sale is counted, including account and membership balances.
Payment method on each deal
Each deal in the Mindbody Sales pipeline now includes a new property:
| HubSpot deal property | Internal name | What it contains |
|---|---|---|
| MB payment method | mindbody_sale_payment_method | The payment method(s) used on the sale, e.g. Cash, Account, or Cash, Check |
This sits alongside the existing sale properties on the deal, such as Amount, MB amount paid, MB sales tax, MB item purchased, and MB date of sale.
What each deal records
| On the deal | Value |
|---|---|
| Amount | The line item's own total (price + tax) |
| Payment method | All tender types used on the sale |
| Duplicates | None. Each line item maps to exactly one deal |
| Account / membership tenders | Included in the sale total |
Existing deals correct themselves
You do not need to re-enter or re-import anything.
The daily sync re-checks past sales and updates any deal whose amount was previously understated. Sales that were affected before this release will self-correct on the next daily run.
Things to know
- Payment method is set when a deal is first created. A deal that already existed and is only being amount-corrected keeps its original payment-method value until the sale is re-created.
- Walk-in, online, and reserved-status sales still create deals. They are attached to a shared generic contact for that studio, since these sales have no individual client record.
- Refunds and returns (negative amounts) are handled by the same per-item logic and are being validated on live data before wider rollout.
FAQ
A client paid with two cards. How many deals do I get? One deal per item on the sale. If it was a single item, you get one deal at the item's amount, with both payment methods listed on it.
Why doesn't the deal split the amount by payment method? Mindbody does not record which payment covered which item, so any split would be a guess. CRMConnect uses the exact per-item amount for the deal value and lists the payment methods as context.
Will my old, incorrect deals get fixed automatically? Yes. The daily sync updates previously understated deals to the correct amount.