What is a virtual terminal?

The essential definition

Current official materials from PayPal and Square describe a virtual terminal as a browser-based way for a merchant to manually enter card payments. PayPal calls its product a browser-based register for manual credit and debit card entry. Square says its Virtual Terminal lets a business charge a customer from a web browser and identifies remote billing and phone payments as common uses.

Those provider examples establish the core concept without creating a universal feature list. The virtual terminal is the staff-facing interface. It is not the customer's physical card, a countertop terminal, or the entire processing network behind the transaction. For a step-by-step view, read how a virtual terminal works.

What a business user does

A virtual terminal can reduce the need for dedicated checkout hardware in a staff-assisted workflow, but it does not remove the need for a clear operating procedure. The business still needs to decide who may use the tool, how an order is matched to a transaction, and how sensitive information stays inside designated payment fields.

How it differs from nearby payment tools

• Physical card terminal: A customer-present device reads a card or contactless wallet. A virtual terminal usually relies on a business user entering information through a browser. See how a credit card terminal works.
• Payment link: A link generally sends the customer to a hosted payment experience where the customer enters the payment details. Learn what a payment link is.
• Hosted invoice page: An invoice payment page connects a customer-facing payment experience with an invoice or balance. Review hosted invoice payment pages.
• Payment gateway: A gateway or connected provider service carries transaction data within an electronic payment flow. The virtual terminal is the interface the employee sees, not a synonym for every service behind it.

The right distinction is based on who enters the payment details and where that entry happens. If an employee types information supplied during a phone order, the workflow may be a virtual terminal. If the customer enters information on a provider-hosted page, the workflow is closer to a payment link, invoice page, or online checkout.

When a virtual terminal may fit

A business may evaluate a virtual terminal when it receives occasional phone or mail orders, completes service work before collecting payment, handles a custom order away from a conventional checkout, or needs an authorized employee to initiate a remote transaction. It can also be useful when the transaction begins through a conversation rather than a self-service shopping cart.

It may be a weaker fit when most customers are standing at a counter and can use a physical terminal, or when the business would rather have remote customers enter their own payment details through a hosted page. A merchant should map the actual customer journey before selecting a tool. Volume, staffing, recordkeeping, payment methods, and the desired customer experience all shape that decision, but no one workflow is automatically best for every business.

Questions to ask during evaluation

• Order source: Which phone, mail, service, or other remote-order situations need staff-assisted payment entry?
• User roles: Can each employee have appropriate access, and can the business review activity without sharing credentials?
• Required fields: Which transaction, customer, and order-reference fields are available or required?
• Customer communication: How does the tool produce or send a receipt, and which customer contact details does it use?
• Record matching: Can the team connect the provider's transaction record to its invoice, work order, or internal reference?
• Alternatives: Would a physical terminal, payment link, invoice page, or ecommerce checkout better match who should enter the details?

Confirm answers in current provider documentation and in the account configuration being evaluated. A feature shown by one provider should not be assumed to exist in another product.

Keep payment entry privacy-safe

Enter sensitive payment information only through the provider's designated payment interface. Do not request or accept full card numbers, security codes, passwords, bank credentials, complete account numbers, or secret API keys through ordinary email, text messages, chat, shared notes, or a general contact form.

Give workers only the access needed for their duties, follow the provider's current sign-in guidance, and remove access when responsibilities change. A short staff procedure should identify the approved screen, the non-sensitive order reference to record, how to read the displayed result, and whom to contact when something is unclear. The provider's documentation and the business's approved policies remain authoritative for the specific account.

Common questions