← Back to Glossary

Definition

Virtual Terminal

A virtual terminal is a secure web interface that lets a business manually enter and process a customer's payment details. It is often used for phone orders, invoice payments, remote services, back-office billing, and one-off customer payments.

Unlike a customer-facing checkout, a virtual terminal is usually operated by the merchant or support team. The customer provides payment details through an approved channel, and the business enters the transaction.

Key Takeaways

  • A virtual terminal lets merchants manually process card or payment details online.
  • It is useful for phone orders, remote billing, invoices, and support-assisted payments.
  • Virtual terminal payments are usually card-not-present transactions.
  • Security, permission controls, receipts, and payment records matter because staff handle sensitive payment workflows.

How A Virtual Terminal Works

A team member logs into a payment system, enters the customer's payment details, amount, billing information, and order notes, then submits the transaction for authorization.

If the payment is approved, the business can send a receipt and record the order. If it fails, the customer may need to provide another payment method or contact their bank.

Virtual Terminal Vs Checkout

A checkout is customer-facing. The buyer enters their own payment details and completes the order.

A virtual terminal is merchant-facing. A staff member enters payment information on behalf of the customer.

Spiffy's checkout pages are designed for customer-facing purchases, while virtual terminals are more common for assisted or manual payment workflows.

Common Virtual Terminal Uses

Common use cases include:

  • Phone orders.
  • Manual invoice payments.
  • Coaching or consulting payments.
  • Support-assisted billing.
  • Card updates after failed payment.
  • One-off adjustments.
  • Remote service payments.
  • Back-office order creation.

The use case should decide what records and permissions are needed.

Card-Not-Present Risk

Virtual terminal payments are usually card-not-present transactions. The card is not physically presented, so the business may face higher fraud and dispute risk than with in-person card-present payments.

Clear receipts, billing descriptors, order notes, and customer authorization records can help reduce confusion later.

Security Considerations

Virtual terminals should be limited to trained users. Businesses should avoid writing down card details, sending payment details through insecure channels, or letting too many staff members access payment tools.

Useful controls include user permissions, audit logs, two-factor authentication, tokenization, and clear internal payment-handling rules.

Customer Authorization

Virtual terminal payments should have clear customer authorization. The business should record what the customer agreed to pay, what the payment covered, and whether future billing is involved.

This record matters if the customer later disputes the charge. A receipt alone may not explain the context, especially for custom services, phone orders, or support-assisted billing.

A payment link lets the customer enter their own payment details. A virtual terminal lets staff enter details for the customer.

Payment links can reduce sensitive-data handling because the customer completes the payment directly. Virtual terminals are useful when staff need to help, but they create more responsibility around access, training, and recordkeeping.

Many businesses use both. Payment links work well for repeatable customer-facing collection, while virtual terminals work better for exceptions that need staff judgment or custom context.

Virtual Terminal And Subscriptions

Some businesses use virtual terminals to help customers update payment details or pay overdue invoices. For subscription businesses, this should be handled carefully so the customer understands future billing terms.

Spiffy's subscriptions and customer portal workflows are better suited for customer-managed recurring billing updates when available.

Metrics To Watch

Useful metrics include manual payment volume, approval rate, refund rate, dispute rate, failed-payment recovery, support-assisted payments, and staff error rate.

These metrics show whether manual payments are helping customers or creating avoidable operational risk.

Practical Example

A consulting business takes a phone payment for a custom workshop. A team member enters the amount and card details in a virtual terminal, sends a receipt, and records the service details.

That is a virtual terminal payment. It is useful, but it needs clean records and secure handling.

Summary

A virtual terminal lets a business manually enter and process payment details through a secure web interface. It is useful for assisted payments, phone orders, and remote billing.

For online businesses, virtual terminal use should be controlled, documented, and measured because it often involves card-not-present risk and staff-managed payment workflows.