The first chargeback we ever got at Cork & Candles came eleven months in. A customer had booked a private candle-making party online for ten people, prepaid the whole thing (about $850), attended the event, sent a thank-you email afterward, and three weeks later disputed the charge as "service not received." We won the dispute, eventually. It took fourteen days of submitting screenshots, the booking confirmation, the email exchange, the calendar invite, and the photos we'd posted on Instagram. While the dispute was open, Square held that $850 from our payout.
That was the first time we realized something we hadn't appreciated: card processing isn't a single thing. There are two pricing tiers and two risk profiles, and the difference between them, for an experiential operator, is significant.
The fee gap
Most experiential operators see one number on their merchant statement and think it's the rate. It isn't. Card processing has two tiers.
Card-present transactions are typically priced around 2.5% + 10¢. These are the transactions where the physical card is at your counter. Swiped, dipped, or tapped through your POS hardware. The lower rate exists because the fraud risk is structurally lower. The card is verified, the cardholder is present, and your hardware authenticates the transaction.
Card-not-present transactions are typically priced around 2.9% + 30¢. These are transactions where the card details were entered online, by phone, or through any channel where the physical card wasn't present at your terminal. The higher rate exists because the fraud risk is higher. There's no signature, no chip read, no way for the processor to verify the cardholder was the one initiating the charge.
For a venue doing $30,000 a month in mixed transactions, the difference between processing everything as card-present vs. everything as card-not-present is roughly $135 a month. About $1,600 a year. That's not catastrophic on its own, but it compounds with the second thing.
The chargeback gap
Card-not-present transactions don't just cost more. They're statistically more likely to result in a chargeback.
The numbers vary by category, but for experiential and hospitality businesses, the chargeback rate on card-not-present transactions tends to run three to four times higher than on card-present. Some of that is genuine fraud. A stolen card used to book a service. But the bigger share is what the industry calls friendly fraud: a real customer disputes a real transaction because they forgot they made it, didn't recognize the merchant name on their statement, or are gaming the system to get their money back.
Friendly fraud is especially common in experience businesses for a specific reason. The lag between when the customer pays and when they receive the service is longer than at, say, a coffee shop. They book a paint-and-sip class for three weeks out, prepaid online, and forget about the charge. When they see it on their statement, they don't remember what it was. Some percentage of those become disputes.
The defense against friendly fraud is documentation. A clear booking record, a receipt, an attendance log, communications between you and the customer. The defense is much harder to mount when there's no signed receipt and no card-present authorization.
What we noticed about deposits
Here's the part we wish someone had told us before we set up Cork & Candles' booking policies. The chargeback risk is roughly proportional to how much of the experience was paid online.
We have two ways we collect payment for a private party:
Full prepay online. $850 for ten people. All online, all card-not-present. Chargeback risk is real, and if it happens, your exposure is the full $850.
Deposit-only with balance in-person. $250 deposit online (30%), $600 balance paid by card-present transaction at the event. Chargeback risk on the deposit is still real, but capped at the deposit amount. If the customer disputes, even successfully. You lose at most $250, not $850.
We moved to the deposit model for private events about eighteen months in. Two things happened: our chargeback rate on private events dropped meaningfully (the deposit acts as a commitment device, plus the in-person card swipe is harder to dispute), and the chargebacks we did get were capped at the deposit amount.
The trade-off isn't free. Asking for a balance at the event means more administrative work day-of, occasional payment friction, and you carry the risk of the customer not paying the balance at all. We've never had that happen with corporate clients. We've had it happen twice with private parties, and in both cases the host paid before the class ended after we politely asked.
When full prepay still makes sense
Deposits aren't always the right answer.
For public classes, your standard Friday-night paint-and-sip with twelve seats from twelve different customers. Full prepayment is operationally cleaner. Tracking twelve separate deposit balances and chasing twelve people for the rest of their tab at the door is more friction than the chargeback math saves.
For low-cancellation venues, a winery doing $40 tasting reservations, where no-show rates run under 10%. The deposit-vs-prepay math tilts back toward prepay. The friction of taking the balance in-person outweighs the chargeback exposure.
For online-only experiences, virtual classes, gift card sales, anything where there's no in-person event. You have no choice but to take it all online. Documentation becomes your only defense.
The refund policy that holds up
A few specific things we learned about defending against chargebacks, the hard way:
- Your refund policy must be visible at checkout, not just in a footer somewhere. We made it a checkbox the customer has to tick before submitting payment.
- Photograph the actual experience. We post Instagram stories from every class. When a chargeback comes in months later, we can show the disputed customer was there.
- Save the email confirmation, the calendar invite, and any messages between you and the customer. Square's chargeback portal will ask for all of it.
- Communicate proactively. We email customers their booking confirmation, a day-before reminder, and a thank-you after. Three touchpoints with the merchant name on them reduces friendly-fraud disputes by a meaningful margin.
What we built into ArtistryHost
The pricing-tier and chargeback story is one of the reasons ArtistryHost separates deposits from balance payments architecturally. The deposit is processed online at booking. The balance is processed in person at the event, and when it is, it gets routed through Square's card-present flow, which means lower processing fees AND lower chargeback risk.
Most booking platforms treat all payment as one thing. Bookeo's Square integration, for example, runs every transaction through Square's E-commerce endpoint. Even when your guest hands you a card at the host stand, the platform processes it as card-not-present, because that's the only flow it knows.
We separated them because we got tired of paying card-not-present fees on transactions that were genuinely card-present. And tired of fielding disputes on transactions that could have been signed for at the venue.
A small architectural detail. Worth real money over a year.