Nobody budgets for card fees. They just show up, buried in the merchant statement, quietly clipping every deposit, every payoff, every "just put it on my card" moment at the desk. One transaction at a time, they don't look like much. Priced across a year of remote payments, they're a line item you'd fire somebody over.
The math, by payment size
Card processing runs 2.5 to 3% of the amount. Phone-in payments sit at the expensive end of that range because they process as card-not-present, the riskiest tier in card pricing. Here's what that means in dollars:
| Payment | Amount | Card fee at 2.5–3% |
|---|---|---|
| Hold-the-car deposit | $500 | $13 – $15 |
| Typical down payment | $2,000 | $50 – $60 |
| Strong down payment | $5,000 | $125 – $150 |
| Negative-equity payoff | $10,000 | $250 – $300 |
That money comes out of the store's side, every time, before the deal books. A store taking a handful of remote card payments a week is paying a real salary's worth of fees a year for the privilege of typing card numbers into a terminal.
Why dealer card costs run high
Three reasons your effective rate is worse than the teaser rate the processor quoted.
Card-not-present pricing. When the card isn't physically swiped or tapped, the transaction processes in a higher-risk tier with higher interchange. Every deposit taken over the phone is in that tier by definition.
Big-ticket amounts. Percentage pricing is designed for $40 retail baskets. Dealership payments are ten to a hundred times that, and the percentage scales with them. The processor does the same work on a $10,000 payoff as on a $100 sale and earns 100 times more.
Rewards cards. The customer putting $5,000 on their card to farm points is doing it with the most expensive card types in the interchange table. Their points are partly your money.
The fee is the cheap part: chargebacks
A chargeback is the cardholder disputing the charge with their bank. The money gets pulled back from the store while the dispute is decided, and card-not-present transactions leave the store in the weakest position to win.
Deposit disputes happen more than anyone admits. Deals fall apart and the customer wants the deposit back faster than your refund process moves. A co-signer claims they never authorized it. Occasionally it's plain fraud: a stolen card number that sailed through authorization and detonates weeks later. If your documentation doesn't tie the authorization to the deal cleanly, you eat the loss, plus the dispute fee, plus the afternoon someone spent assembling evidence.
The delivered-car scenario
The worst version: the down payment came in by phone on a card, the car delivered, and the chargeback landed 60 days later. Now the store is short the down payment on a car it no longer owns, and the recovery path runs through a dispute process built for retail purchases, not vehicle deals.
The standard defenses, and their limits
Stores that have been burned usually land on some combination of three policies: cap the amount you'll take on a card, require the cardholder present with the physical card and ID, or push anything big to certified funds. All three work. All three also add friction exactly where you don't want it, on the remote customer who is ready to commit money right now.
The cap turns "I'll put down $3,000" into "we can only take $500 on the card." The cardholder-present rule turns a committed buyer into a maybe. And certified funds mean the customer's next stop is their bank, not your store.
The bank-rail alternative
The structural fix is to get the payment off the card networks entirely. A bank-to-bank transfer has no percentage of the amount coming out of the store's side, and no card networks means no chargeback machinery built around retail purchases.
The catch, covered in depth in our ACH guide, is that an unverified bank transfer can return like a bounced check. The version worth running verifies before the money moves: the account is real, the owner matches your customer, the funds are present, with a return-risk score on the payment. Your team sees the results and makes the call.
That's what Voltra Payments does, built into the platform your team already works deals in. Payments are processed through regulated U.S. banking partners; Voltra provides the platform and never holds your funds. On the cost side: no percentage of the amount comes out of the store's side. The customer sees a payment verification fee, disclosed up front, covering instant verification of funds and account ownership plus on-the-spot confirmation. And it's optional, the customer who wants to pay at the store still can.
When a card still makes sense
Honest answer: sometimes. A $200 hold on a unit while the customer drives in is fine on a card; the fee is pocket change and the speed matters more. A customer who insists on their card for the points, knows you take it, and is standing in your showroom with ID is a normal retail transaction. The card problem is specifically the big, remote, card-not-present payment. That's the one to move to the bank rail.
For the full walkthrough on taking remote deposits the clean way, read how to collect a down payment remotely.