Offshore Call Center Merchant Account: What Underwriters Ask
Industry Payment Guides

Offshore Support Teams: What Underwriters Ask Tech Support Firms

Getting an offshore call center merchant account: what to disclose, how to keep card data from agents, and the BPO contract terms underwriters expect.

Person in a gray cardigan and wristwatch typing on a laptop at a wooden desk beside a tea mug, phone and notebook

Photo: Pixabay

On this page 6 sections
  1. Why an Offshore Call Center Merchant Account Gets Extra Scrutiny
  2. Overseas Call Center Underwriting Starts With an Honest Inventory
  3. Keep Foreign Agents From Taking Card Payments Directly
  4. Quality Monitoring and Script Controls Processors Expect
  5. BPO Vendor Contracts: You Answer for Their Conduct
  6. Arrangements That Look Like Transaction Laundering

Key takeaways

  • Disclose every agent site, vendor, phone number and website on the application, and tell your processor before you add a new one.
  • The safest setup keeps card numbers away from offshore agents entirely, through payment links, hosted checkout or masked keypad entry.
  • Break out disputes and refunds by site and by agent, because a blended chargeback rate can hide one vendor's problem.
  • Your processor holds you responsible for a BPO's conduct, so your contract and your daily monitoring both need to be in place before launch.

A U.S. tech support company can use overseas or outsourced agents and still get approved for an offshore call center merchant account. Underwriters will ask where the agents sit and who employs them. They will also want to know whether agents ever handle card numbers and how you control what those agents promise customers. Applications run into trouble when the arrangement is left vague, or when it looks like another company's sales are running through your account. A documented setup gives the risk team something concrete to approve. That means card data kept out of agents' hands and vendor obligations put in writing.

Tech support is a high-risk category before agent location even comes up. If you're new to that review, read why tech support merchant accounts get declined and how to apply first. Offshore staffing adds its own set of questions on top of the ones every applicant in this category already faces.

Why an Offshore Call Center Merchant Account Gets Extra Scrutiny

Underwriters are reacting to a fraud pattern they have seen many times. A pop-up claims the computer is infected and shows a phone number. On the call, an agent implies a link to a major software company, takes remote control of the machine and "finds" problems that justify a repair fee or a long service plan. Many of these operations ran from overseas call centers and targeted older consumers. Federal and state regulators have pursued them, and enforcement has reached payment companies that kept processing the sales. Acquirers now pay close attention to how FTC enforcement is changing what processors must know about their merchants.

When an application says agents work in another country, the underwriter is weighing four concerns. Supervision comes first: whether the U.S. business can hear and correct what agents tell customers. Reach is next, because people outside the country may sit beyond U.S. courts and regulators if something goes wrong. Card data is a separate worry, since numbers might cross borders and pass through systems the merchant doesn't control. Finally, the setup resembles the operations that once cost acquirers money and regulatory attention, so it starts out looking like a known problem.

Offshore support is not presumed fraudulent. Legitimate help desks operate in many countries, and plenty of U.S. software companies rely on them. What matters is that your application answers all four concerns before an underwriter has to raise them.

Overseas Call Center Underwriting Starts With an Honest Inventory

Risk teams compare what you tell them with what they can find. A reviewer may dial your support line or search complaint boards for your brand. If that call reaches a company you never mentioned, you now have a credibility problem, and it is much harder to fix than a disclosure you made up front.

List every site in writing, whether your own staff run it or a business process outsourcing (BPO) vendor runs it for you:

ItemWhat to provide (illustrative format)
Vendor legal nameRegistered name and country of incorporation
Site locationStreet address, city and country
Staffing modelYour employees, vendor employees or contractors
CoverageApproximate agents per shift and hours covered
FunctionsInbound support, outbound calling, billing, retention or disputes
Phone numbers and URLsEvery number and website that routes calls to the site
Payment roleWhether agents ever handle, see or key card data

Outbound calling deserves its own sentence on the application. Calling consumers who never contacted you brings federal and state telemarketing rules into play, and it draws far more scrutiny than answering inbound calls. If any site makes outbound sales calls, say so plainly and have counsel review that program before it starts.

Disclosure doesn't end at approval. Merchant agreements generally require notice of material changes to your business. Adding a second BPO counts, as does moving work to a new country or giving agents a new job such as billing. Tell your processor before the change happens rather than after a dispute spike exposes it.

Keep Foreign Agents From Taking Card Payments Directly

The cleanest answer to the data concern is a setup where offshore agents never hear or see a card number. Agents handle the support, and customers pay through a channel the agent can't read.

A payment link is the simplest version. The agent triggers an email or text message, and the customer pays on a hosted page tied to your gateway. During a live call, keypad entry with tone masking does the same job: the customer types card digits on the phone, the system captures them, and the agent hears only flat tones. Some businesses let offshore staff finish the technical work and then transfer the call to U.S. billing staff for payment. Others send customers to a specific plan page with hosted checkout on their own website.

If agents must key cards into a virtual terminal for phone orders, the controls get heavier. Give each agent a unique login limited to sales, with refunds turned off. Recording should pause during card entry, and personal phones and paper stay off the floor. Keyed entry by vendor staff also pulls their people and systems into your PCI DSS scope, so expect to show evidence of how the vendor protects card data. The card networks run registration programs for certain third parties that handle card data on a merchant's behalf, and your processor can tell you whether your vendor's role triggers one. For more on those tradeoffs, read taking cards by phone for tech support.

