Merchant Account for Tech Support Business [Instant Approval]

No. 2Accept does not charge an application fee, underwriting fee, or setup fee on tech support accounts. You only pay transaction fees once your tech support MID goes live and starts processing. There is no fee to be reviewed, and there is no fee if you are declined.

Yes. 2Accept onboards both U.S.-based and non-U.S. tech support merchants. Non-U.S. tech support brands serving U.S. customers face additional scrutiny because the FTC and U.S. state AGs have specifically pursued offshore tech support operators in prior enforcement actions. Approval is conditional on a clean prior-investigation record, transparent pricing, two-party-consent customer recording deployed regardless of jurisdiction, and (for some acquirers) a U.S.-domiciled compliance officer or registered agent.

Yes. Personal credit below 600 does not automatically disqualify a tech support merchant. Acquirers weigh tech support business volume, chargeback ratio, BBB standing, no-pop-up-warnings advertising posture, and customer-recording coverage more heavily than personal FICO. A personal guarantee is typically required on sub-600 credit applications, and the acquirer may add a small rolling reserve increase.

No. 2Accept tech support agreements do not include early termination fees or multi-year lock-in. You may close the tech support account with 30 days written notice. The acquiring bank retains the rolling reserve for 180 days post-closure to cover any lingering tech support chargebacks, which on subscription-plan books can extend longer than the standard 180 days due to annual-renewal dispute exposure.

After approval, 2Accept provides credentials for Authorize.net, NMI, or a native 2Accept gateway. Tech support integrations support REST API, hosted payment page, native gateway connectors for ConnectWise Manage and Automate, ServiceNow, FreshService, Zendesk, Datto Autotask, Kaseya, NinjaOne, Calendly and Acuity for booking-platform integration, and direct connections to Splashtop, TeamViewer, AnyDesk, and ConnectWise Control for session-audio capture against the transaction ID. Our integration team provides free developer support during go-live.

A tech support application typically requires your EIN, Articles of Incorporation, voided check for settlement, 3 months of business bank statements, 3 months of processing statements (if applicable), government-issued ID for the signer, a live URL with working booking flow, your sales-page and current advertising assets (for FTC no-pop-up-warnings and truth-in-advertising audit), your customer-recording infrastructure documentation (two-party-consent disclosure language, recording-retention policy, remote-access tool integration), your signed service-engagement agreement template, your refund and cancellation policy, your subscription terms if you sell continuity support plans, your BBB profile URL, your technician-credential documentation if you operate a marketplace or dispatch model, and full disclosure of any prior FTC, state AG, or card-network investigation history. Two-party-consent customer-recording deployment is the single most important non-document requirement and is verified during underwriting.

Yes. Pop-up-warning advertising — browser pop-ups falsely claiming the user's computer is infected, fake Microsoft or Apple branding, fake virus warnings of any kind — is the defining marker of the tech-support-fraud variant the FTC has prosecuted in over 100 enforcement actions, and 2Accept does not underwrite operators using this marketing under any condition. If your current customer-acquisition uses any of these patterns, remediation (transitioning to organic-search, paid-search, referral, or direct-mail customer acquisition with transparent pricing) is required before the application can be approved.

Yes. Most tech support merchant accounts carry a 5%-15% rolling reserve held for 180 days to soften the elevated dispute risk on the vertical. Established legitimate-variant tech support brands with clean processing history can qualify at the lower 5% end; new tech support merchants, marketplace operators, and operators with prior FTC investigation history typically sit toward the 15% end. Reserve percentages can be renegotiated downward after 6 months of clean processing.

Chargeback fees on 2Accept tech support merchant accounts range from $20 to $50 per dispute depending on the account configuration, risk profile, and acquiring bank. The fee applies whether you win or lose the representment. Ethoca and Verifi alerts prevent disputes from becoming chargebacks. The elevated chargeback fee compared to lower-risk verticals reflects the per-dispute cost the acquirer absorbs on the structurally elevated tech support dispute exposure.

