How Software Support Teams Use Virtual Terminals to Take Payments Over the Phone

What a virtual terminal is and why support teams use one

A virtual terminal is a web-based tool that lets you enter a customer's payment card details into a form on your computer, then process that payment without a physical card reader. For software support teams, this means you can take payment during a phone call, through email, or while troubleshooting a customer's issue—without asking them to visit a website or use a separate checkout page.

Support teams use virtual terminals because customers often call with urgent problems and want to pay immediately to get help faster. Instead of transferring them to billing, emailing a payment link, or asking them to log into a portal, you can process the card right there in the conversation. The payment goes through your merchant account (the same one that powers your online checkout), and the customer gets a receipt in seconds.

Virtual terminals are not the same as payment links or invoicing tools. A payment link is a URL you send to a customer; they enter their own card details. A virtual terminal requires you to enter the card details yourself, which means you need to be PCI-compliant (trained and certified to handle card data safely) and your customer has to trust you with that information over the phone.

Key Takeaways

• A virtual terminal lets support staff enter customer card details into a secure web form and process payment without a physical card machine, useful during phone support calls.
• Virtual terminals charge per transaction (usually 2.5% to 3.5% plus a flat fee per swipe) and require your team to be PCI-compliant, meaning trained in secure card handling.
• Most merchant account providers (Stripe, Square, PayPal, your bank) offer a virtual terminal as part of their standard service, often at no extra monthly cost.
• Payment links are safer for your team because the customer enters their own card details; virtual terminals are faster but put the burden of security on you.
• Your payment processor handles the actual transaction, fraud checks, and settlement to your bank account—you just enter the details and hit process.

How the transaction flows from phone call to bank account

When a customer calls your support line and agrees to pay, you log into your virtual terminal (usually through your merchant account dashboard). You ask for the card number, expiration date, CVV, and billing zip code—the same details they would enter on a website. You type those into the form fields, enter the dollar amount, and click "Process" or "Charge".

