A social post announces a ticket price. Someone clicks through, gets to checkout, and the total is higher than what was promoted. This is not a pricing error and it is not a scam. Ticketing platforms charge fees per ticket, and by default those fees are added to the buyer’s total at checkout rather than folded into the announced price. If the person who ran the social post did not set fee absorption when the ticket type was created, the checkout total and the promoted number will not match, and now someone has to explain the gap.
What Eventbrite actually charges, per its own pricing page
Per Eventbrite’s organizer pricing page, fetched September 9, 2026, a paid ticket carries two separate charges: a 3.7% plus $1.79 service fee per ticket, which applies to paid tickets only, and a 2.9% payment processing fee per order. Free events carry no ticketing fees at all. The same page states this plainly: publish an unlimited number of free events at no cost, and pay Ticketing Fees only when a ticket has a price attached.
Those fees are billed to the ticket buyer by default. Eventbrite’s help documentation on ticketing fees, also fetched September 9, 2026, describes the mechanism directly: by default, Ticketing Fees are paid by the ticket buyer. When an organizer creates a paid ticket type, they can check a box labeled “Absorb fees” so the fees come out of the ticket price at payout instead of being added on top at checkout. That checkbox is the entire mechanism this piece is about.
Where the fee actually lands, and why it surprises people
Leave the “Absorb fees” box unchecked, and the organizer’s announced price stays intact everywhere they control it: the social post, the event page headline number. But the total the buyer actually pays at checkout is higher, because the service fee and the payment processing fee stack on top there. This is the buyer-absorbed state, and it is Eventbrite’s default.
Check the box, and the outcome flips. The organizer’s ticket price now has the fees built in, or the organizer accepts a lower net payout per ticket. Either way, the number the buyer sees at checkout matches the number in the social post, because there is nothing added on top of it.
This is why two events can advertise the identical price and produce two different checkout experiences. The platform did not change what it charges. One organizer checked a box and the other did not.
The complaint this produces, and who it actually reaches
The shape of the friction is predictable even without a count of how often it happens. Someone sees a social post with a price, buys a ticket, gets to checkout, and the total is higher than the caption said. They reply to the post, tag the organizer’s account, or send a direct message to whoever runs it. [EVIDENCE NEEDED: a sourced figure on how common this complaint is; none is available, so no frequency or percentage is stated here.]
The person who receives that message is often the same person who wrote the social post and did not touch the fee setting when the ticket type was created. That makes this a workflow gap between the person managing the social account and the person configuring the event, not only a finance detail buried in a payout report.
How to check and change who absorbs the fee
- The absorption choice is made when a paid ticket type is set up, using the “Absorb fees” checkbox described in Eventbrite’s own help documentation. It is a per-ticket-type setting, not a single account-wide toggle, so a mixed event with several ticket tiers can have different fee treatment on each one.
- Eventbrite’s documentation states the setting can be changed at any time, but a change only applies to future orders. Anyone who already checked out under the old setting keeps whatever total they paid. That makes the decision effectively final for a social post: fix the setting before the post goes out, not after the first complaint arrives.
- Before writing a price into a social post, open the actual checkout preview for that ticket type and read the total a buyer will see. The announced price and the buyer’s total are two different numbers unless the organizer has checked “Absorb fees.”
- Absorbing the fee changes the organizer’s net payout per ticket. It does not remove the fee itself. The service fee and the payment processing fee are still charged; they simply come out of the organizer’s payout instead of appearing as a separate line at checkout.
What this means for the price you put in the post
The decision has to happen before the caption is written, not after the first reply asks about it. Whoever approves the social copy needs to know which fee setting is on the ticket type in question, then write the price to match whichever total the buyer will actually see. If the fee is absorbed, the announced price and the checkout price are the same number, and the post can say so plainly. If the fee is passed on, the honest version of the post either states the checkout total will run higher, or names the fee structure so the buyer is not surprised.
A mismatch between the announced price and the checkout price is not a platform error worth escalating to Eventbrite’s support. It is a setting on the ticket type that someone can check in a few minutes, and it is worth checking before the post goes out rather than after someone points out the difference.
The same pattern, a platform’s pricing page stating one number while a separate detail changes what actually gets charged or metered in practice, shows up elsewhere in social workflows too. It is worth checking what a usage meter actually counts before promoting a tool built on one, and worth knowing what happens when a social campaign outperforms the plan you picked, since a ticketing fee surprise and a form-tool overage surprise come from the same root cause: a plan or a setting nobody checked before the post went live.
Try followed for wire-service coverage of the tools around your stack
followed tracks how tools that sit next to the social media workflow actually price and behave once real usage hits them, the same way this piece traced one checkout mechanic back to its source. See what the cap actually does when a post reaches more people than expected for the same theme applied to a different tool, and read the rest of the blog for more of that.
FAQ
Why does the checkout total not match the price I posted on social?
Because ticketing fees are charged per ticket and, by default, added to the buyer’s total at checkout rather than included in the announced price. The organizer can change this by checking “Absorb fees” when setting up the ticket type, which folds the fee into the price instead of adding it on top.
Who pays Eventbrite’s fee by default, the organizer or the buyer?
The buyer, by default, per Eventbrite’s own help documentation. The organizer can choose to absorb the fee instead, which changes the organizer’s net payout at payout time rather than removing the fee.
Sources
- Eventbrite organizer pricing page, fetched September 9, 2026.
- Eventbrite help center: how much does it cost for organizers to use Eventbrite, fetched September 9, 2026.