This table is a starting point for deciding what offshore agents should touch:

TaskOffshore agent?Control
Remote troubleshootingYesCustomer consent logged and recorded before access
Quoting a planYesApproved price list read verbatim
Collecting a card numberAvoidPayment link, keypad masking or U.S. handoff
Issuing refundsNoU.S. staff, with each refund logged
Outbound sales callsHighest riskDisclosed to processor and reviewed by counsel
Answering chargebacksAssist onlyU.S. staff own the response

Quality Monitoring and Script Controls Processors Expect

Underwriters want proof that you can hear what agents say. In practice, that means recording calls, or at least every call that ends in a sale. Some states require consent from everyone on a call before it is recorded, so open each call with a recording notice and confirm the rules with counsel.

Scripts need two parts. Required statements typically cover your business name, a clear line that you are independent of any software or hardware maker, the price before payment and how cancellation works. Banned claims should include declaring a computer infected before any diagnosis and implying that a bank or software company referred the caller. Pressuring someone to buy before hanging up belongs on that list too. Brand misuse in particular ends accounts quickly, as covered in using Microsoft or Apple names in tech support.

Most businesses skip one step: measuring results by site and by agent. A blended dispute rate can look tolerable while one vendor drives most of the trouble.

Illustrative example. Suppose your in-house team closes two of every five sales and a BPO site closes the other three. Over one month, a dozen sales turn into chargebacks: three from your own staff and nine from the vendor. So the vendor produced three-fifths of the sales but three-quarters of the disputes. Work through the rates and the vendor's sales dispute at exactly double the in-house rate. Your combined rate lands between the two and makes the vendor look better than it is. Each disputed sale also costs you the ticket amount plus whatever per-dispute fee your processor charges.

When a split like that shows up, pull the recordings for the disputed calls and find where the script broke. Then fix it with that vendor before the next billing cycle. Run the same breakdown for refund requests, which often reveal a problem before chargebacks do. For responding to the disputes themselves, see winning "I was scammed" tech support chargebacks.

BPO Vendor Contracts: You Answer for Their Conduct

To your processor, a tech support BPO merchant account arrangement has one responsible party, and it's you. Merchant agreements generally make the merchant liable for the acts of its employees and agents. Chargebacks, network fines and terminations land on your account no matter whose agent made the call.

Your vendor contract should reflect that. Start with scope. The vendor performs only the functions you disclosed to your processor, follows your approved scripts and price lists, and touches card data only through tools you approve. If the vendor is in PCI DSS scope, require evidence of its compliance. Add a ban on subcontracting or relocating work without your written consent. A separate clause should bar side business, so the vendor can't run its own campaigns under your brand or push other clients' payments through your systems.

Audit rights are what make those promises enforceable. You need access to recordings, quality scores and agent rosters on request. Record retention should run long enough to cover dispute timelines. Indemnification for losses caused by vendor misconduct, including chargebacks and fines, belongs in the agreement, along with immediate termination for cause.

Be realistic about indemnity. Collecting from a company in another country can be slow and expensive, and sometimes it doesn't happen at all. The contract sets expectations and gives you an exit. Your daily monitoring is what keeps the account open. This is general information rather than legal advice, so have a qualified attorney draft or review the agreement.

Arrangements That Look Like Transaction Laundering

Transaction laundering means running sales through a merchant account that the acquirer didn't underwrite for those sales. Card network rules prohibit it, and acquirers screen for it actively. Outsourced tech support payment processing can drift into it without anyone using the term. Watch for these patterns:

  • A BPO runs ads or generates leads for several support brands and routes some of those payments through your account.
  • A partner asks you to bill its customers' plans under your descriptor.
  • Websites, phone numbers or brand names take orders that never appeared on your application.
  • The vendor collects payments on its own account and remits a share to you, or you collect for the vendor.
  • Volume is spread across several merchant accounts to keep each one under monitoring thresholds.
  • Your billing descriptor doesn't match the business name the customer heard on the call.

If a vendor proposes any of these, decline. No compliant version exists of processing another business's sales on your account. The consequences can include termination, held funds and placement on the MATCH list, which can block future accounts. Our guide to what happens when a tech support merchant account is terminated covers that process. Advertising practices can trigger the same outcome, as explained in tech support ads that get merchant accounts terminated.

Before you apply, assemble a vendor packet. It should hold the location table above filled in for every site, your signed BPO contract, your scripts with the banned-claims list, your recording and quality policy, and a one-page diagram of how a payment moves from call to settlement. Underwriters reviewing offshore arrangements tend to ask for each of those documents eventually, and having them ready shortens the back-and-forth.

MannyPay offers high-risk merchant accounts, and applications are reviewed through its bank partners' underwriting. When your packet is complete, request a free quote and a MannyPay specialist will respond within one business day.

About the author

Marcus Bennett

Marcus Bennett is Payments Risk & Compliance Analyst for Beyond the Swipe, covering high-risk processing, chargebacks, rolling reserves, frozen merchant accounts and fraud prevention.

This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.

Related reading