If your business takes payment over the phone — whether you're a service company, a retailer processing remote orders, a travel agency, a medical practice, or any merchant where customers call in to pay — you're operating under a structural chargeback disadvantage that most merchants don't fully recognize until a dispute arrives and they realize how little evidence they have to fight it with.
The good news is that this disadvantage is almost entirely solvable with a single operational change: replacing the verbal card collection process with a payment link sent to the customer during or after the call. CyoGate's electronic invoicing and payment link feature turns every phone order into a customer-initiated, self-authorized transaction — with a dramatically stronger evidence package, reduced PCI scope, and in many cases a complete liability shift on fraud disputes.
The Structural Problem With Phone Order Chargebacks
A standard phone order — where the customer reads their card number to your agent and the agent keys it into a virtual terminal — creates what card networks classify as a MOTO (Mail Order/Telephone Order) transaction. MOTO transactions have several characteristics that make them structurally difficult to defend in disputes:
No customer self-authorization. The defining characteristic of a MOTO transaction is that the merchant — your agent — entered the card details, not the cardholder. There is no digital record of the customer initiating the payment. When that customer later calls their bank and says "I didn't authorize this charge," they're technically correct in a meaningful sense: they didn't authorize it in the way the card network's fraud model expects authorization to look. The agent authorized it on their behalf.
Weak evidence of cardholder participation. What documentation does a typical phone order generate? A call log entry. Perhaps a recording if you record calls. A virtual terminal transaction record showing the card was keyed manually. None of this definitively proves the cardholder participated willingly. A cardholder who claims their card was used without their knowledge — whether truthfully or dishonestly — has a relatively easy path to a successful dispute because the transaction record doesn't contradict them.
No IP address or device data. One of the most powerful pieces of dispute evidence in ecommerce is the IP address and device fingerprint associated with the transaction — proof that a specific device, at a specific location, submitted the payment. MOTO transactions generate none of this because the transaction was entered by your agent from your system, not by the customer from theirs. The IP address in the transaction record belongs to your office, not the cardholder.
No AVS or CVV friction. While agents typically collect billing zip and CVV, the absence of a self-service checkout means there's no record of the cardholder providing these details themselves. A dispute that claims "my card was stolen" has no checkout form submission to contradict it.
Elevated friendly fraud exposure. The combination of all the above creates elevated friendly fraud exposure — customers who made a legitimate purchase, experienced buyer's remorse, and discovered that a phone order is far easier to dispute successfully than an online purchase they completed themselves. The dispute doesn't require the cardholder to lie convincingly; they simply report an "unauthorized" charge and the weak evidence record makes it difficult to prove otherwise.
How Payment Link Invoicing Changes Everything
A payment link — sent via email or SMS during or after the call — transforms the transaction from merchant-initiated MOTO to customer-initiated card-not-present. The customer receives the link, opens it on their own device, reviews the invoice details, and enters their own card information to complete the payment. From an evidence and liability standpoint, this is an entirely different transaction type.
Here's what the evidence package looks like when a customer pays via payment link versus a standard phone order:
| Evidence Type | Standard Phone Order | Payment Link |
|---|---|---|
| Customer self-authorization | ✗ Agent entered | ✓ Customer entered |
| Customer IP address | ✗ Office IP only | ✓ Customer's device IP |
| Device fingerprint | ✗ Not available | ✓ Captured at checkout |
| Invoice viewed/accepted | ✗ Verbal only | ✓ Digital record |
| Email/SMS delivery record | ✗ Not applicable | ✓ Timestamped delivery |
| Link click timestamp | ✗ Not applicable | ✓ Captured and logged |
| 3DS authentication eligible | ✗ Not available | ✓ Available, liability shift |
When a customer who paid via payment link files a dispute claiming "I didn't authorize this charge," you have: the timestamp when the link was sent to their email or phone number, the timestamp when the link was clicked, the IP address of the device that opened the link, the device fingerprint, and a record of the invoice being viewed before payment was submitted. That evidence package makes the "I didn't authorize this" claim extremely difficult to sustain.
The PCI Scope Benefit
Beyond chargeback prevention, payment link invoicing delivers a significant PCI compliance benefit that many merchants overlook entirely: when customers enter their own card details through the payment link, your agents never see, hear, or handle card numbers at all.
In a standard phone order process, your agent hears the card number spoken aloud, keys it into a terminal or virtual terminal interface, and potentially writes it down during the call. Each of these touchpoints creates PCI scope — your call recording system, your agent's workstation, your network, and potentially any written notes are all in scope for PCI compliance review. Managing PCI scope across a call center environment is a significant ongoing compliance burden.
With payment link invoicing, none of this applies. The agent's involvement ends when they send the link. Card data goes directly from the customer's device to the payment gateway — your agents, your call recording system, and your internal network are entirely out of the card data flow. The PCI scope for your call handling environment effectively disappears.
For merchants currently completing SAQ C-VT (the virtual terminal SAQ) or SAQ D for their phone order processing, migrating to payment link invoicing can reduce the applicable SAQ to SAQ A — the simplest possible compliance path. Our guide on PCI compliance for small businesses explains the SAQ types and what each one requires.
Adding 3D Secure for Maximum Protection
Because payment link transactions are customer-initiated card-not-present payments made through a standard checkout flow, they're eligible for 3D Secure 2.0 authentication — something that MOTO transactions fundamentally cannot support.
When 3DS is enabled on the payment link checkout flow, the transaction goes through the issuing bank's risk assessment. For low-risk transactions — most of your regular customers paying routine invoices — the authentication is frictionless: the customer pays normally with no additional step required, and the liability shift applies automatically. For higher-risk transactions, the customer may be prompted for a brief authentication step before payment completes.
The liability shift is the critical outcome: on a transaction authenticated through 3DS, "unauthorized transaction" chargebacks shift from the merchant to the issuing bank. The bank's fraud model approved the transaction; if it turns out to be fraudulent, that's the bank's liability. For merchants in categories with elevated fraud exposure — travel, high-ticket services, medical practices, subscription businesses — this liability shift on payment link transactions can reduce fraud-driven chargebacks to near zero.
Our guide to 3D Secure 2.0 for merchants covers the full implementation and liability shift mechanics in detail.
How It Works Operationally
The operational change required to move from phone order to payment link is minimal — which is one of the most appealing aspects of the approach. The customer experience on the call changes very little; the payment collection method changes significantly.
A typical payment link workflow:
- Customer calls to place an order or make a payment. The agent takes the order details as normal.
- Instead of asking for card details, the agent says: "I'm going to send you a secure payment link right now — you'll get it by email [or text]. Just click it when you're ready and enter your card details directly. It usually takes about a minute."
- The agent generates the payment link from the gateway interface — entering the amount, a description of what's being paid for, and the customer's email or mobile number. The link is sent instantly.
- The customer receives the link on their device, clicks it, reviews the invoice, and enters their card details directly in the secure checkout form. The payment processes and both parties receive confirmation.
- The agent can see in the gateway dashboard when the link has been opened and when payment has been completed — and can follow up if the link hasn't been clicked within a reasonable window.
For customers who are already on the phone and willing to pay immediately, the entire process typically takes two to three minutes — comparable to reading a card number aloud and having an agent key it in. For customers who prefer to complete payment later, the link remains active and the agent can check its status without a follow-up call.
Which Merchants Benefit Most
Payment link invoicing delivers the most value for merchants where phone orders represent a significant share of revenue and where the chargeback or PCI challenges of MOTO processing are actively felt:
Service businesses billing by phone. HVAC companies, plumbers, contractors, auto repair shops, and similar businesses that quote and collect over the phone after completing work. The "I didn't authorize that repair cost" dispute is a persistent problem in these categories — payment link invoicing essentially eliminates it.
Medical and dental practices. Healthcare providers collecting co-pays and outstanding balances by phone benefit enormously from both the chargeback protection and the PCI compliance angle. HIPAA considerations around call recording make keeping card data out of the phone conversation particularly valuable.
Travel agencies and tour operators. As we discussed in our guide on travel and advance purchase merchant accounts, this category has elevated chargeback exposure. Payment links for phone bookings create the strongest possible evidence of customer authorization on transactions that may be disputed months later.
High-ticket retailers. Merchants processing large individual transactions by phone — furniture, jewelry, specialty equipment — have both high dollar exposure per dispute and customers who are more likely to dispute when buyer's remorse sets in. Payment link invoicing reduces both the frequency and the success rate of those disputes.
Subscription and recurring billing businesses. For businesses that set up recurring billing arrangements over the phone, the initial authorization via payment link creates a clean, defensible record of the customer agreeing to the recurring terms — far stronger than a verbal authorization captured in a call recording.
Getting Started With Payment Link Invoicing
CyoGate's electronic invoicing and payment link feature is available as an add-on to your existing CyoGate gateway account. Setup is straightforward — no integration work required, no changes to your existing checkout or ecommerce setup. The payment link interface is accessible directly from your gateway dashboard, and links can be generated and sent in under a minute.
If you're currently processing phone orders through a virtual terminal and experiencing MOTO chargebacks, or if you're looking to simplify your PCI compliance posture for your call handling environment, contact us to discuss adding electronic invoicing to your account. Or if you don't yet have a CyoGate merchant account, apply now and include electronic invoicing in your gateway setup from day one.