No. 2Accept publishes a flat monthly statement with your discount rate, per-transaction fee, monthly gateway fee, customer-recording-storage fee, and chargeback fee only. There are no PCI non-compliance surcharges, no early termination fees, no monthly minimums on standard accounts, and no junk-fee line items.

Tech support rates start at 3.95% for established legitimate-variant tech support brands with clean processing history (chargeback ratio under 0.7%), a fully deployed two-party-consent customer-recording infrastructure, a clean no-pop-up-warnings advertising posture, an A or A+ BBB rating, complete signed-service-engagement-agreement capture on every booking, and ROSCA-compliant subscription cancellation flow if continuity is offered. Rates run higher for new tech support brands without processing history, marketplace operators with sub-merchant technician populations, operators with prior FTC or state AG investigation history, and operators in temporary remediation status. Custom interchange-plus rates are available for high-volume tech support operators above $250K monthly.

Yes. After 6 months of clean tech support processing (chargeback ratio under 0.5%, consistent volume, no FTC or state AG inquiry, current BBB standing, full customer-recording coverage, and zero pop-up-warning advertising remediation events), 2Accept can submit a rate review request to the acquiring bank. Successful tech support rate reviews reduce the discount rate by 0.25%-0.75%.

Domestic U.S. tech support merchant accounts typically receive next-day funding via ACH for all batches submitted before 8:00 PM ET on the per-incident and MSP recurring books. Subscription-plan books may carry a slightly longer initial hold (T+2 to T+3) during the first 90 days of processing while the chargeback pattern is observed; the hold reduces to next-day after clean processing history is established. Offshore tech support acquiring accounts fund on a weekly or bi-weekly schedule (T+3 to T+7).

Interchange is the wholesale fee that Visa, Mastercard, and Discover charge the acquiring bank for every transaction, typically 1.5%-2.5% depending on card type. 2Accept offers both flat-rate pricing (discount rate includes interchange) and interchange-plus pricing (interchange passed through plus a fixed 0.75%-1.5% markup) for tech support merchants processing above $250K monthly. MSP recurring contract MIDs and on-demand marketplace MIDs are most commonly priced interchange-plus.

Yes. Monthly and annual subscription support plans process under MCC 5968 (direct-marketing-subscription-merchants) with ROSCA-compliant cancellation flows, pre-rebill NRR notifications, Account Updater across the renewal cycle, and tokenized vault for card-on-file. Annual renewal disputes are one of the most common chargeback patterns in the vertical, so the MID is configured with the full continuity-defense stack by default.

A tech support business is classified high risk because the vertical consistently ranks in the top five highest-chargeback categories in card-not-present payments, because the FTC has filed over 100 enforcement actions against fraudulent tech support operators in the last decade with judgments running into hundreds of millions of dollars (which has trained issuing-bank dispute reps to apply the fraud reason code aggressively to tech support transactions), because state AGs run parallel tech-support-fraud investigations under state consumer-protection statutes, because most aggregators decline the vertical outright in their acceptable-use policies, and because the legitimate-vs-scam distinction requires active underwriting screening that adds cost to every approval.

