Can a virtual terminal accept keyed payments?

Yes, many virtual terminals are designed to let an authorized business user manually enter card details and submit a payment from a web browser or provider dashboard. This is commonly called a keyed or manually entered payment.

The exact workflow is not universal. A provider may require the feature to be enabled, limit access to users with payment permissions, request particular billing details, or offer a different remote-payment method. Merchants should confirm the available fields and account settings before relying on a virtual terminal for phone, mail, or other card-not-read transactions.

What a keyed virtual-terminal payment means

A keyed payment begins when a trained user types payment information into the provider's hosted virtual-terminal screen instead of reading the card with a chip, tap, or swipe device. PayPal describes a virtual payment terminal as a browser-based interface where a merchant manually enters card details. Square likewise documents manual card entry through its Virtual Terminal when a customer or payment card is not physically present.

The virtual terminal is the interface used by the business. It does not mean that every account has identical controls or that every card and transaction type will be available. For more background, compare what a virtual terminal is with the broader walkthrough of how a virtual terminal works.

What the operator may need to enter

Transaction details

The screen may ask for an amount, transaction type, invoice reference, order description, or other business record. The exact fields and terminology vary by provider and selected workflow.

Card details

Provider instructions may request the card number, expiration date, and security code. Square also identifies the billing postal code for its manual-entry workflow. Required fields should be taken from the provider's current screen and documentation rather than from a generic checklist.

Customer or billing details

Name, billing address, email, or phone fields may be required, optional, or unavailable depending on the provider and account settings. Enter only information needed for the transaction and approved business recordkeeping workflow.

User authorization

Some providers restrict virtual-terminal checkout to account owners or team members with the relevant permission. Businesses should give each approved user appropriate access instead of informally sharing a general login.

When the answer may be no

A business should not assume that manual card entry is active merely because a virtual-terminal menu appears. The feature may be disabled in checkout settings, unavailable for the selected account or payment method, restricted by the user's role, or blocked while a different processing mode is active. Square, for example, documents a setting that enables manual card entry and notes that it is not available while processing offline payments.

A declined transaction also does not prove that the virtual terminal lacks keyed-entry capability. Incorrect or incomplete details, an issuer response, provider controls, or account configuration can affect the outcome. Staff should follow the message shown by the provider and use official support channels rather than repeatedly changing customer information.

If the provider does not offer keyed entry for the intended workflow, a hosted invoice page or payment link may let the customer enter their own details. See how card payments on invoices work for a separate customer-facing approach.

A careful operating workflow

Confirm the use case. Identify whether the payment is being taken by phone, from a mail order, at a workstation without a reader, or through another documented business process.
Verify account access. Check that the operator has an individual authorized account or role and that manual entry is enabled for the correct business location or account.
Use the provider's hosted screen. Enter only the fields requested by the current virtual terminal. Do not transfer card details into a general contact form, support ticket, chat, spreadsheet, or ordinary email.
Review before submitting. Confirm the amount, order reference, and customer-provided details on the provider's review screen. Do not guess at missing payment information.
Record the outcome safely. Keep the provider's transaction reference and ordinary order notes, but avoid copying complete card data into separate business notes.

For access, device, and workspace considerations, review how to secure a virtual terminal. Businesses handling remote transactions can also use the overview of card-not-present fraud to plan staff training and escalation steps.

Questions to ask a provider

Is keyed card entry available for this account, location, transaction type, and user role?
Which fields are required, optional, or validated before submission?
Can individual employee permissions and activity records be configured?
What should staff do when the screen requests additional information or returns a decline?
Which customer-facing alternative is available when manual entry is not appropriate?
Where are the provider's current setup, training, and support instructions?

The Virtual Terminals, Invoicing & Payment Links FAQ hub can help merchants compare related workflows without treating them as interchangeable.

Match the payment workflow to the business

Document how staff receive an order, where payment details are entered, which employees need access, and whether the customer could use a hosted page instead. Then ask the selected provider to confirm the supported virtual-terminal workflow and settings for that account.

Discuss virtual-terminal requirements

Share only business contact information and a high-level workflow description through a general form. Do not submit cardholder data, passwords, bank credentials, complete account numbers, security codes, or secret API keys.

To learn more about how TSYS can help improve the way your organization accepts payments, markets to new customers, or manages its HR responsibilities, get in touch by calling 585-981-8463 to get started.