Every store has this deal. The customer found the truck online, ran the numbers over the phone, and wants to lock it up before someone else does. They're not coming in until Saturday. You need money down tonight.
What happens next at most dealerships hasn't changed since 2005. Somebody in F&I picks up the phone and reads back a card number, or tells the customer to mail a check, or asks them to drive in with a certified check "whenever you get a chance." All three cost you something. Let's price them.
The three old ways, and what each one costs
Card over the phone. Fast, familiar, expensive. Card processing runs 2.5 to 3% of the amount, and phone-in payments are card-not-present transactions, the highest-risk tier a store can take. On a $3,000 down payment, that's $75 to $90 gone before the deal books. Worse: if the cardholder disputes the charge later, card-not-present chargebacks are hard to win, and deposit disputes happen more than anyone likes to admit.
Personal check. Free to accept, slow to trust. The check takes days to arrive and days to clear, and the failure mode is brutal: the car is delivered, the check bounces, and now you're chasing a customer who already has the keys.
Certified check. The gold standard for certainty, and the worst customer experience on the list. The customer has to go to their bank, get the check cut, and physically bring it to you. Deals die in the gap between "I'll come by with it" and the actual drive.
| Method | Speed | Cost to the store | Failure mode |
|---|---|---|---|
| Card over the phone | Minutes | 2.5–3% of the amount | Chargeback after delivery |
| Personal check | Days | Float and follow-up time | Bounces after delivery |
| Certified check | Whenever they drive in | Deals lost to friction | Customer never makes the trip |
| Verified bank transfer | Minutes to start, verified up front | No percentage coming out of the store's side | Flagged payments go to review first |
What a clean remote down payment flow looks like
Whatever platform you use, a remote deposit process worth running has five properties. Hold your current process against this list.
1. The payment is tied to the deal from the start. Not a standalone charge somebody has to match to a deal jacket at month end. The deposit should be created on the deal record, so the money and the deal never separate.
2. You send a link. You never take numbers. The customer should enter their own payment details on a secure page, not read them to your F&I manager over the phone. The store keeping card numbers on sticky notes is how small problems become big ones.
3. It's a bank connection, not a card number. A bank-to-bank transfer skips the card networks entirely. No percentage coming off the top of the deposit, no card-not-present risk tier.
4. Verification runs before the money moves. This is the step that separates a modern flow from a fast one. Before the payment is submitted, you want to know three things: the account is real, the account owner matches your customer, and the funds are actually in there. A bank transfer without verification is just a check that travels faster.
5. The whole thing leaves a record. Who created the payment, when the customer paid, when it was verified, when it settled. When a dispute shows up months later, that record is the difference between a five-minute answer and an afternoon of archaeology.
Verify the funds before the car leaves
The deposit is usually the small money. The real exposure is delivery: a car leaving the lot against a payment that hasn't actually landed. Stores spot-deliver against personal checks and phone-in cards every week, and most of the time it works out. The times it doesn't are the stories that get told at 20 Groups for years.
Verification up front flips the order of operations. Instead of delivering and then finding out, you know before the handoff: real account, right owner, funds present, and a return-risk score on the payment. Your team sees that information and makes the delivery call with it, not on gut feel.
The rule worth writing down
No vehicle leaves against an unverified remote payment. Not because every unverified payment fails, but because the ones that do are expensive enough to pay for the discipline many times over.
The dispute problem nobody plans for
Deposits get disputed. Deals fall apart, customers change their minds, and sometimes someone claims a charge they made never happened. The store's position in that fight depends entirely on its records: what was authorized, when, tied to which deal, with what confirmation.
A phone-in card payment usually has a handwritten note and a receipt. A verified bank transfer should have a full audit trail on every money event, created, verified, moved, settled, that nobody can quietly edit after the fact. That's the difference between arguing and showing.
Where Voltra fits
Voltra Payments is this flow built into the platform your team already works in. The payment is created on the deal, the customer connects their bank once on a hosted page, and verification runs before the money moves: real account, owner match, funds present, return-risk score. Your team sees the results and makes the call. Voltra informs; it never approves or declines a payment.
Payments are processed through regulated U.S. banking partners; Voltra provides the platform and never holds your funds. The customer sees a payment verification fee disclosed up front, and paying remotely is always optional, anyone who wants to pay at the store still can.
For the wider picture on bank-rail payments at a dealership, read ACH payments for car dealerships. For the full cost math on cards, read what credit card fees really cost on deposits.