Yes. In-home tech support and installation providers — smart-home device setup, TV mounting and home-theater wiring with embedded-tech configuration, smart-thermostat and smart-lock deployment — process under MCC 7379 with hybrid card-present (mobile card reader at the customer's location) and card-not-present (online booking) acceptance. Per-incident auth-and-capture with hold-and-release authorization aligns the customer charge with service delivery, and in-person signature capture on the service receipt provides an additional layer of representment evidence beyond the standard signed service-engagement agreement.

Yes. MSP (managed service provider) recurring per-endpoint billing for SMB contracts is one of the most common tech support business models we underwrite. Billing supports per-endpoint metering ($50-$200 per endpoint per month is typical) with monthly seat-count true-up cycles, card-plus-ACH hybrid configurations for $10K+ annual commitments, and net-30 invoicing alongside card processing. MSP books typically carry a materially lower chargeback rate than consumer-facing tech support books because of the B2B contract structure.

Because the FTC has aggressively pursued the fraudulent variant of tech support for over a decade — Operation Tech Trap (2017), Operation Stop Scams (2019), and ongoing sweeps — and because card networks have built risk-team review escalation paths specifically for the vertical. The acquirer that approves a fraudulent tech support operator faces direct exposure to FTC penalty assessments, card-network fines, and reputation damage. Acquirers respond by screening every tech support application aggressively for the markers of the fraudulent variant: pop-up-warning advertising, fake-virus-warning marketing, high-pressure-scarcity sales scripts, lack of transparent pre-engagement pricing, and absence of customer-recording infrastructure. Most aggregators skip the screening work and decline the vertical entirely.

Yes, with elevated scrutiny. 2Accept holds acquiring relationships with banks in the United States, United Kingdom, European Union, and certain APAC regions that approve legitimate-variant tech support. Non-U.S. tech support brands serving U.S. customers face additional scrutiny because the FTC and U.S. state AGs have specifically pursued offshore tech support operators in prior enforcement actions. Approval is conditional on clean prior-investigation record, transparent pricing, deployed two-party-consent customer recording, and (for some acquirers) a U.S.-domiciled compliance officer or registered agent.

Yes. On-demand tech support marketplaces — two-sided platforms (HelloTech-style, Puls-style) matching credentialed technicians with consumer and SMB customers — qualify for MCC 7299 with payment-facilitator-adjacent structure. Approval requires technician sub-merchant onboarding with KYC at the platform level, credential verification (CompTIA, Apple Certified Support Professional, Microsoft 365 Certified), background checks where applicable, payout hold periods that bridge the chargeback-exposure window, reserve-fund management for chargeback liability, and platform-level enforcement of two-party-consent customer recording across all technician-fulfilled sessions.

98% of tech support merchants who complete a full application with all required documentation (customer-recording infrastructure deployed, no-pop-up-warnings advertising audit clean, BBB standing in good order, refund and cancellation policies in place, ROSCA-compliant cancellation flow if continuity is offered, prior-investigation history disclosed) get approved. The 2% rejection rate is driven by OFAC sanctions matches, undisclosed prior FTC consent-decree history that surfaces during underwriting, undisclosed pop-up-warning advertising history, active state AG investigation, BBB rating below C, or the applicant being on the card brand's internal tech-support-fraud watchlist.

Yes. New tech support businesses without prior processing can be considered at mid-tier pricing with a 5%-15% rolling reserve and personal guarantee. Projected tech support volume, customer-recording infrastructure readiness, advertising posture, business plan, BBB standing, technician-credential documentation (if applicable), and principal experience substitute for processing history. The reserve drops after 90-180 days of clean tech support processing.

A soft credit inquiry is run during tech support underwriting for personal guarantee verification. Soft pulls do not affect your FICO score and do not appear on your credit report to other lenders. Hard credit pulls can be used in some cases depending on the particular acquiring bank's requirements.

If a primary acquirer denies your tech support application, 2Accept automatically reshops it to secondary and offshore tech-support-friendly banks within our network without requiring you to resubmit. If all placements decline, you receive a written explanation and a remediation roadmap specific to tech support underwriting (typically focused on customer-recording deployment, advertising remediation, BBB resolution, or refund-policy revision).

Most tech support merchant accounts are approved in 48 hours to 7 business days after complete documentation is received. Established legitimate-variant tech support brands with deployed customer-recording infrastructure, clean no-pop-up-warnings advertising, A or A+ BBB rating, and clean processing history approve in 48-72 hours. New tech support brands, on-demand marketplaces with sub-merchant technician populations, and operators with prior FTC or state AG investigation history may require 5-10 business days due to additional KYC and operator-legitimacy verification.

First-pass tech support rejections usually result from any pop-up-warning, fake-virus-warning, or fake-Microsoft / fake-Apple branding discovered in current or archived advertising, missing or weak customer-recording infrastructure (no two-party-consent disclosure language, no recording integration with the remote-access tool, no recording retention policy), absent or non-symmetric ROSCA cancellation flow on a subscription support plan, BBB rating below C or pattern of unresolved BBB complaints, undisclosed prior FTC or state AG investigation history that surfaces during underwriting, inconsistent bank and tax records, a disclosed chargeback ratio above 1.5%, or the applicant's domain appearing on the Global Merchant Violations List under tech-support-fraud sub-categorization. 2Accept's tech support underwriter catches most of these before submission to prevent rejections.

Clean processing history (under 0.5% chargeback ratio), six or more months of bank statements showing consistent tech support revenue, deployed two-party-consent customer-recording infrastructure with 100% session coverage, clean no-pop-up-warnings advertising posture (with archived ad-copy history available for review), A or A+ BBB rating with no unresolved complaints, transparent pre-engagement pricing displayed at checkout, ROSCA-compliant subscription cancellation flow (if continuity is offered), a signed service-engagement agreement on every booking, documented technician credentials (if you operate a marketplace or dispatch model), entity formation over 12 months old, and prior FTC investigation clearance (or no investigation history at all).

Ethoca Alerts and Verifi CDRN forward dispute intents from issuing banks before they post as chargebacks. On tech support transactions you receive the alert within 24-72 hours of the customer's bank contact, issue a refund inside the alert window, and the chargeback never counts against your tech support MID's ratio. Alert-driven refunds are particularly important on tech support MIDs because of the 'I was scammed' fraud-classification escalation risk — refunding before the dispute posts prevents the card-network risk-team review trigger.

A refund is initiated by the merchant and returns funds to the tech support customer without a dispute entry. A chargeback is initiated by the customer through their issuing bank, carries a reason code (10.1-13.9 for Visa), counts against the VAMP/ECM ratio, imposes a $20-$50 chargeback fee regardless of outcome, and on tech support MIDs carries the additional escalation risk that a single 'I was scammed' (10.4) dispute can trigger card-network risk-team review. Refund-before-chargeback within the Ethoca or Verifi alert window is the core prevention strategy on tech support MIDs because the consequences of letting a dispute post are heavier than on most verticals.

Visa's VAMP and Mastercard's ECM thresholds are 1.5%. Crossing either triggers Early Warning monitoring on your tech support MID. Tech support carries an additional escalation path that does not apply to most other verticals — a single high-profile 'I was scammed' fraud-classification dispute (Visa reason code 10.4) can trigger card-network risk-team review and acquirer-mandated MID audit on its own, regardless of whether your aggregate chargeback ratio is otherwise clean. Staying over the 1.5% threshold for 4+ months leads to enrollment in VAMP, ECM, or VFMP, additional fines of $25,000-$200,000, and possible MID termination with MATCH listing. The aggressive issuing-bank application of the fraud reason code on tech support transactions is what makes the 'I was scammed' dispute pattern the single most dangerous variant on the MID.

An Excessive Chargeback Merchant is a Mastercard designation applied when a merchant exceeds 100 chargebacks in a month AND a 1.5% chargeback ratio for two consecutive months. ECM enrollment imposes escalating fines ($5,000-$25,000 monthly), mandatory chargeback reduction plans, and a path to permanent MATCH listing if the tech support ratio is not remediated within 6 months. Tech support MIDs are particularly exposed to ECM because of the elevated baseline dispute rate in the vertical and the aggressive issuing-bank application of the fraud reason code.

Verifi CDRN is owned by Visa and covers Visa issuers. Ethoca is owned by Mastercard and covers Mastercard plus Amex, Discover, and some Visa issuers. Using both networks together covers roughly 90% of U.S. card-issuing banks — particularly important on tech support MIDs where dispute volume is elevated and the 'I was scammed' fraud-classification escalation risk makes refund-before-chargeback the dominant defense strategy.

Yes. 2Accept's representment team files compelling-evidence packages on tech support disputes including the two-party-consent customer recording (the single most powerful piece of evidence in the vertical, with the customer's verbal acknowledgement of the issue at session start and the work performed at session end), the signed service-engagement agreement with results disclaimer, the session log with remote-access timestamps and work performed, IP and device-fingerprint records, and operator-legitimacy front matter (BBB rating, no-pop-up-warnings audit certificate, business-license verification, technician-credential proof). Representment win rates on 2Accept-managed tech support disputes run 55-65% when the customer recording and signed agreement are captured cleanly; without one or both, win rates collapse below 15%.

