Virtual terminals for small business.

A virtual terminal is a secure web page where you type in a customer's card details to take a payment — no card reader, no hardware, just a browser. It's built for the sales where the card isn't in front of you: phone orders, mail orders, invoice follow-ups, and deposits.

And the merchant-account question has a short honest answer: every virtual terminal runs on a merchant account. The choice isn't whether one exists — it's whether it's your own dedicated account or an aggregator's shared one. That single choice drives your rate, your payout stability, and even whose name shows up on your customer's statement, so let's take it properly.

How a virtual terminal works

Behind the web form, a virtual terminal is a front end to a payment gateway. You key the card number, expiry, security code, and usually the billing ZIP; the gateway encrypts the data, sends it through a processor to the card networks for authorization, and shows you an approve or decline in a couple of seconds. Settled funds land in the merchant account behind the gateway — which brings us to the question everyone searches for.

"Without a merchant account" — what that actually means

Search results promising a virtual terminal "without a merchant account" are describing an aggregator (also called a payment facilitator or PayFac). Providers like PayPal and Square board you in minutes as a sub-merchant under their own master merchant account — so you skip individual underwriting, but you're transacting on a shared account governed by their risk rules. The alternative is a dedicated merchant account in your business's name, underwritten through an ISO or acquirer. Neither is wrong; they trade off differently:

The pattern most small businesses follow: start on an aggregator because it's instant, then move to a dedicated account once keyed volume is steady — because at that point the flat rate and the hold risk both start costing real money.

When a virtual terminal is the right tool

• Phone and mail orders. The customer reads the card; you key it while they're on the line and confirm approval before hanging up.
• Invoice follow-ups. A customer calls to pay an outstanding invoice — you take the payment on the spot instead of waiting on a check.
• B2B remote payments. Purchasing departments routinely pay by corporate card over the phone — see B2B card processing.
• Deposits and balances. Take a booking deposit today and charge the stored card for the balance when the job's done.

And when it's not: if the customer and card are physically in front of you for most sales, keying is the wrong habit — it costs more per transaction and carries more fraud liability than a chip or tap read. Card-present volume belongs on real hardware like the PAX A920Pro running Lifted Pay; keep the virtual terminal for the sales that genuinely happen remotely.

The economics of keyed entry

Card networks price interchange — the wholesale cost of a transaction — by fraud risk, and a keyed card that was never physically read is riskier than a chip or tap in person. So Visa's published U.S. interchange schedule (and Mastercard's equivalent) places card-not-present and keyed categories meaningfully above card-present retail categories. Whatever pricing model sits on top, a keyed sale starts from a higher wholesale cost than the same card tapped on a terminal.

Two levers pull that cost back down:

• Level 2/3 data on commercial cards. Business, purchasing, and government cards qualify for lower interchange when enhanced transaction data is submitted — and keyed B2B payments are exactly where those cards show up. See Level 2/3 processing.
• ACH for invoice-style payments. A bank-to-bank payment has no card interchange at all. If the payer is flexible — common in B2B — routing the invoice to ACH/eCheck is usually the single biggest saving available.

If you want to see what your keyed volume is really costing, run a recent statement through our effective rate calculator — keyed transactions are one of the most common places an effective rate quietly climbs.

PCI compliance: smaller scope, but not zero

A hosted virtual terminal is good news for PCI: the card data goes straight from your keyboard into the provider's PCI DSS validated system, and with tokenized storage the card number never lives in your files. But be precise about what that earns you. Because you are keying the card, a virtual terminal merchant typically falls under SAQ C-VT in the PCI Security Standards Council's self-assessment framework — for merchants who key one transaction at a time into a hosted virtual terminal from an isolated device and store no cardholder data electronically. That's a far shorter questionnaire than the full SAQ D, but it is not SAQ A, the minimal form reserved for fully outsourced payment flows where you never touch card data. Anyone telling you keyed entry is "SAQ A eligible" is selling, not advising.

The practical takeaways: key cards from a clean, dedicated device rather than a personal laptop full of extensions, never write card numbers down on paper or in spreadsheets "temporarily," and let tokenization handle storage. How tokenization shrinks scope — and where SAQ A genuinely applies — is covered in tokenization & SAQ-A compliance.

Cards on file and repeat billing

The quiet superpower of a good virtual terminal is tokenized cards on file. Key the card once, and the gateway vaults it and hands back a token; every future charge references the token instead of the card number. That turns one phone call into a standing billing relationship — monthly retainers, deposit-then-balance jobs, repeat wholesale orders — without your business ever storing a real card number, and without asking the customer to read out their card every time.

The virtual terminal in the Lifted merchant portal

Lifted Payments merchants get a virtual terminal inside the merchant portal at pay.liftedpayments.com, alongside transaction history, customer records with tokenized cards on file, and reports. Card payments run on the Maverick gateway; ACH and eCheck run on the NMI gateway — so when a customer is paying an invoice remotely, you can offer the cheaper bank-to-bank rail from the same portal instead of defaulting every payment to a keyed card. It's one piece of the full merchant services stack, on a dedicated merchant account in your name.

What a virtual terminal costs

As of mid-2026, the aggregator tier prices keyed entry at a premium flat rate: Square charges 3.5% + $0.15 for keyed and virtual terminal transactions, and PayPal Virtual Terminal runs 3.49% + $0.09 per keyed transaction plus a monthly fee. No underwriting, but on $10,000 of monthly keyed volume that flat rate is roughly $350 before fixed fees.

Dedicated-account virtual terminals typically pair a modest monthly software or gateway fee with interchange-plus rates, so your cost tracks the actual wholesale interchange of each card plus a disclosed markup. Lifted prices it the same way across every channel: interchange-plus, quoted after we review one recent statement with no application fee, and software at $15/month per device. On real keyed volume — especially commercial cards earning Level 2/3 rates, or invoices moved to ACH — that structure usually beats a 3.5% flat rate by a wide margin.