How does a virtual terminal work?

The short answer

Current first-party materials from PayPal, Square, and Chase describe virtual terminals as browser-based tools for manually entering card payments. PayPal explains that a business user signs in, enters order and card information, submits the transaction, and receives a confirmation. Square describes a web-browser workflow for remote billing or phone payments. Chase describes its Orbital Virtual Terminal as a way to enter remote card payments directly through a browser.

Those examples establish the common pattern, not a universal feature list. A virtual terminal is the staff-facing entry screen. The payment provider and its connected processing services handle the transaction request behind that screen. For a broader view of the electronic payment path, see how online credit card payments work.

A typical virtual-terminal payment flow

1. An authorized user signs in. The employee opens the provider's business dashboard or virtual-terminal page using an approved account. Access should be assigned to the individual who needs it rather than shared informally.
2. The user starts a transaction. The screen may ask for an amount, order reference, customer details, or other provider-defined information. Required and optional fields differ, so the merchant should follow the labels shown in its own account.
3. Payment details are entered on the hosted screen. For a phone or mail order, the employee enters the information through the provider's designated payment fields. Sensitive payment data should not be copied into email, chat, ordinary notes, or a general contact form.
4. The transaction is submitted. The provider sends the request through the connected payment flow and returns a result to the user. A confirmation shows that the request received a response; it should not be treated as a promise about later disputes, settlement, or other account events.
5. The user completes the record. Depending on the product, the workflow may offer a receipt, transaction history, order details, or reporting entry. The employee should verify the provider's response and preserve only the business records the organization actually needs.

How it differs from a physical card terminal

Some providers may connect optional readers or other tools to a browser-based product, while others focus on manual entry. That distinction is product-specific. Confirm supported equipment and transaction types with the provider before choosing a workflow.

When the workflow can be useful

A virtual terminal may suit a business when an employee needs to take a staff-assisted payment for a phone order, mail order, custom invoice, service completed away from a checkout counter, or another remote interaction. It can also give a team a central browser interface when a full ecommerce checkout is unnecessary for that particular order path.

It is not automatically the best option for every sale. A customer-facing hosted payment page or payment link may let the customer enter payment details privately. An ecommerce checkout can support a self-service web purchase, while a physical terminal can be more natural when the customer and card are present. Start with the customer journey, who performs the data entry, and what record must connect the payment to the order.

Details to compare before selecting a virtual terminal

• Transaction workflow: Confirm which staff-assisted payment scenarios the provider supports and which fields appear during entry.
• User access: Review whether team members can have individual accounts, appropriate roles, and an activity trail.
• Order references: Check how the screen records invoice numbers, customer references, descriptions, or other identifiers your team uses for reconciliation.
• Customer communications: Confirm whether and how the product can issue a receipt, and make sure the customer contact details are handled appropriately.
• Transaction management: Review where users find prior transactions and how provider-defined follow-up actions appear.
• Reporting: Determine which exports and filters are available and whether the output connects cleanly with your bookkeeping workflow. The guide to exporting payment-processing data offers related planning questions.

Document the required workflow before comparing products. This keeps the evaluation focused on the business's actual operating needs without assuming that a feature shown by one provider is available from another.

Keep the staff-assisted process privacy-safe

Use only the provider's designated payment-entry interface for sensitive payment information. Do not ask a customer to send full card details through ordinary email, text, chat, or a general web form. Do not paste card numbers, security codes, passwords, bank credentials, or secret API keys into customer notes or internal messaging.

Give each worker only the access needed for the job, follow the provider's current sign-in and account-management instructions, and remove access when responsibilities change. Create a simple call or mail-order procedure that tells staff where to enter payment details, how to confirm the displayed result, what non-sensitive order reference to record, and where to escalate an unexpected response. Provider instructions and the merchant's own approved policies remain authoritative for its account.

Questions merchants often ask