There's a category of small business that gets left out of most payment processing conversations: businesses that take orders by phone, collect payments after completing work, send invoices and then manually collect card details when the client calls to pay, or operate in environments where a card reader simply isn't practical. Contractors, consultants, service businesses, call centers, order-taking operations, nonprofits collecting memberships over the phone — all of these businesses need a way to process card payments without a customer physically present.
A virtual terminal is the answer, and it's simpler than most small business owners expect. This guide explains exactly what a virtual terminal is, how it works, who needs one, what the PCI compliance picture looks like, and how it fits into a broader payment infrastructure alongside other tools like electronic invoicing and the customer vault.
What a Virtual Terminal Actually Is
A virtual terminal is a secure, browser-based interface that lets an authorized user manually enter credit card details to process a payment — without a physical card reader or point-of-sale terminal. It functions like a card-swipe terminal in terms of what it does (authorizes and settles credit card transactions), but instead of reading card data from a physical card, the operator types in the card number, expiration date, CVV, and billing information provided by the customer over the phone, by mail, or by fax.
Because it runs in a web browser, a virtual terminal works on any computer, laptop, or tablet with an internet connection. There's no hardware to purchase, no software to install, and no dedicated device to manage. As long as you're logged into your gateway control panel, you're ready to process.
CyoGate's virtual terminal is included with every internet payment gateway account. Beyond basic payment entry, it supports sales, authorizations, voids, refunds, subscription billing, batch uploads, and detailed transaction reporting — a full payment management environment, not just a data entry form.
Who Needs a Virtual Terminal
A virtual terminal is the right tool whenever a payment is collected without the customer and their card physically present at the point of transaction. The use cases are broader than most merchants initially recognize:
Phone order businesses. Any business that takes orders or bookings by phone and then processes payment — restaurants with delivery operations, mail-order retailers, service businesses that quote and close over the phone, call center operations, and businesses in any category where the customer calls to buy rather than walks in or clicks to checkout. This transaction type is classified as MOTO (Mail Order / Telephone Order) and requires a merchant account specifically approved for card-not-present processing, which is what a virtual terminal account provides.
Service businesses and contractors. Plumbers, electricians, landscapers, cleaning services, consultants, accountants, attorneys, and any business that completes work and then collects payment — often by calling the client after the job is done. Rather than invoicing and waiting for a check, a virtual terminal lets you take the card on the spot (phone or in person without a reader) and settle immediately.
Nonprofits and membership organizations. Organizations that collect dues, donations, or event registrations by phone or mail. A virtual terminal gives staff the ability to process payments during phone calls without routing callers through an online form.
Remote sales teams. Sales representatives who close deals by phone and need to collect a deposit or first payment at the time of sale — before a formal invoice is generated and without requiring the client to complete an online payment form. The ability to process from a laptop anywhere with an internet connection makes the virtual terminal a natural tool for distributed sales teams.
Mail and fax order merchants. Businesses that receive physical order forms with card details written on them — still a real use case in certain B2B and catalog retail contexts — use a virtual terminal to key in those orders in batch. CyoGate's virtual terminal supports batch upload processing for merchants with high volumes of keyed transactions.
Virtual Terminal vs. Card Reader: Which One Do You Need?
The fundamental difference is whether the customer and their physical card are present at the time of payment. If your customer hands you their card (or taps their phone to your reader), a physical terminal or mobile card reader is the right tool — it's faster, carries lower interchange rates for card-present transactions, and provides EMV chip and contactless protection against counterfeit card fraud.
If the customer isn't physically present — they're on the phone, they've mailed an order form, or you're collecting payment after completing remote work — a virtual terminal is what you need. The card-not-present interchange rates are slightly higher than card-present rates (reflecting the higher fraud risk of transactions where the card can't be verified in person), but for most MOTO businesses the rate difference is modest and worth the operational flexibility.
Many small businesses need both. A retail operation that also takes phone orders runs a physical terminal at the counter and a virtual terminal for orders that come in by phone. Setting up both correctly — with the right merchant account type for each transaction environment — is important, because routing card-present transactions through a MOTO merchant account (or vice versa) creates compliance problems and incorrect interchange pricing. Our guide on point of sale vs. ecommerce merchant accounts covers the channel separation principle in detail.
PCI Compliance and the Virtual Terminal
Accepting card details over the phone and keying them into a virtual terminal puts your business in a specific PCI DSS scope — and it's worth understanding before you start processing this way, not after a compliance assessment flags it.
When a customer reads their card number to you over the phone and you type it into a virtual terminal, that card number passes through your environment: it's heard over a phone line, typed on a keyboard, and submitted through your browser. This creates a cardholder data environment (CDE) that PCI DSS requires you to protect. The key requirements for MOTO businesses using a virtual terminal:
No recording of calls that capture card data. If you record phone calls for quality assurance — common in call center environments — those recordings must not capture card numbers. PCI DSS explicitly requires that card numbers be masked or paused-during-recording when a caller provides them. Many call recording systems support a "pause recording" function during card data entry specifically for this purpose.
No storing of CVV after authorization. The CVV (the three or four digit security code) is used to verify card presence at the time of authorization and must not be stored afterward — not in databases, notes, spreadsheets, or any other format. Once the transaction is processed, CVV data must be gone.
SAQ B or SAQ C-VT self-assessment. Most MOTO businesses using a virtual terminal qualify for either SAQ B (no electronic storage of card data, using a standalone dial-out terminal — uncommon for virtual terminal setups) or SAQ C-VT (using a virtual terminal provided by a third-party service provider). SAQ C-VT is typically the right assessment for a CyoGate virtual terminal user. It's a manageable compliance questionnaire that focuses on your access controls, network security, and data handling practices. Our PCI compliance guide for small businesses walks through the SAQ types and what each requires.
Virtual Terminal Features Worth Knowing About
CyoGate's virtual terminal goes well beyond basic card entry. Several features are particularly valuable for small businesses:
Subscription and recurring billing. The virtual terminal supports setting up recurring payment schedules directly from the payment entry screen. Once set up, the gateway handles the recurring charges automatically without requiring the customer to be called again or the card to be re-entered — card credentials are stored securely in the customer vault, not in your system, keeping your PCI scope contained.
QuickBooks integration. If your business uses QuickBooks Pro, Premier, or Enterprise, CyoGate's SyncPay integration processes card payments directly from within QuickBooks — no double entry, no manual reconciliation. Payments processed through SyncPay automatically create the corresponding accounting entries and mark invoices as paid.
Detailed transaction reporting. The virtual terminal control panel provides full transaction history, batch summaries, search and filter tools, and export capabilities. For businesses that need to reconcile payment records against their order management or accounting system, the reporting tools provide the data in usable form.
Card-present support with a magnetic stripe reader. For businesses that occasionally process in-person transactions but don't need a dedicated POS terminal, CyoGate's SwIPe software allows card-present swiped transactions through the virtual terminal using an inexpensive USB magnetic stripe reader connected to your PC. This won't cover EMV chip or contactless transactions, but it's a practical option for businesses with low-volume in-person needs that don't warrant a full POS setup.
Getting Set Up With a Virtual Terminal
The starting point for a virtual terminal is a merchant account approved for card-not-present processing. A standard retail card-present merchant account doesn't cover MOTO transactions — you need an internet or MOTO merchant account specifically underwritten for the card-not-present environment. Once your merchant account is established and connected to a CyoGate gateway, the virtual terminal is available in your control panel immediately.
For most small businesses, setup involves logging into the control panel, familiarizing yourself with the transaction entry form, and running a test transaction before processing live payments. There's no technical integration required — the virtual terminal is a ready-to-use interface, not a development project.
If you're currently collecting card numbers on paper or by phone without a proper virtual terminal setup, getting this right matters both for compliance and for operational efficiency. Apply for a merchant account that covers your card-not-present volume and get a virtual terminal that handles it properly.