If your business takes credit card orders over the phone or through the mail — and the person entering the card number is your staff member, not the cardholder themselves — you need a MOTO merchant account. MOTO (Mail Order / Telephone Order) processing is a specific account type with its own rate structure, compliance requirements, and risk profile that is fundamentally different from retail swiped transactions and different again from standard ecommerce where the cardholder enters their own card details online.
This distinction matters because many businesses set up the wrong account type — either a retail account they're using for phone orders (a compliance violation), or an ecommerce account for transactions that don't actually fit the ecommerce model. This guide covers everything you need to know about MOTO processing: what it is, who needs it, how rates work, what the compliance requirements look like, and how to set up a proper MOTO infrastructure.
What Exactly Is MOTO Processing?
MOTO refers to any credit card transaction where the cardholder is not physically present and not entering their own card information in real time. The two defining scenarios:
Telephone order (TO): A customer calls your business, reads their card number to a staff member, and the staff member keys the transaction into a virtual terminal, point-of-sale system, or payment interface. The card never changes hands — the staff member types in what the customer reads aloud.
Mail order (MO): A customer fills out a paper order form with their card details and mails or faxes it to your business. Staff process the transaction from the written information. Less common today than it was in the 1990s catalog era, but still active in some industries (B2B ordering, government procurement, some nonprofit donation programs).
What both have in common: the merchant is keying in card data that was provided by a person not physically present, without the card present for verification, and without the cardholder self-entering their data into a secure form. This is the "card not present, merchant-keyed" environment that defines MOTO — and it's distinct from ecommerce, where the cardholder types their own card number into a checkout form.
Who Needs a MOTO Merchant Account?
Any business that takes card payments over the phone or by mail needs MOTO processing coverage. The most common categories include:
Service businesses with phone-in orders: HVAC contractors, plumbers, electricians, landscapers — trades where customers call in, schedule service, and pay by card over the phone before or after the work.
B2B suppliers and distributors: Companies that sell to other businesses often take orders by phone or fax, particularly from purchasing departments that don't use online portals. B2B MOTO volume can be significant — high ticket sizes and reliable customers, but still card-not-present risk.
Professional services: Law firms, accounting firms, consultants, and other professionals who invoice clients and collect payment by phone. Many clients prefer to pay by phone rather than through an online portal.
Medical and healthcare practices: Patient billing departments frequently collect card payments over the phone — copays, balances after insurance, payment plans. HIPAA intersects with PCI compliance in this context, adding another layer of requirements.
Nonprofit organizations: Donation programs that solicit by direct mail or phone often collect card information through those same channels rather than redirecting donors to a website.
Call center operations: Any inbound or outbound call center taking card payments as part of its service function — customer service billing, renewals, collections — needs MOTO account coverage.
Insurance and financial services: Premium payments, loan payments, and other financial transactions frequently happen over the phone.
MOTO Rates: Why They're Higher Than Retail
MOTO transactions carry higher interchange rates than card-present retail transactions, and the reason is straightforward: risk. When a customer swipes or taps their card at a terminal, the physical card is present, the chip or tap authentication verifies the card, and the cardholder is standing at the point of sale. Fraud and chargeback rates are lower.
In a MOTO transaction, none of that verification exists. You have a card number, expiration date, and CVV — all of which can be stolen and used fraudulently. There's no chip authentication, no cardholder presence, and in a phone transaction, no self-authorization by the cardholder that creates a clear record. Chargebacks on MOTO transactions are easier for cardholders to file and harder for merchants to win.
At the interchange level, MOTO transactions typically fall into "card not present" categories with interchange rates roughly 0.2%-0.4% higher than equivalent card-present retail transactions on the same card type. On a processor's markup, MOTO accounts may also carry a slightly higher rate than standard ecommerce because the keyed-entry environment (staff manually typing card numbers) creates additional data entry error and fraud exposure.
The practical difference on your effective rate between a retail account and a MOTO account might be 0.3%-0.5% in total cost — meaningful at volume, but the cost of operating your business model correctly rather than using an account type that doesn't fit your actual transactions.
PCI Compliance for MOTO: The SAQ C-VT Path
MOTO merchants have a specific PCI DSS compliance pathway that reflects their processing environment. If you process MOTO transactions exclusively through a virtual terminal — a browser-based interface where staff key in card numbers — and you don't store cardholder data, you typically qualify for SAQ C-VT (Self Assessment Questionnaire C-Virtual Terminal).
SAQ C-VT is one of the simpler compliance paths — significantly less demanding than SAQ D, which applies to merchants who store card data or have more complex environments. The requirements focus on:
Physical security of the workstation: The computer used to access the virtual terminal needs to be in a controlled environment — not visible to customers, not shared with personal use, and protected from malware and unauthorized access.
No card data storage: You cannot store card numbers, CVV codes, or full magnetic stripe data. If you're writing card numbers on paper order forms and keeping them in a filing cabinet, you're out of compliance — full stop. The customer vault approach (tokenizing cards so you have a stored token rather than actual card data) is the correct way to enable future billing for returning customers without storing raw card numbers.
CVV handling: You can request the CVV over the phone to verify the card, but under PCI rules you cannot record it, write it down, or store it in any form — even temporarily. This creates a specific operational challenge for call center environments: you need to have a clear policy that staff pause call recordings when collecting CVV, and that CVV is entered directly into the virtual terminal and never written down. Our guide on virtual terminal compliance for phone orders covers this in detail.
Secure virtual terminal access: The virtual terminal must be accessed over a secure, encrypted connection (HTTPS) and must require authentication. Shared passwords are a compliance failure — each staff member who accesses the virtual terminal should have their own credentials.
The Virtual Terminal: Your Primary MOTO Tool
The operational centerpiece of MOTO processing is the virtual terminal — a browser-based payment interface where authorized staff enter card details received by phone or mail. A well-designed virtual terminal for MOTO processing should include:
AVS (Address Verification Service) prompts: Always collect and verify the billing address ZIP code and street number on MOTO transactions. AVS match is your primary fraud screening tool when no physical card is present, and it's one of the few pieces of evidence you can cite in a representment if a MOTO transaction gets disputed as unauthorized.
CVV verification: Collect the three or four-digit CVV on every MOTO transaction. A CVV mismatch should result in decline — processing a transaction where the CVV doesn't match eliminates your ability to use CVV as a fraud defense later.
Order detail fields: The virtual terminal should allow you to capture order details — invoice number, product description, customer reference — that link the payment to the underlying transaction record. This documentation is critical for dispute management.
Customer vault integration: For returning customers or recurring billing, the customer vault lets you store a token (not the actual card number) and charge the card on future transactions without re-collecting card information by phone. This improves the customer experience, eliminates re-keying errors, and keeps your PCI scope minimal since you're working with tokens rather than raw card data.
Payment Link Invoicing: A Better Alternative for Many MOTO Scenarios
While traditional MOTO processing (staff keying in card details collected by phone) is the right model for some scenarios, payment link invoicing has emerged as a superior approach for many businesses that formerly relied on phone order processing.
Instead of having the customer read their card number to a staff member, you send the customer a payment link by email or SMS. The customer clicks the link, enters their own card details on a secure hosted payment page, and completes the transaction themselves. The result is a card-not-present transaction — but one where the cardholder self-authorized it, which creates a significantly stronger position in any dispute.
CyoGate's electronic invoicing system supports this model — generate a payment link in the control panel, send it to the customer by email, and receive funds when the customer completes the payment. The chargeback protection benefits are significant: a customer who clicked a link, entered their own card details, and authorized the payment has very little recourse when claiming the transaction was unauthorized.
Our post on how payment link invoicing reduces chargebacks on phone orders explains the liability shift mechanics in detail. For any MOTO scenario where there's any lag time between the phone conversation and the payment — service businesses invoicing after completion, professionals billing after a consultation — payment links are strongly preferable to traditional MOTO keying.
MOTO vs. Ecommerce: Why the Account Type Matters
A common mistake is merchants processing MOTO transactions through an ecommerce merchant account, or vice versa. The card networks track your transaction entry mode — keyed, swiped, chip, online — and the environment in which each transaction is processed needs to match the merchant account type.
Using a retail account to process keyed phone orders violates the terms of that account. If it comes to light during a chargeback review or audit, you face the possibility of rate adjustments, fines, or account termination. The same applies to processing online ecommerce transactions through a MOTO account — the accounts have different compliance requirements and risk pricing for a reason.
Many businesses legitimately need both: an ecommerce merchant account for online orders placed by customers on your website, and a MOTO account for orders taken by phone. CyoGate offers both, and the account type comparison guide covers how to structure multi-channel processing correctly.
Applying for a MOTO Merchant Account
MOTO merchant account applications follow the same general process as other account types, but with some specific documentation emphases:
Your application should clearly describe the MOTO nature of your business — how orders are taken, what percentage of volume is phone versus mail versus online, and your typical transaction profile (average ticket, monthly volume, industry). Underwriters need to understand your keyed-transaction environment to set the account up correctly and price the risk appropriately.
If you have existing processing statements from a prior merchant account, include them — your historical chargeback rate on keyed transactions is the most relevant risk factor for the underwriter. Clean history at similar volume is your strongest application asset.
If you're a new business without processing history, be prepared to provide additional documentation of business legitimacy — website, business license, bank statements, and references from customers or suppliers. New MOTO accounts without history may carry slightly higher initial rates that can be renegotiated after 6-12 months of clean processing.
CyoGate's MOTO merchant accounts are designed for businesses that take phone and mail orders, with virtual terminal access included, customer vault for returning customers, and the fraud screening tools you need to manage card-not-present risk effectively. Apply now and note that you're processing MOTO transactions — this ensures the right account configuration from the start.