CardConnect's virtual terminal: who actually needs one

The virtual terminal is one of the quieter pieces of the CardPointe platform, but for certain business models it's the single most-used feature.

What a virtual terminal is for

A virtual terminal is a secure, browser-based screen where a staff member can manually type in a customer's card number, expiration date and billing details to process a payment — no physical card reader required. It's built for situations where the customer isn't standing in front of a register: phone orders, mail-order and telephone-order (MOTO) businesses, invoicing a client after a service call, or taking a deposit over the phone.

Where it fits well

• Service businesses that quote a job, then charge by phone once the work is approved.
• Businesses that take mail or phone orders alongside a retail counter.
• Professional offices — clinics, studios, consultancies — invoicing clients who pay by card.
• Anyone occasionally processing a refund or an adjustment outside a normal checkout flow.

Where it's the wrong tool

If a business only ever takes payments with the card physically present — a coffee shop, a typical retail counter — a virtual terminal isn't a meaningful part of daily operations, and it's worth asking whether any associated fee for it is really necessary. Card-not-present transactions keyed manually also generally carry higher interchange costs than a chip or tap transaction, since there's less proof the physical card was present, so leaning on a virtual terminal for transactions that could otherwise be tapped or dipped can quietly raise your effective rate.

Security considerations

Because a virtual terminal involves a human typing sensitive numbers, it's worth pairing it with sensible internal controls — limiting which staff accounts can access it, requiring a reason code or note on manually keyed transactions, and reviewing refund activity periodically. None of that is CardConnect-specific; it's good practice for any card-not-present tool.

Related reading