What is the right way to treat credit card processing fees before tips enter the pool?

Where the money actually goes on a card tip

When a guest adds a tip to a card payment, the processor does not charge you on the food and drink and then wave the tip through for free. It charges on the full authorized amount, which means a slice of the tip itself goes to the processor before the money ever lands in your account. Rates vary by processor, card type and how the card was presented, but the cost is typically a low single digit percentage of the transaction plus a small flat fee per swipe or tap. On any individual check the difference is pennies. Across a busy weekend of card-heavy sales, it adds up to a number an owner notices on the statement.

That creates two honest but different views of the same shift. Your server looks at the tip line and sees the amount the guest wrote. You look at the deposit and see slightly less. Neither person is wrong, and neither person is being cheated, but if nobody has ever explained the gap, it looks like something is being skimmed. In our experience most arguments about card fees are not really about the money. They are about a number changing between the ticket and the payout with no explanation attached. Explain the mechanism once, in plain language, and the temperature drops immediately.

Keep reading: How do you set up a fair tip pool that the whole team trusts?, Should you split tips by hours worked or by role-based points instead?, Why should you keep transparent tip records for every single shift?. See how TipPoolr helps you tip pooling and fair gratuity distribution.

What the rules allow, and where they stop

Federal wage rules have long taken the position that an employer may reduce a card tip by the proportionate share of the processing cost attributable to that tip, and by no more than that. Three limits come with it. You cannot mark the deduction up into a convenient round number that exceeds your real cost. You cannot apply it to cash, where no processing cost exists. And the deduction cannot pull a tipped employee below the minimum wage they are owed for the workweek, which matters a great deal if you take a tip credit. This is a general description of how the framework works, not legal advice for your specific situation.

State law is where operators get surprised. Several states prohibit this deduction outright, and others impose their own conditions on top of the federal baseline, so the same practice can be routine in one state and a wage violation across the border. Before you build the deduction into your close, get the answer for your state from your payroll provider or an employment attorney who works with restaurants. Our practical test: if nobody can state your state's rule in one clear sentence, absorb the fee until somebody can. The cost of guessing wrong on tip deductions is far larger than the amount you were trying to recover. Related: What should restaurants understand about tip pooling rules before starting one?

If you deduct, do it before pooling and publish the rate

Sequence matters more than people expect. Net the fee at the transaction or shift level so that the number entering the pool is the money you actually collected, then run your tip-outs and your split on that figure. If you distribute first and adjust afterward, every employee gets a small correction on their line that they cannot reproduce, and you have manufactured a weekly argument. One clean deduction at the top is visible, checkable and takes about a minute. A dozen small corrections at the bottom are none of those things. Related: Why should you keep transparent tip records for every single shift?

Use your effective rate, not the headline rate on the sales sheet. Pull the last two or three monthly statements, divide total processing cost by total card volume, and use that. Round in the employee's favor, publish the number where staff can see it, and revisit it a couple of times a year rather than every month. On the shift record, keep both the gross card tips and the net card tips as separate fields. When someone asks in March what happened to a Friday in January, you want to answer from the record in ten seconds instead of rebuilding the night from memory. Related: Should you split tips by hours worked or by role-based points instead?

Whether the deduction is worth what it costs you

Before adopting the policy, do the arithmetic on what it actually returns. Take a normal month of card tips, apply your effective rate, and look at the yearly figure. For a lot of small operations the recovered amount is modest next to payroll, while the cost is not just money. It is the extra field in the close, the explanation at every orientation, the question from a new server who heard the last place did it differently, and a small persistent suspicion that management is taking something off the top. Sometimes the number justifies all of that. Often it does not, and it is worth knowing which situation you are in before you commit.

If you decide to absorb the fee, say so out loud. Staff at other restaurants have had it deducted, and hearing that you eat it is a real, cheap piece of goodwill. If you decide to deduct it, be boringly consistent: same rate, every shift, card tips only, written into the tip policy everyone signs. The failure mode we see most is not deducting or absorbing. It is doing both, drifting between them depending on how the week went, at a rate nobody can reproduce. That is what turns a small line item into a trust problem. Related: How do you set up a fair tip pool that the whole team trusts?