3DS 2.0 shifts liability for fraud-based chargebacks (reason codes 10.4, 83) from the merchant to the issuing bank on authenticated tech support transactions. It does not eliminate friendly fraud, service-not-as-described, or 'the issue wasn't fixed' disputes — common on tech support. Implementing 3DS typically reduces total tech support chargebacks by 30%-50% and saves $4-$8 per transaction in fraud losses. On higher-ticket tech support transactions ($200+) we recommend 3DS authentication on the initial authorization.

Authorize.net and NMI are payment gateways, not merchant accounts. A gateway transmits tech support card data between your booking flow and the acquiring bank but does not underwrite or settle tech support funds. You still need a tech support merchant account behind them, and the acquirer relationship is where the FTC tech-support-fraud screening, customer-recording verification, and no-pop-up-warnings audit happens.

Yes. Running a primary and backup tech support processor (or multi-MID load balancing across 3-5 tech support accounts split by service line — per-incident, subscription, MSP recurring, marketplace facilitation) is standard risk practice for high-volume tech support merchants. 2Accept builds multi-MID structures into Mid-Tier and Top-Tier tech support plans by default because the consequences of a single 'I was scammed' dispute triggering card-network risk-team review make MID redundancy materially more important than on most other verticals.

Yes. 2Accept offers native tech-support-friendly plugins for WooCommerce, Calendly, Acuity, ConnectWise Manage and Automate, ServiceNow, FreshService, Zendesk, Datto Autotask, Kaseya VSA, and NinjaOne. Custom tech support platforms integrate through REST API, hosted payment page iframe, or direct Authorize.net/NMI connection. Native session-audio capture integration is available for Splashtop, TeamViewer, AnyDesk, ConnectWise Control, and Bomgar / BeyondTrust. Integration support is free for the lifetime of the tech support account.

