Virtual terminal_

Travel agents and back-office teams still use virtual terminals for phone bookings, balance chases and ad-hoc charges, especially where a payment-link flow is not yet in place. The trade-off is higher PCI scope and more manual evidence handling.

A virtual terminal in a travel back office is one of the highest-PCI-scope surfaces in the business. Every agent screen is in scope, every desktop is potentially in scope, and the controls have to be proven year after year against an auditor. The cost is paid for every booking taken on the terminal, even the ones that could have been done by link.

The travel businesses gradually moving off virtual terminals do it by replacing the recited-card-number flow with a customer-led link or portal flow. The result is the same booking captured with less PCI scope, cleaner audit evidence and a happier customer. The businesses that hold on to virtual terminals usually do so because the operations have ossified around them, not because the trade-off still favours them.

felloh’s virtual-terminal experience keeps booking context attached to every keyed payment so the audit trail and reconciliation work the same way they do for self-serve payments.

The pay virtual-terminal flow tokenises card details on entry so the agent’s screen never holds the value, with the dashboard’s Transactions view recording every keyed payment against the booking. Where the agent can instead send a Payment Link, the customer takes over the entry and PCI scope drops further.

For travel businesses gradually shrinking their MOTO operations, the transition is workable without breaking the agent workflow. Audit trail stays clean, PCI scope shrinks, and the customer experience improves at the same time.