Your payment processor (Stripe, Square, PayPal, or your bank's processor) receives that data over an encrypted connection. It checks the card with the card network (Visa, Mastercard, Amex) and the customer's bank to confirm the card is valid, the account has funds, and there are no fraud flags. This takes 10 to 30 seconds. If approved, the processor sends you a confirmation number and receipt. If declined, it tells you why (insufficient funds, card expired, fraud hold) so you can ask the customer for a different card.

The money does not land in your bank account immediately. Most processors settle transactions once per day, usually overnight. So a payment taken at 2 p.m. on Tuesday will show in your bank account on Wednesday morning. Some processors offer faster settlement (same-day or next-day) for a higher fee.

The customer receives a receipt by email (if you capture their email address in the virtual terminal form) or you can print or email one manually. Your accounting system should record the transaction—either by exporting it from your merchant dashboard or by integrating your payment processor with your billing software.

Virtual terminals versus payment links: which is right for your team

A payment link is a URL you send to a customer via email, text, or chat. The customer clicks the link, lands on a secure payment page hosted by your processor, and enters their own card details. You never see the card number. Payment links are safer for your team because you are not handling card data, and they work well when the customer is not on the phone—they can pay at their own pace and you get a notification when the payment clears.

A virtual terminal requires you to enter the card details yourself. It is faster during a live call (no waiting for an email to be read or a link to be clicked) but it puts the security burden on you. You have to be trained in PCI compliance, your computer must be secure, and you have to handle the card number carefully (never write it down, never email it, never say it out loud where others can hear).

For most support teams, the best practice is to offer both. Use a payment link as the default—send it via email or chat and let the customer pay on their own time. Use the virtual terminal only when the customer is on the phone, wants to pay immediately, and you have confirmed they are comfortable giving you their card details verbally. This keeps your team out of unnecessary compliance risk while still offering the speed customers expect during a support call.

Costs: what you pay per transaction and any monthly fees

Virtual terminals are usually included free with your merchant account. You do not pay an extra monthly fee to access the tool. Instead, you pay per transaction, the same way you do for online payments.

Typical costs are 2.5% to 3.5% of the transaction amount plus a flat fee per transaction (usually $0.20 to $0.30). So a $100 payment might cost you $2.70 to $3.80 in fees. The exact rate depends on your processor, your industry (software support is usually lower-risk than retail), and your contract terms. Some processors charge slightly higher rates for virtual terminal transactions than for online card payments, because the risk of fraud is higher when you are entering the card yourself.

If you process a high volume of payments, you may be able to negotiate a lower rate. If you process very few, your processor may require a monthly minimum or charge a higher per-transaction fee. Always ask your processor what their virtual terminal rates are before you sign up—they are not always the same as your website checkout rates.

PCI compliance: what your team needs to know about handling card data

PCI compliance is a set of security rules created by the card networks (Visa, Mastercard, Amex) to protect customer card data. If your team uses a virtual terminal, you are handling card data, which means you have to follow these rules or face fines and loss of your merchant account.

The most important rules for support teams are: never write down a card number, never email a card number, never store a card number in a spreadsheet or document, and never say a card number out loud where someone else can hear it. Use the virtual terminal form only—it is encrypted and secure. If a customer reads their card number to you over the phone, type it directly into the terminal form and do not repeat it back to confirm (this prevents others from overhearing it).

Your processor should provide PCI training for your team, usually a short online course that takes 20 to 30 minutes. Some processors require this training before you can access the virtual terminal. Your team should also use strong passwords for your merchant account, enable two-factor authentication if available, and log out of the terminal when you are done—do not leave it open on a shared computer.

If you are not comfortable with these rules or do not have the infrastructure to keep card data secure (for example, if your support team works from home on unsecured networks), use payment links instead. Your processor handles the security, and you avoid the compliance burden entirely.

Setting up a virtual terminal with your current payment processor

If you already have a merchant account (for your website, in-person payments, or invoicing), your processor almost certainly offers a virtual terminal. Log into your merchant dashboard and look for a section called "Virtual Terminal," "Keyed Entry," "Card Not Present," or "Phone Payments." Click it and you should see a form where you can enter card details and process a payment.

If you do not see it, contact your processor's support team and ask them to enable virtual terminal access for your account. They may ask you to confirm that your team has been trained in PCI compliance. Some processors require you to sign an addendum or agree to their terms before they turn it on.

If you do not have a merchant account yet, you will need to open one before you can use a virtual terminal. Most payment processors (Stripe, Square, PayPal, your bank) can set you up in a few days. You will need your business license, tax ID, and bank account information. Once your account is approved, the virtual terminal is usually available immediately in your dashboard.

Test the virtual terminal with a small test transaction before you use it with real customers. Most processors provide test card numbers that will go through the system without charging your account. This lets you confirm the form works, you know how to navigate it, and your team understands the flow.

When a virtual terminal is not the right tool

Virtual terminals work well for one-off payments during support calls, but they are not ideal for recurring charges, subscriptions, or high-volume transactions. If you charge customers the same amount every month, set up a recurring payment (subscription) instead—your processor can charge the card automatically without your team entering the details each time. If you process hundreds of payments per day, a point-of-sale system or a fully integrated billing platform will be faster and more reliable than a manual virtual terminal.

Virtual terminals are also not the right choice if your support team is not trained or comfortable handling card data. If you have high turnover, remote staff, or limited IT infrastructure, payment links are safer and easier to manage. You can send a link via email or chat, the customer pays themselves, and you avoid the compliance risk.

If a customer refuses to give you their card details over the phone (which is reasonable), do not push them. Send a payment link instead. Most customers will pay via a secure link if you make it easy—a text message with a link is often faster than a phone call.

Frequently Asked Questions

Do I have to use a virtual terminal, or can I just use payment links?

You can use payment links exclusively if you prefer. They are safer for your team and work well for most support scenarios. Use a virtual terminal only when a customer is on the phone, wants to pay immediately, and is comfortable giving you their card details verbally. Payment links should be your default.

What happens if a payment is declined?

Your virtual terminal will show you the decline reason (insufficient funds, expired card, fraud hold, etc.). Tell the customer why the card was declined and ask them to provide a different card or contact their bank. Do not keep trying the same card—multiple failed attempts can trigger a fraud block.

Can I refund a payment taken through a virtual terminal?

Yes. Log into your merchant dashboard, find the transaction, and click "Refund" or "Void." A void cancels the transaction before it settles (usually within 24 hours of the original charge). A refund processes after settlement and returns money to the customer's card in 1 to 3 business days. Your processor will show you which option is available for each transaction.

What if a customer disputes a charge I took through the virtual terminal?

The customer can contact their bank and file a chargeback, claiming they did not authorize the charge or did not receive the service. Your processor will notify you and ask for proof that the customer authorized the payment (for example, a recording of the call, an email confirmation, or a support ticket showing the customer requested the charge). Keep records of all virtual terminal transactions and customer communications to defend against chargebacks.

Is a virtual terminal safe for remote support teams?

Virtual terminals are safe if your team uses secure computers and networks. If your support staff work from home, make sure they are using a personal device (not a shared computer), a strong password, and a secure internet connection (not public WiFi). If you cannot may provide this, use payment links instead and avoid the risk.