PayPal will accept some tech support transactions but imposes a standard 21-day fund hold on tech support payments (held against potential chargeback exposure), which effectively destroys cash flow on a tech support business that needs to pay technicians weekly. PayPal also routinely freezes tech support accounts on the first major dispute spike. PayPal is not a viable primary processor for tech support; some merchants use it as a secondary backup. A 2Accept tech support MID provides next-day funding without the 21-day hold.

Yes. If you currently use Authorize.net, NMI, USAePay, or any compatible gateway for your tech support booking flow, 2Accept switches only the acquiring bank behind it. Your tech support booking flow, customer vaulting, subscription tokens, and recurring billing schedules remain in place with no customer-visible change and no re-integration work. 2Accept's one-click migration tool ports active customer subscriptions, stored tokens, and active MSP contract billing schedules from Stripe or PayPal to the new MID without forcing buyers to re-enter card details mid-subscription-cycle.

No. Shopify Payments is powered by Stripe and prohibits or restricts tech support in its acceptable-use policy. 2Accept integrates directly with Shopify as a third-party gateway, replacing Shopify Payments while keeping the native Shopify checkout experience intact for your tech support booking flow.

PaymentCloud, Durango, and Soar are ISOs/MSPs similar to 2Accept, but they operate primarily as resellers with variable pricing and most do not specialize in tech support underwriting at the depth required for the vertical. 2Accept publishes flat-tier pricing upfront (2.89% / 3.95% / 5.95%), includes chargeback alerts in standard plans, provides dedicated tech support underwriters who understand FTC tech-support-fraud enforcement history, no-pop-up-warnings advertising audit, two-party-consent customer-recording deployment, MSP per-endpoint billing, and on-demand marketplace split-payout, and offers guaranteed 48-hour approvals on legitimate-variant tech support brands with deployed customer-recording infrastructure and clean advertising posture.