The short version
- Do not launch until the processor agreement, state review, network rules, terminal, invoices, signs, and receipts agree.
- Test every payment channel and card type the shop actually accepts, including refunds.
- Measure customer complaints, payment mix, processing cost, funding, and reconciliation after launch.
A dual pricing launch checklist should begin everywhere except the power button. Terminals are usually easy. Trouble shows up in the estimate with one price, the text link with another, the advisor using the wrong name, or the first debit card nobody bothered to test.
This is the list we would want beside an independent shop owner before the first live transaction. It follows a repair order from estimate to receipt. It is an operations guide, not legal advice and not a substitute for written approval from the processor or acquirer.
1. Build the baseline before comparing offers
The baseline keeps the comparison honest. Without it, a provider can hold a narrow advertised rate next to the shop's entire current bill and call the difference savings. It also tells us whether enough volume is actually credit. A shop full of debit cards may have very little to move.
- Collect three complete processing statements and any separate equipment or gateway invoices.
- Calculate the effective rate for each month and for all three months combined.
- Separate credit, debit, prepaid, ACH, check, cash, financing, fleet, and warranty volume where possible.
- Record transaction count, average ticket, keyed volume, payment-link volume, refunds, and chargebacks.
- List every system that creates, approves, collects, or reconciles a repair order.
- Write down the current contract end date, cancellation terms, and equipment ownership.
2. Get the complete program in writing
Read the equipment paragraph slowly. Free should mean there is no terminal price and no lease payment, not that a four-year lease is hiding under a different heading. The same goes for no contract. The cancellation section should agree with the sales page.
Before signing, ask the provider to mark which charges disappear, which stay, and which only happen after an event such as a chargeback. If the answer will not fit in writing, it is not ready for your bank account.
- Program name and definition of the regular price
- Credit, debit, prepaid, commercial, rewards, mobile wallet, keyed, stored, and payment-link treatment
- All monthly, transaction, PCI, gateway, equipment, batch, chargeback, and other fees
- Contract term, renewal, cancellation, funding, reserve, and equipment return terms
- State availability and processor or acquirer approval
- Required signs, notices, estimate language, terminal display, and receipt language
- Refund and partial-refund procedure
- Support contact and replacement-terminal procedure
3. Map the repair order from estimate to receipt
A standalone terminal can sit beside many shop-management systems without replacing them. That does not mean the repair-order total will move over by itself. If someone must type the amount twice, decide who checks the match before a decimal error reaches the customer or the deposit.
- Create or receive the initial estimate.
- Show the applicable pricing explanation before authorization.
- Repeat the explanation when additional work changes the total.
- Generate the final invoice with consistent prices.
- Collect payment at the counter, through a link, or by another approved channel.
- Produce a receipt that matches the payment method and amount.
- Reconcile the deposit to the repair order.
- Handle voids, refunds, partial refunds, chargebacks, and warranty adjustments.
4. Run live tests before the first customer
Use small live amounts, then save every receipt and screen. Do not wave off a failed test as something the terminal will sort out later. If the debit card, wallet, link, or refund does not match the written program, stop before a real customer finds the problem for you.
| Test | What to confirm |
|---|---|
| Credit card | Expected price, terminal display, receipt, funding |
| Debit card | Correct identification and treatment |
| Prepaid card | Correct identification and treatment |
| Mobile wallet | Same policy as the underlying card type |
| Keyed transaction | Pricing, added risk, and fee treatment |
| Payment link | Disclosure before confirmation and matching receipt |
| Full and partial refund | Correct amount and customer record |
| Terminal outage | Documented fallback that preserves disclosure |
5. Train the team and measure the first 90 days
Activation is the start of the test, not the end of the project. Review the first week while conversations are still fresh. At 30 and 90 days, compare statements and customer behavior. The expected savings should be visible without a new pile of reconciliation mistakes or angry pickup calls.
- Give every service advisor one approved two-sentence explanation.
- Place the supplied sign where prices are discussed and payment is accepted.
- Add matching language to estimates, texts, invoices, and payment links.
- Define who can resolve a disclosure complaint and when an exception is appropriate.
- Track effective rate, total fees, credit and debit mix, funding time, refunds, chargebacks, complaints, abandoned repairs, and repeat visits.
- Review the first week, first month, and first quarter with the processor.
Questions business owners ask
How long should an auto shop plan for a dual-pricing launch?
The timeline depends on underwriting, equipment, software, state review, and staff readiness. Do not choose a date until the agreement, disclosures, terminal tests, and training are complete.
Can the new terminal work beside the shop's current POS?
A standalone terminal can work beside many systems without direct integration. Automatic transfer of repair-order totals and reconciliation varies by system and configuration.
What should the shop measure after launch?
Track total cost, effective rate, payment mix, complaints, refunds, chargebacks, funding, reconciliation errors, abandoned estimates, and repeat business.
Primary sources
BlueFinch reviewed these sources on August 11, 2026. Payment rules and state requirements can change.
This page provides general business information, not legal, tax, or accounting advice.