VoIP Merchant Account

Merchant Account for VoIP Business [Instant Approval]

Opening a merchant account for a VoIP business through 2Accept connects hosted PBX providers, SIP trunking carriers, cloud contact center platforms, CPaaS programmable voice operators, residential and business VoIP retailers, international long-distance brands, and white-label VoIP resellers to acquiring banks that explicitly underwrite MCC 4814, MCC 4812, MCC 4813, and MCC 7372 — without the freezes, holds, and sudden terminations that aggregators like Stripe, Square, and PayPal issue the moment they see a telecom MCC, an international long-distance top-up funnel, or a continuity-billing chargeback spike on your account.

The process of opening a VoIP merchant account with 2Accept takes four steps. First, complete the online application with your EIN, Articles of Incorporation, last three months of bank and processing statements, your FCC Section 214 grant or pending application, USF contributor filings (FCC Forms 499-A and 499-Q), CALEA Section 105 compliance certificate, E911 / Kari’s Law / RAY BAUM’S Act deployment documentation, state PUC registrations for the jurisdictions you serve, and your HIPAA BAA template if you serve healthcare clients. Second, a dedicated VoIP underwriter reviews your billing model, international routing exposure, port-out and cancellation flow, telecom-fraud controls (velocity caps, BIN-block lists, IP-geofencing on prepaid top-up), and chargeback history within one business hour. Third, you receive your MID and integrate via Recurly, Chargebee, Maxio, Zuora, Authorize.net, NMI, USAePay, or direct REST API after signing the merchant processing agreement. Fourth, you go live in 48 hours with Account Updater, intelligent dunning, telecom velocity caps, chargeback alerts, dynamic descriptors, and multi-MID load balancing built into the account.

Rates for a VoIP merchant account on 2Accept start at 2.89% for clean business-VoIP seat-based SaaS with annual-prepay revenue mix and chargeback ratio under 0.9% and run higher for residential VoIP with metered international long-distance exposure, prepaid top-up flows with elevated telecom-fraud-card-use, and CPaaS platforms with novel-API abuse patterns. Pricing depends on monthly volume, average ticket size, chargeback ratio, billing model (seat-based vs. metered vs. prepaid top-up), whether you operate domestic-only or need offshore acquiring for international subscribers, your FCC Section 214 and USF compliance posture, and whether your international long-distance traffic terminates to high-risk destinations that drive elevated fraud-card-use against the MID.

48h
Average approval
98%
Approval rate
40+
Acquiring banks
$2B+
Processed yearly

Apply for a merchant account

Free underwriting review. No application fee.

Phone number
SSL encrypted. No credit pull. Soft underwriting review only.
Industries we underwrite

Everything 2Accept handles for VoIP merchants

VoIP merchants evaluate a payment processor on recurring-billing depth, telecom-fraud defense, port-out-dispute representment, FCC Section 214 and USF compliance posture, E911 / Kari's Law and CALEA documentation, and chargeback defense calibrated for monthly-rebill friendly fraud and international long-distance fraud-card use. 2Accept's VoIP desk covers every dimension below and approves the business types, billing models, compliance configurations, and platform integrations listed here without aggregator-style continuity-billing freezes or telecom-MCC terminations.

VoIP Services We Approve

VoIP products and services covered by 2Accept

2Accept underwrites the full landscape of voice-over-IP and cloud telephony businesses — hosted PBX providers (RingCentral, 8x8, Vonage Business-style multi-line cloud phone systems), SIP trunking carriers wholesaling minutes to enterprise PBXs, cloud contact center platforms with omnichannel routing and recording, CPaaS programmable voice operators (Twilio-style API platforms exposing SIP, PSTN, and WebRTC), residential VoIP retail (Ooma-style consumer home phone replacement), business VoIP plans with unlimited domestic and metered international, international long-distance VoIP retail with prepaid top-up and calling-card style billing, white-label VoIP reseller programs for MSPs and IT shops, HIPAA-compliant VoIP for healthcare providers with BAA coverage, and call-center-as-a-service offerings bundled with hardware (Polycom, Yealink) plus monthly service.

Service positioning, billing cadence, international routing exposure, and 911 service configuration are reviewed during onboarding because they determine whether the acquirer approves the MID under MCC 4814 (telecommunication services), MCC 4812 (telecommunication equipment, including hardware bundles), MCC 4813 (key system / multi-station phone services), or MCC 7372 (computer software / SaaS) for pure CPaaS API platforms billed like software. Subscriber notification language, FCC Section 214 status, USF contribution filings (FCC Form 499-A/Q), and CALEA Section 105 compliance certificate are audited at the operator level before the MID is placed.

Apply for a VoIP Services We Approve MID

Approved VoIP Service Categories

  • Hosted PBX / Business VoIP PlansMCC 4814
  • SIP Trunking / Wholesale MinutesMCC 4814
  • CPaaS Programmable Voice (API)MCC 7372 / 4814
  • Cloud Contact Center as a ServiceMCC 4814 / 7372
  • Residential VoIP / Consumer ATAMCC 4814
  • VoIP + Hardware Bundles (ATA / IP Phones)MCC 4812 / 4813
VoIP Business Models

VoIP business models we underwrite

VoIP merchants come in many billing-model configurations — pure monthly seat-based SaaS (per-extension or per-user per month with unlimited US/Canada included), metered usage billing (per-minute international long-distance, per-SMS, per-API-call on CPaaS), hybrid seat-plus-metered (monthly base plus overage), prepaid top-up (residential and international long-distance calling-card style where the customer loads a balance and the system drains it per minute), annual-prepay business plans with auto-renew, hardware-and-service bundles (an IP phone or ATA sold up-front with monthly service attached), and white-label reseller billing where a downstream MSP charges the end customer and remits to the platform. 2Accept underwrites all of these business configurations, matching each model to the acquirer that approves the billing mechanic for the telecom MCC.

Whether your VoIP service bills monthly, annually, on a metered per-minute basis, or as prepaid top-ups, the MID is structured to support the rebill schedule with tokenized vault storage, Account Updater for expired-card replacement, intelligent dunning retries on declined seat-renewals, and proration on mid-cycle plan changes (add or remove extensions, change plan tier). International long-distance retail gets extra scrutiny because telecom-fraud-card use against international VoIP termination is one of the highest-fraud product categories on the card networks — the underwriter audits your velocity limits, BIN-block lists, IP-geofencing on signup, and balance-cap-per-card rules before approving the MID.

Apply for a VoIP Business Models MID

Approved VoIP Business Configurations

  • Monthly Seat-Based SaaS (Per-User)Approved
  • Metered Per-Minute / Per-API BillingApproved
  • Prepaid Top-Up (Calling Card / Balance)Approved with velocity caps
  • Annual-Prepay with Auto-RenewApproved (with notice)
  • Hardware + Service BundlesApproved (MCC 4812 + 4814)
  • White-Label Reseller / MSP BillingSupported
FCC, USF, CALEA & E911

Telecom compliance handling for VoIP merchants

VoIP merchants sit at the intersection of FCC regulation, state PUC oversight, federal lawful-intercept law, and 911 service obligations. Interconnected VoIP providers must hold FCC Section 214 authority for international service, file FCC Forms 499-A and 499-Q to contribute to the Universal Service Fund (the USF contribution factor runs around 33% of interstate and international end-user revenues and resets quarterly), maintain CALEA Section 105 compliance for lawful-intercept readiness with a designated TTP (Trusted Third Party) or in-house solution, and provide E911 service that meets the FCC's Kari's Law (direct 911 dialing without prefix from multi-line systems) and RAY BAUM'S Act (dispatchable location information delivered with each 911 call) requirements. State Public Utility Commission (PUC) registration is required in many states for intrastate VoIP service, and HIPAA Business Associate Agreements are required if you serve healthcare clients whose protected health information traverses your voice or messaging plane.

2Accept's VoIP underwriting desk audits your telecom compliance posture at onboarding — FCC Section 214 grant or pending application, USF contributor filings, CALEA compliance certificate, E911 / Kari's Law / RAY BAUM'S Act dispatch-location implementation, state PUC registrations for the jurisdictions you serve, and HIPAA BAA template if applicable. Missing or weak telecom compliance is the #1 cause of first-pass rejection on VoIP applications because the acquiring bank's compliance team will not place a telecom MID without evidence the operator is in good standing with the FCC and meets the 911 service obligations that carry the highest enforcement exposure. We catch the gaps before submission and coach merchants through remediation so the application clears underwriting on the first review cycle.

Apply for a FCC, USF, CALEA & E911 MID

Compliance Frameworks Covered

  • FCC Section 214 (International Service)Required, verified
  • FCC Forms 499-A / 499-Q (USF)Required, audited
  • CALEA Section 105 ComplianceRequired, certificate verified
  • E911 / Kari's Law / RAY BAUM'S ActRequired at deployment
  • State PUC Registration (per state)Mapped per jurisdiction
  • HIPAA BAA (Healthcare VoIP Clients)Supported with BAA template
Recurring Billing & Telecom Vault

Payment features for VoIP merchants

VoIP billing depends on four technical pillars: a tokenized card vault that stores credentials safely across monthly seat-renewals and prepaid top-ups, Account Updater that swaps in new card numbers when issuers reissue or replace cards (critical because business-VoIP churn from involuntary card decline runs 7-12% without Account Updater), intelligent dunning that retries soft declines on a smart schedule to recover failed seat-renewals before they disconnect the customer's phone service, and metered-billing support that lets a per-minute or per-API-call usage charge settle through the same MID as the monthly seat fee. 2Accept VoIP MIDs ship all four by default. The vault is PCI Level 1, Account Updater is enrolled on Visa, Mastercard, and Amex, the dunning engine retries declines on a 1-3-5-7 day curve, and metered-billing transactions route under merchant-initiated-transaction (MIT) flags so they qualify for the recurring interchange tier rather than the higher card-not-present rate.

For VoIP merchants with international subscribers, multi-currency settlement is available on offshore MIDs (USD, EUR, GBP, CAD, AUD, JPY) so EU and APAC customers settle in their local currency without FX surprises on the cardholder statement that drive 'I don't recognize this charge' disputes. Prepaid top-up balance-load transactions and calling-card style funding flows are supported with velocity caps, BIN-block lists, and IP-geofencing applied at the gateway layer to defeat telecom-fraud-card use against international long-distance termination.

Apply for a Recurring Billing & Telecom Vault MID

Supported Payment Capabilities

  • Tokenized Card Vault (PCI Level 1)Included
  • Account Updater (Visa/MC/Amex)Included
  • Intelligent Dunning Retries1-3-5-7 day curve
  • Metered Per-Minute / Per-API BillingSupported (MIT flagged)
  • Prepaid Top-Up with Velocity CapsSupported
  • Multi-Currency SettlementUSD, EUR, GBP, CAD, AUD, JPY
VoIP Platform Integrations

Billing platform & gateway integrations for VoIP stacks

Most VoIP operators run on a dedicated billing platform or homegrown engine — Recurly, Chargebee, Maxio (formerly SaaSOptics + Chargify), Zuora, Stripe Billing migrators looking to escape the telecom-MCC freeze, or a custom in-house billing engine built around a softswitch like FreeSWITCH, Asterisk, Kamailio, or a commercial Class 4/5 softswitch like Sansay or Metaswitch with an integrated billing module. 2Accept ships native gateway connectors for all major subscription billing platforms, plus direct integrations for VoIP-specific billing systems like Inteliquent, BroadWorks BSS hooks, and Genband/Ribbon billing exports. CPaaS operators (Twilio-style) plug in through REST API with full webhook coverage for usage events.

For custom-built VoIP billing stacks, integration is through REST API with full webhook support for billing lifecycle events (seat-renewed, top-up loaded, payment failed, account suspended for non-payment, reactivated). Authorize.net, NMI, and USAePay gateways are supported as drop-in alternatives if your stack is already wired to one of them, so switching the acquiring bank behind a familiar gateway is a one-day swap rather than a re-integration. Hardware-and-service bundle merchants get a split-MID configuration where the up-front IP-phone or ATA sale settles under MCC 4812 and the recurring monthly service settles under MCC 4814 from the same checkout.

Apply for a VoIP Platform Integrations MID

Native Integration Support

  • RecurlyNative gateway
  • ChargebeeNative gateway
  • Maxio (Chargify / SaaSOptics)Native gateway
  • ZuoraNative gateway
  • Authorize.net / NMI / USAePayDirect gateway
  • Custom REST API + WebhooksFull developer docs
VoIP Chargeback & Telecom Fraud Defense

Risk defense for VoIP chargeback and fraud exposure

VoIP chargeback ratios cluster around four failure modes: subscription cancellation friendly fraud ('I didn't authorize this monthly charge' disputes that run around the telecom baseline of ~12.6 disputes per 1,000 transactions on continuity-billing telecom), telecom-fraud-card-use on international long-distance termination (stolen-card balance top-ups feeding fraudulent international call traffic), service-not-delivered disputes filed during VoIP outages or 911 service failures, and port-out cancellation disputes where the customer ports their number to a competitor and disputes the final pro-rated invoice. 2Accept's stack catches all four before they post — Ethoca and Verifi alerts forward dispute intents 24-72 hours pre-post, dynamic billing descriptors with embedded support phone and brand name reduce 'I don't recognize this charge' disputes by 40%+, pre-rebill email notifications reduce continuity friendly-fraud by 20-30%, and velocity caps with BIN-block lists and IP-geofencing on prepaid top-up defeat the bulk of telecom-fraud-card-use before the funds settle.

For high-volume VoIP merchants, multi-MID cascading distributes volume across 2-5 accounts so no single MID exceeds Visa's VAMP threshold or Mastercard's ECM threshold (1.5%). 3DS 2.0 on the initial card-on-file authorization shifts fraud liability to the issuer for subsequent merchant-initiated rebills. Representment win rates on VoIP friendly-fraud and port-out disputes run ~55%+ when the compelling-evidence package includes signed sign-up consent, port-out request log, CDR (call detail record) usage proof, login activity, and the pre-rebill notification email send record.

Apply for a VoIP Chargeback & Telecom Fraud Defense MID

Risk & Chargeback Tools Included

  • Ethoca Chargeback AlertsIncluded (Mid/Top tier)
  • Verifi CDRN AlertsIncluded (Mid/Top tier)
  • Telecom Velocity Caps & BIN-BlockIncluded (top-up flows)
  • Dynamic Billing DescriptorsIncluded
  • Multi-MID CascadingSupported (2-5 MIDs)
  • Representment Service (Port-Out / 13.2)Available (~55%+ win rate)
Pricing Tiers

High risk processing rates, published up front

Every high risk merchant account is priced by risk tier. Your vertical, volume, and chargeback ratio determine which tier underwrites you. Rates are average and may vary depending on individual circumstances and risk profile. Interchange may be passed to merchants for more challenging approvals

Low-Tier High Risk
2.89%
+ $0.20

Subscription · SaaS · Coaching · Digital

  • Domestic U.S. MID
  • Next-day funding
  • 0–10% rolling reserve
  • Free gateway integration
  • Account updater included
Apply
Most Approved
Mid-Tier High Risk
3.49%
+$0.25

CBD · Peptides · Telehealth · Vape · Dating · Travel

  • Domestic or offshore MID
  • Chargeback alerts (Ethoca + Verifi)
  • 0-10% rolling reserve
  • Dedicated underwriter
  • MATCH-list considered
  • Multi-MID load balancing
Apply
Top-Tier High Risk
4.95%
+$0.30

Adult · Firearms · Crypto · Gaming

  • Offshore acquiring
  • AEP / MSB registration support
  • 0-10% rolling reserve
  • 3DS 2.0 authentication
  • Descriptor optimization
  • Cascading across 3+ MIDs
Apply
How It Works

From application to live processing in 4 steps

01

Apply Online

Complete the 4-minute application. No credit pull, no application fee, no long-term contract.

02

Meet Your Underwriter

A 2Accept underwriter reviews your business model, volume, and documents within 1 business hour.

03

Go Live in 48 Hours

Sign your MPA, receive your MID, and integrate via gateway API, hosted checkout, or Shopify.

04

Scale Safely

Grow with chargeback alerts, fraud scoring, and multi-MID load balancing as your volume scales.

2Accept vs Aggregators

Why a dedicated MID beats Stripe, Square, and PayPal

Aggregators pool thousands of merchants under one master account. When any single MCC trips a threshold, entire verticals get frozen. A dedicated MID from 2Accept belongs to your business alone.

Feature 2ACCEPTStripeSquarePayPal
CBD / Hemp approved
Vape / E-cig approved
Firearms / Ammo approved
Dedicated MID (not aggregator)
MATCH-list merchants considered
Human underwriter (not chatbot)
Multi-MID load balancing
Risk Management

Keep your MID alive with built-in chargeback defense

Every 2Accept high risk merchant account includes the monitoring and mitigation stack required to stay under Visa's 1.0% chargeback threshold.

Chargeback Alerts

Ethoca and Verifi CDRN integrations catch disputes before they post, letting you refund pre-chargeback and protect your ratio.

Fraud Scoring

Kount, Sift, and NoFraud rules block velocity attacks, BIN testing, and stolen-card fraud in real time at authorization.

3DS 2.0 Authentication

3D Secure shifts liability to the issuer on authenticated transactions, eliminating fraud-based chargebacks on compliant checkouts.

Representment

Our dispute team files compelling evidence packages against friendly fraud and product-not-received disputes, recovering revenue within 45 days.

Multi-MID Load Balancing

Split volume across 2–5 MIDs via our cascading gateway to stay under per-MID caps and maintain chargeback ratios on every account.

Descriptor Optimization

Dynamic billing descriptors matched to your brand lower “I don't recognize this charge” disputes by 40%+.

Real businesses, real approvals

What merchants say

“After Stripe terminated us for selling CBD gummies, 2Accept had us live in 48 hours on a domestic MID. Zero freezes in 18 months.”

SL

Sarah L. Founder, 

CBD E-commerce Brand

“I tried four processors for my FFL store. 2Accept was the only one that understood MCC 5999 and got my ammo transactions approved.”

MR

Michael R. , 

Owner, Firearms Retailer

“Our subscription box was flagged by Square for 'high chargeback volume.' 2Accept's Ethoca alerts dropped our ratio to 0.3% in one month.”

MR

Michael R. , 

Firearms Retailer

What It Is

What is a VoIP merchant account?

A VoIP merchant account is a specialized payment processing account that acquiring banks issue to hosted PBX providers, SIP trunking carriers, cloud contact center platforms, CPaaS programmable voice operators, residential and business VoIP retailers, international long-distance VoIP brands, and white-label VoIP resellers, designed to handle the elevated dispute exposure on continuity-billing telecom (~12.6 disputes per 1,000 transactions baseline), the telecom-fraud-card-use exposure on international long-distance termination, the FCC Section 214 / USF / CALEA / E911 compliance requirements, and the port-out-cancellation dispute defense that aggregators like Stripe, Square, and PayPal refuse to underwrite at scale.

The account permits card-on-file rebilling across monthly seat-renewals, metered per-minute and per-API-call usage charges, prepaid top-up balance loads, and annual-prepay business plans — with tokenized vault storage, Account Updater enrollment, intelligent dunning retries, dynamic billing descriptors, pre-rebill subscriber notifications, telecom velocity caps, and BIN-block lists on international top-up — and it operates under tailored underwriting terms that include 0%-10% rolling reserves, FCC compliance audits, port-out-dispute representment support, and discount rates between 2.89% and 4.50%.

A VoIP business gets a high-risk classification because telecom continuity billing carries structurally higher chargeback exposure than one-time purchase commerce (~12.6 disputes per 1,000 transactions on the telecom baseline), because international long-distance termination is one of the highest-fraud product categories on the card networks (telecom-fraud-card-use against international VoIP termination is a perennial card-brand watch-list item), because the FCC's Section 214, USF (~33% contribution factor on interstate revenue), CALEA Section 105, and E911 / Kari's Law / RAY BAUM'S Act create federal regulatory liability that aggregators are not equipped to underwrite, and because card networks treat MCC 4814 (telecommunication services), MCC 4812 (telecommunication equipment), MCC 4813 (key system / multi-station phone services), and MCC 7372 (computer software / SaaS, used for pure CPaaS API platforms) with heightened scrutiny on dispute ratios and friendly-fraud patterns. Acquiring banks also weigh whether your service has E911 / Kari's Law direct-dial-911 capability deployed, whether your USF Form 499-A and 499-Q filings are current, whether your CALEA Section 105 compliance certificate covers your softswitch and recording plane, and whether your port-out flow is clean enough to defend a representment.

Opening a VoIP merchant account differs from opening a standard low-risk account in three ways. First, underwriting takes 24 hours to 5 business days rather than instant approval, because the acquirer reviews your FCC Section 214 grant, USF contributor filings, CALEA compliance certificate, E911 deployment documentation, state PUC registrations, port-out and cancellation flow, and processing history. Second, pricing typically ranges from 2.89% (clean business-VoIP seat-based SaaS with annual-prepay mix) to 4.50% (high-volume international long-distance prepaid top-up with elevated telecom-fraud-card exposure) rather than the flat 2.6%-2.9% aggregators offer, because the acquirer absorbs additional dispute exposure on telecom continuity and international termination. Third, the account issues a dedicated MID that belongs exclusively to your VoIP business — Account Updater is enrolled in your name, the descriptor is yours with embedded support phone, telecom velocity caps and BIN-block lists are tuned to your traffic, and the MID cannot be terminated for serving the VoIP vertical the MID was approved to serve.

2Accept underwrites VoIP merchant accounts for hosted PBX providers (RingCentral, 8x8, Vonage Business-style multi-line cloud phone systems competing in the $30B+ business-VoIP market), SIP trunking carriers wholesaling minutes to enterprise PBXs, cloud contact center platforms with omnichannel routing and call recording, CPaaS programmable voice operators (Twilio-style API platforms competing on developer-priced minutes), residential VoIP retailers (Ooma-style consumer home phone replacement), international long-distance VoIP brands with prepaid top-up and calling-card style billing, white-label VoIP resellers serving the MSP and IT-channel market, HIPAA-compliant VoIP for healthcare providers, and call-center-as-a-service operators across the United States. Applications are reviewed by a dedicated VoIP underwriter within one business hour, approved in 24 hours to 5 business days depending on FCC / USF compliance complexity and international routing exposure, and integrated through Recurly, Chargebee, Maxio (formerly Chargify), Zuora, Authorize.net, NMI, USAePay, or direct REST API with full webhook coverage for billing lifecycle events after signing the merchant processing agreement.

Common types of VoIP merchants we underwrite

  Acquiring banks segment VoIP merchants by what they bill for, how the service is delivered, and what telecom-compliance framework applies. The VoIP verticals 2Accept underwrites most often are:
  • Hosted PBX / business VoIP providers —  — MCC 4814, monthly seat-based SaaS competing in the RingCentral / 8x8 / Vonage Business / Zoom Phone market with per-extension billing, unlimited US/Canada, and metered international
  • White-label VoIP resellers —  — MCC 4814, MSP and IT-channel resellers reselling hosted PBX or SIP trunking under their own brand with platform-billing or end-customer-billing models
  • Hardware-and-service VoIP bundles —  — MCC 4812 for the IP phone or ATA sale (Polycom, Yealink, Grandstream) plus MCC 4814 for the recurring service, settled through a split-MID checkout
  • International long-distance VoIP retail —  — MCC 4814, prepaid top-up balance and calling-card style billing for diaspora and expat customer bases calling Africa, Asia, Latin America with elevated telecom-fraud exposure
  • Cloud contact center as a service —  — MCC 4814 / 7372, seat-based contact-center subscription with omnichannel routing, call recording, IVR, and WFM bundled in a per-agent-per-month plan
  • CPaaS programmable voice operators —  — MCC 7372 / 4814, Twilio-style API platforms exposing SIP, PSTN, WebRTC, and SMS as developer-priced primitives with usage-metered billing
  • Residential VoIP retailers —  — MCC 4814, consumer home phone replacement with ATA hardware and monthly service, Ooma / Vonage Home / MagicJack-style positioning
  • HIPAA-compliant healthcare VoIP —  — MCC 4814 with BAA coverage, business-VoIP for medical practices, telehealth platforms, and behavioral-health providers where voice data is PHI
  • SIP trunking carriers —  — MCC 4814, wholesale per-minute and per-channel billing to enterprise PBXs, IP-PBX deployments, and downstream resellers with Class 4 softswitch routing

Advantages of a VoIP-specific merchant account

  A dedicated VoIP merchant account gives you advantages that no payment aggregator can match, because the account is underwritten by an acquiring bank that explicitly approves telecom continuity billing, international long-distance prepaid top-up, and hosted-PBX seat-based SaaS:
  • Port-out-dispute representment support —  — compelling-evidence packages including signed sign-up consent, port-out request log, CDR usage proof, and pro-rated billing terms to defend port-out cancellation disputes
  • Dedicated MID for VoIP rebills —  — belongs to your business alone, not shared in an aggregator pool that gets frozen the moment any one telecom merchant trips a chargeback threshold or telecom-fraud-card-use spike
  • Intelligent dunning retries —  — 1-3-5-7 day retry curve on soft declines recovers 30-40% of failed seat-renewals before they disconnect the customer's business phone service
  • Offshore acquiring for international subscribers —  — multi-currency settlement in USD, EUR, GBP, CAD, AUD, JPY so non-U.S. VoIP customers settle in their local currency without FX surprises
  • Account Updater in your name —  — Visa, Mastercard, and Amex automatically refresh stored card numbers on seat-renewals, cutting involuntary VoIP-service-disconnect churn by 7-12%
  • Higher monthly volume caps —  — $500K+ on domestic VoIP accounts vs. $25K-$50K aggregator ceilings before forced review of your telecom continuity book
  • No sudden terminations on telecom MCC —  — the MID is approved for MCC 4814 / 4812 / 4813 / 7372 explicitly, so Stripe-style aggregator de-platforming on the telecom acceptable-use clause doesn't apply
  • Chargeback alerts included —  — Ethoca + Verifi CDRN catch disputes 24-72 hours before they post, critical on telecom MIDs where pre-rebill refund-before-chargeback is the dominant prevention strategy
  • Telecom velocity caps and BIN-block lists —  — tuned to your traffic on prepaid top-up and international long-distance to defeat the bulk of telecom-fraud-card-use before settlement
  • Human VoIP underwriters —  — understand FCC Section 214, USF Form 499 filings, CALEA Section 105, E911 / Kari's Law, RAY BAUM'S Act, state PUC registration, and HIPAA BAA workflows; not chatbots or generic ticket queues
  • Dynamic billing descriptors —  — customer-facing brand name plus support phone embedded in the descriptor, reducing 'I don't recognize this charge' disputes by 40%+ on monthly seat-renewals

How to qualify for a VoIP merchant account

  Qualifying for a VoIP merchant account requires meeting documentation, entity, telecom-regulatory, and compliance requirements that the acquiring bank reviews during underwriting. Standard qualification criteria include:
  • Registered legal entity —  — LLC, Corporation, or DBA with valid EIN
  • Chargeback ratio under 1.5% —  on prior VoIP processing history (under 0.9% for clean approvals at the lower-tier rate)
  • E911 / Kari's Law / RAY BAUM'S Act —  — direct 911 dialing without prefix on multi-line systems and dispatchable location information delivered with each 911 call, with deployment documentation
  • USF contributor filings —  — FCC Form 499-A annual and Form 499-Q quarterly contributor filings current with USAC; the USF contribution factor (~33%) is recovered as a line item on customer invoices
  • FCC Section 214 authority —  — granted or pending application for international VoIP service, with the FCC's grant letter or filing receipt provided to the underwriter
  • Three months of processing statements —  if you were previously processing VoIP transactions on another MID or aggregator
  • Live VoIP website with consent flow —  — working checkout, Terms, Privacy, Refund, Cancellation, Acceptable Use, and Contact pages, plus material-terms disclosure of monthly seat price, per-minute international rates, and pro-rated cancellation policy displayed above the buy button
  • HIPAA BAA template —  — if you serve healthcare clients whose voice or messaging traffic includes PHI, your standard Business Associate Agreement template
  • Personal guarantee —  from the principal for new VoIP merchants or sub-650 credit applicants
  • Business bank account —  in the legal entity's name for VoIP service settlement
  • CALEA Section 105 compliance —  — compliance certificate or TTP (Trusted Third Party) agreement covering your softswitch, SBC, and recording plane for lawful-intercept readiness
  • State PUC registrations —  — Public Utility Commission registration in the states where you provide intrastate VoIP service, with registration numbers documented per jurisdiction
  • Three months of bank statements —  showing consistent VoIP service revenue
  • Government-issued ID —  for the principal signer
  • Telecom-fraud controls walkthrough —  — velocity caps, BIN-block lists, IP-geofencing on signup, and balance-cap-per-card rules for prepaid top-up and international long-distance flows

Strategies for managing a VoIP merchant account

  Keeping a VoIP merchant account active long-term requires active risk management because telecom continuity billing generates structurally higher dispute exposure than one-time commerce, because Visa's VAMP and Mastercard's ECM thresholds (1.5%) trigger fines and termination above the limit, and because the FCC's enforcement posture on USF contribution, E911, and CALEA creates ongoing regulatory liability that can flow back to the MID. The strategies that protect a VoIP MID are:
  • Tune dunning retries on a smart curve —  — 1-3-5-7 day retries on soft declines recover 30-40% of failed seat-renewals before service disconnect
  • Refund before chargeback —  — resolve disputes within 24 hours of an Ethoca or Verifi alert so they never post against your ratio
  • Run dynamic billing descriptors —  — customer-facing brand name plus support phone in the descriptor reduces 'I don't recognize this charge' disputes by 40%+ on VoIP monthly rebills
  • Run 3D Secure 2.0 on initial CoF —  — authenticate the first transaction to shift fraud liability to the issuer on subsequent merchant-initiated seat-renewals
  • Cap velocity and BIN-block on prepaid top-up —  — per-card and per-IP balance-load limits, BIN-block lists for known fraud BINs, and IP-geofencing on signup defeat the bulk of telecom-fraud-card-use against international long-distance termination
  • Send pre-rebill notifications on seat-renewals —  — a transactional email or in-app notice 1-7 days before each monthly seat-renewal reduces telecom continuity friendly fraud by 20-30%
  • Track chargeback reason codes monthly —  and address the top three VoIP sources (13.2 cancelled recurring on seat-renewals, 13.1 service not provided on outages, 10.4 fraud-card-not-present on international top-up) before they trigger ECM enrollment
  • Document port-out requests —  — archive the port-out authorization, CDR usage through the port date, and pro-rated final-invoice math so port-out representments have the evidence package they need
  • Distribute VoIP volume across multiple MIDs —  via cascading gateway logic so the international top-up book and the business-VoIP seat-renewal book are on separate MIDs and a fraud spike on one doesn't threaten the other
  • Keep FCC and USF filings current —  — FCC Form 499-A and 499-Q filings, Section 214 status, CALEA compliance certificate, and state PUC registrations must stay current or the acquirer's compliance team can flag the MID for review
  • Enroll Account Updater —  — Visa, Mastercard, and Amex automatically refresh expired or reissued cards, preventing the involuntary VoIP-service-disconnect that often triggers an angry chargeback the day after disconnection
  • File representment on friendly fraud —  with compelling-evidence packages including signed consent, login activity, CDR usage proof, pre-rebill notification email logs, and cancellation-flow screenshots, within the 30-day dispute window
  • Maintain ROSCA-style cancellation symmetry —  — online cancel-anytime button that takes the same number of clicks as the sign-up flow, no retention-rep phone gauntlet for direct VoIP cancel
Payment processing
Frequently Asked Questions

Questions merchants ask before applying

Do I sign a long-term contract on a VoIP merchant account?

No. 2Accept VoIP agreements do not include early termination fees or multi-year lock-in. You may close the VoIP account with 30 days written notice. The acquiring bank retains the rolling reserve for 180 days post-closure to cover any lingering continuity-billing chargebacks or port-out disputes that filter in after the final batch settles.

What documents do I need to apply for a VoIP merchant account?

A VoIP 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 checkout, full VoIP service flow walkthrough (sign-up consent, terms acceptance, cancellation page UX, port-out flow), FCC Section 214 grant or pending application, USF contributor filings (FCC Forms 499-A and 499-Q current with USAC), CALEA Section 105 compliance certificate, E911 / Kari's Law / RAY BAUM'S Act deployment documentation, state PUC registrations for the jurisdictions you serve, HIPAA BAA template if you serve healthcare clients, and your telecom-fraud controls walkthrough (velocity caps, BIN-block lists, IP-geofencing) for prepaid top-up and international long-distance flows.

Is there an application fee for a VoIP merchant account?

No. 2Accept does not charge an application fee, underwriting fee, or setup fee on VoIP accounts. You only pay transaction fees once your VoIP MID goes live and starts processing seat-renewals, metered usage, or prepaid top-ups. There is no fee to be reviewed, and there is no fee if you are declined.

How do I integrate my VoIP billing platform after approval?

After approval, 2Accept provides native gateway connectors for Recurly, Chargebee, Maxio (formerly Chargify and SaaSOptics), Zuora, and a native 2Accept VoIP gateway. Custom VoIP billing stacks (FreeSWITCH, Asterisk, Kamailio, Sansay, Metaswitch, Ribbon, or in-house billing engines) integrate through REST API with full webhook coverage for billing lifecycle events (seat-renewed, top-up loaded, payment failed, account suspended for non-payment, reactivated, port-out completed). Stripe Billing migrators get a one-click data-export tool that ports customers, subscriptions, and tokens to the new MID without forcing customers to re-enter card details.

Can I apply with bad personal credit if I'm running a VoIP business?

Yes. Personal credit below 600 does not automatically disqualify a VoIP merchant. Acquirers weigh VoIP business volume, churn rate, chargeback ratio, FCC and USF compliance posture, and telecom-fraud control quality more heavily than personal FICO. A personal guarantee is typically required on sub-600 credit applications, and the acquirer may add a 5-10% rolling reserve until 90 days of clean continuity processing.

Can I apply if Stripe or another aggregator terminated my VoIP account?

Yes. 2Accept specifically underwrites VoIP merchants terminated by Stripe, Square, PayPal, or other aggregators. Full disclosure of the termination reason is required, along with a remediation plan addressing whatever caused the termination (continuity-billing friendly fraud, international long-distance fraud-card-use, FCC compliance gap, port-out dispute volume, or telecom MCC mismatch). MATCH-listed VoIP merchants are placed on offshore acquirers with a 90-day rolling reserve and progressive rate-review at 6 months.

Can I apply for a VoIP MID if I'm based outside the United States?

Yes. 2Accept onboards both U.S.-based and non-U.S. VoIP merchants. Non-U.S. VoIP brands are placed with offshore acquiring banks in the U.K., EU, Caribbean, or APAC with multi-currency settlement in USD, EUR, GBP, CAD, AUD, and JPY so EU and APAC subscribers settle in their local currency without FX surprises on the cardholder statement. U.S. VoIP entities qualify for domestic MIDs with next-day funding and Account Updater enrollment in your business name. Non-U.S. operators providing service into the U.S. still need FCC Section 214 authority and USF contributor status.

Do I need an existing VoIP business to apply?

Yes. Acquiring banks require a registered legal entity (LLC, Corp, or DBA), an EIN, a business bank account in the legal entity's name, and a live VoIP service with working checkout, consent capture, and the foundational telecom compliance posture (FCC Section 214 application filed, USF Form 499-A registered with USAC, CALEA Section 105 plan in place, E911 / Kari's Law deployment underway). Startup VoIP brands under 6 months old qualify at mid-tier rates with a personal guarantee from the principal and a 90-day rolling reserve that typically drops after 90 days of clean rebill processing.

What is interchange and does 2Accept pass it through on VoIP transactions?

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. VoIP seat-renewal transactions qualify for lower interchange rates when properly flagged as merchant-initiated recurring (MIT) rather than customer-initiated, so flagging matters on every monthly rebill. 2Accept offers both flat-rate pricing (discount rate includes interchange) and interchange-plus pricing (interchange passed through plus a fixed 0.5%-1.5% markup) for VoIP merchants processing above $100K monthly. High-volume hosted PBX and CPaaS merchants almost always choose interchange-plus to capture the recurring-billing interchange savings on seat-based SaaS.

Are there any hidden fees on VoIP accounts?

No. 2Accept publishes a flat monthly statement with your discount rate, per-transaction fee, monthly gateway fee, Account Updater fee (typically waived above $50K monthly volume), and chargeback fee only. There are no PCI non-compliance surcharges, no early termination fees, no monthly minimums on most VoIP MIDs, no junk-fee line items, and no per-rebill notification surcharges. Note that the USF contribution factor (~33% of interstate revenue) is a separate cost recovered from your customers on their invoices, not a processing fee.

Can my VoIP rate decrease over time?

Yes. After 6 months of clean VoIP processing (chargeback ratio under 0.5%, consistent rebill volume, no bank complaints, current FCC Section 214 / USF / CALEA / E911 compliance, and clean port-out dispute history), 2Accept can submit a rate review request to the acquiring bank. Successful VoIP rate reviews reduce the discount rate by 0.25%-0.75%. Annual-prepay business-VoIP and hosted-PBX seat-based SaaS see the largest reductions because the dispute exposure on annual rebills is structurally lower than monthly continuity, and clean compliance posture meaningfully de-risks the acquirer's regulatory exposure.

What is the chargeback fee on a VoIP account?

Chargeback fees on 2Accept VoIP merchant accounts range from $15 to $40 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 in the first place, and pre-rebill notifications on seat-renewals reduce the inbound dispute volume by 20-30%, so the effective per-rebill chargeback cost on a well-managed VoIP MID is dramatically lower than the headline fee suggests. Port-out disputes carry the same chargeback fee as standard friendly-fraud disputes but have a higher representment win rate when the evidence package includes the port-out authorization log and CDR usage proof.

What rates should I expect on a VoIP merchant account?

VoIP rates start at 2.89% for clean business-VoIP seat-based SaaS with annual-prepay revenue mix, NRR-compliant pre-rebill notifications, chargeback ratio under 0.9%, and no international long-distance termination exposure. Mid-tier residential VoIP and CPaaS programmable voice with monthly seat plus metered usage price at 3.49%-3.95% depending on history. International long-distance prepaid top-up and high-volume VoIP merchants with elevated telecom-fraud-card-use run 3.95%-4.50%. Your final VoIP rate depends on monthly volume, average ticket, chargeback ratio, billing model (seat-based vs. metered vs. prepaid top-up), and your FCC / USF / E911 compliance posture.

When does my VoIP MID fund?

Domestic U.S. VoIP merchant accounts receive next-day funding via ACH for all batches submitted before 8:00 PM ET. Offshore VoIP acquiring accounts fund on a weekly or bi-weekly schedule (T+3 to T+7). High-volume VoIP merchants can negotiate same-day funding through wire transfer for batches above defined thresholds.

Do VoIP merchants need a rolling reserve?

Most VoIP merchant accounts often carry a 0%-10% rolling reserve held for 180 days to cover the structurally higher dispute exposure on telecom continuity billing and international long-distance fraud-card-use. Established business-VoIP brands with annual-prepay revenue mix and clean processing history can qualify for zero-reserve domestic accounts. New residential VoIP brands and international long-distance prepaid top-up merchants typically sit toward the 5-10% end. Reserve percentages can be renegotiated downward after 6 months of clean VoIP processing under 0.5% chargeback ratio.

Is there a monthly minimum on a VoIP MID?

Not always. 2Accept does require monthly minimum VoIP processing volume in circumstances where the approval is laborious or the account would operate at a loss when volume is low or zero. You will always pay transaction fees only on the volume you process. Some acquiring banks on top-tier international long-distance prepaid top-up VoIP verticals may set a $25K monthly minimum to maintain the MID, but standard business-VoIP seat-based SaaS MIDs typically carry no minimum.

Do you work with offshore VoIP merchants?

Yes. 2Accept holds acquiring relationships with banks in the United States, United Kingdom, European Union, Caribbean, and APAC regions that approve VoIP and telecom billing. Non-U.S. VoIP operators open accounts with multi-currency settlement in USD, EUR, GBP, CAD, AUD, and JPY so EU and APAC subscribers settle in their local currency without FX surprises that drive 'I don't recognize this charge' disputes. Non-U.S. operators providing service into the U.S. still need FCC Section 214 authority for international service and USF contributor status.

What qualifies a VoIP business as high risk?

A VoIP business is classified high risk because its MCC (4814 for telecommunication services, 4812 for telecommunication equipment, 4813 for key system / multi-station phone services, 7372 for computer software / SaaS used by CPaaS API platforms) is on the restricted MCC list, because telecom continuity billing carries a structurally higher chargeback baseline (~12.6 disputes per 1,000 transactions), because international long-distance termination is one of the highest-fraud product categories on the card networks (telecom-fraud-card-use is a perennial Visa and Mastercard watch-list item), and because the FCC's Section 214, USF, CALEA, and E911 / Kari's Law / RAY BAUM'S Act create federal regulatory liability that aggregators are not equipped to underwrite at scale.

Can I process international long-distance VoIP with prepaid top-up?

Yes, so long as your storefront has telecom-fraud controls in place — velocity caps per card and per IP, BIN-block lists for known fraud BINs, IP-geofencing on signup, and balance-cap-per-card rules that prevent a single card from loading large balances quickly. International long-distance prepaid top-up is one of the highest-fraud-card-use product categories on the card networks, so the acquirer's underwriter audits your control posture before approval. Clean international long-distance retailers qualify with 5-10% rolling reserve depending on history; merchants with elevated fraud history are placed offshore with progressive rate review at 6 months.

Can I sell white-label VoIP through an MSP / IT-channel reseller program?

Yes. White-label VoIP reseller programs serving the MSP and IT-channel market qualify on MCC 4814 with either a platform-billing model (the platform bills the MSP, the MSP bills the end customer separately) or an end-customer-billing model (the platform bills the end customer directly under the MSP's brand via dynamic descriptor). The platform-billing model carries lower chargeback exposure because the end-customer-facing brand is the MSP, not the platform, but the underwriter audits the reseller agreement and end-customer service terms in either case.

Can I combine hosted PBX seats and SIP trunking minutes under one MID?

Some VoIP product combinations share one MID (hosted PBX seats + SIP trunking minutes + cloud contact center seats under MCC 4814 with a single billing engine). Cross-MCC combinations require segregated MIDs — VoIP service on MCC 4814 cannot share an MID with a hardware-bundle storefront selling IP phones and ATAs on MCC 4812, and a pure CPaaS API platform on MCC 7372 typically gets a separate MID from a hosted-PBX seat MID on MCC 4814 because the dispute-rule framework differs by MCC. Your VoIP underwriter structures one or multiple MIDs based on your full product mix and revenue split.

Do you underwrite hosted PBX providers competing with RingCentral, 8x8, Vonage, or Zoom Phone?

Yes. 2Accept underwrites hosted PBX providers competing in the $30B+ business-VoIP market on MCC 4814 with monthly seat-based SaaS billing, per-extension pricing, unlimited US/Canada, and metered international long-distance overage. The underwriter audits your FCC Section 214 status, USF Form 499 filings, CALEA Section 105 compliance, and E911 / Kari's Law deployment as part of the underwriting cycle. Clean hosted-PBX merchants with annual-prepay mix qualify for the lowest VoIP rates (starting at 2.89%).

Do you underwrite CPaaS programmable voice platforms (Twilio-style)?

Yes. CPaaS programmable voice operators exposing SIP, PSTN, WebRTC, and SMS as developer-priced API primitives qualify under MCC 7372 (computer software / SaaS) with metered usage billing on a per-minute, per-SMS, and per-API-call basis. The underwriter audits your usage-fraud controls (rate limiting, per-account spend caps, anomaly detection on novel API consumption patterns) because CPaaS platforms are a frequent target of credential-stuffing attacks that drive fraudulent international call traffic. Clean CPaaS platforms with established usage-fraud detection qualify for mid-tier pricing.

Do you support HIPAA-compliant VoIP for healthcare clients?

Yes. HIPAA-compliant VoIP for medical practices, telehealth platforms, and behavioral-health providers qualifies on MCC 4814 with a Business Associate Agreement in place between your platform and the healthcare client. The acquirer's compliance team reviews your BAA template, encryption posture (TLS / SRTP), call-recording handling, and breach-notification procedure as part of the underwriting cycle. HIPAA-compliant VoIP merchants qualify for the same rate tier as standard business-VoIP.

How long does it take to get a VoIP MID approved?

Most VoIP merchant accounts are approved in 24-48 hours after complete documentation is received. Clean business-VoIP seat-based SaaS with annual-prepay mix and full FCC / USF / CALEA / E911 documentation approves in 24-48 hours. Residential VoIP with metered international long-distance exposure, prepaid top-up flows, and CPaaS platforms may require 3-5 business days due to telecom-fraud controls audit, FCC Section 214 status verification, USF contributor filing review, and additional bank vetting on the continuity-billing dispute history. MATCH-listed VoIP applicants placed on offshore acquirers typically take 5-7 business days.

What's your VoIP approval rate?

98% of VoIP merchants who complete a full application with all required documentation (FCC Section 214 grant or pending application, USF Forms 499-A and 499-Q current, CALEA Section 105 compliance certificate, E911 / Kari's Law / RAY BAUM'S Act deployment, state PUC registrations, NRR-compliant sign-up consent, telecom-fraud controls on prepaid top-up, processing history) get approved. The 2% rejection rate is driven by OFAC sanctions matches, active bankruptcy proceedings that cannot be mitigated with reserves and security deposits, missing FCC Section 214 authority on international VoIP service, lapsed USF filings, no E911 deployment in jurisdictions requiring it, FCC consent decree history, or the applicant being on the card brand's internal telecom-fraud watchlist.

Do you pull my personal credit on a VoIP application?

A soft credit inquiry is run during VoIP 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 for high-volume continuity-billing approvals or MATCH-listed remediation applications.

Can I be approved for VoIP processing without prior VoIP processing history?

Yes. New VoIP businesses without prior processing can be considered at mid-tier pricing with a 0-10% rolling reserve and personal guarantee. Projected VoIP volume, billing-model design, FCC / USF / CALEA / E911 compliance posture, business plan, principal experience, and the quality of your sign-up, cancellation, and port-out flows substitute for processing history. The reserve drops after 90 days of clean continuity-billing processing under 0.5% chargeback ratio.

What increases my chance of VoIP approval?

Clean VoIP processing history (chargeback ratio under 0.5%), six or more months of bank statements showing consistent rebill revenue, a live and fully functional VoIP service with NRR-compliant sign-up consent and ROSCA-compliant cancellation flow, FCC Section 214 already granted (not pending), USF Forms 499-A and 499-Q current with USAC, CALEA Section 105 compliance certificate in hand, E911 / Kari's Law deployment fully live, dynamic billing descriptors already configured, pre-rebill notification email cadence in place on seat-renewals, telecom-fraud controls (velocity caps, BIN-block, IP-geofencing) tuned for prepaid top-up flows, and annual-prepay revenue mix all strengthen approval. Personal credit above 650, entity formation over 12 months old, and prior VoIP processing history also help but are in no way required.

What happens if my VoIP application is denied?

If a primary acquirer denies your VoIP application, 2Accept automatically reshops it to secondary and offshore VoIP-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 VoIP underwriting (typically focused on FCC compliance gaps, USF filing remediation, E911 deployment, telecom-fraud control tuning, or chargeback ratio reduction before reapplication).

What causes a first-pass rejection on a VoIP application?

First-pass VoIP rejections usually result from missing or pending FCC Section 214 authority on international service, lapsed USF Form 499-A or 499-Q filings, missing CALEA Section 105 compliance certificate, no E911 / Kari's Law / RAY BAUM'S Act deployment in jurisdictions where it is required, a cancellation flow that fails ROSCA click-to-cancel symmetry (mandatory phone-call cancel, retention-rep gauntlet), no telecom-fraud controls on prepaid top-up or international long-distance flows, a disclosed chargeback ratio above 1.5%, FCC consent decree history, or the applicant's domain appearing on the card brand's internal telecom-fraud watchlist. 2Accept's VoIP underwriter catches most of these before submission to prevent rejections.

Can I get VoIP processing if I'm on the MATCH list?

Yes. 2Accept can consider MATCH-listed VoIP applicants. Full disclosure of the termination reason code and a remediation plan addressing the continuity-billing dispute pattern or telecom-fraud-card-use that caused the listing are required. MATCH-listed VoIP merchants are typically placed on offshore acquirers with a 90-day rolling reserve and progressive rate-review at 6 months of clean rebill processing.

How do chargeback alerts work on VoIP transactions?

Ethoca Alerts and Verifi CDRN forward dispute intents from issuing banks before they post as chargebacks. On VoIP 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 VoIP MID's ratio. On telecom continuity-billing MIDs the refund-before-chargeback strategy is the dominant ratio-management tool because friendly-fraud disputes ('I didn't authorize this monthly charge') resolve cleanly with a refund and rarely revert to a full chargeback once the customer sees the refund post.

What counts as a chargeback vs a refund on a VoIP rebill or top-up?

A refund is initiated by the merchant and returns funds to the VoIP subscriber 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, with 13.2 cancelled-recurring being the dominant VoIP seat-renewal code and 10.4 fraud-CNP being the dominant international top-up code), counts against the VAMP/ECM ratio, and imposes a $15-$40 chargeback fee regardless of outcome. Refund-before-chargeback is the core prevention strategy on VoIP MIDs — when an Ethoca or Verifi alert lands, the playbook is to refund immediately rather than dispute, so the ratio stays clean and the subscriber relationship can sometimes be salvaged on a future re-enrollment.

What is reason code 13.2 (cancelled recurring) and how do I defend it on a VoIP seat-renewal?

Reason code 13.2 is a Visa dispute code raised when a customer claims they cancelled the VoIP service but were rebilled anyway on the monthly seat-renewal. It is the highest-volume dispute code on VoIP continuity-billing MIDs. Defense requires three pieces of evidence in the representment package: the original sign-up consent with material-terms disclosure above the buy button, the cancellation-flow screenshot proving ROSCA click-to-cancel symmetry, and a customer-account log showing no cancellation action was taken before the disputed seat-renewal. With all three plus CDR proof of active VoIP usage through the disputed billing period, representment win rates on 13.2 disputes run 60%+ — without the cancellation-log and CDR proof, win rates drop below 30%.

Does 3D Secure 2.0 eliminate fraud chargebacks on VoIP transactions?

3DS 2.0 shifts liability for fraud-based chargebacks (reason codes 10.4, 83) from the merchant to the issuing bank on the initial authenticated card-on-file transaction. Subsequent merchant-initiated seat-renewals inherit the authentication context from the initial CoF authorization, so the liability shift carries forward on the recurring schedule. 3DS does not eliminate friendly-fraud, 'cancelled recurring,' 'service not provided,' or port-out disputes — common on VoIP MIDs. Implementing 3DS on the initial CoF and on prepaid top-up balance loads typically reduces total VoIP chargebacks by 20-35% and significantly cuts telecom-fraud-card-use against international long-distance termination.

Can I fight friendly fraud chargebacks on VoIP seat-renewals and port-out disputes?

Yes. 2Accept's representment team files compelling-evidence packages on VoIP disputes (signed sign-up consent, click-to-cancel UX screenshots, login activity logs, pre-rebill notification email send record, CDR (call detail record) usage proof, port-out authorization log, pro-rated final-invoice math, AVS and CVV match, ToS acceptance) to win friendly-fraud cases at roughly 55%+ for 2Accept-managed VoIP disputes. The CDR usage proof is the single strongest piece of evidence on port-out disputes — archive every customer's call detail records through the port date so you can prove service was actively used through the billing period in question.

How do I defend a port-out cancellation dispute?

Port-out cancellation disputes happen when a customer ports their phone number to a competing VoIP or wireless carrier and then disputes the final pro-rated invoice from your service. Defense requires the LOA (Letter of Authorization) the customer signed for the port-out, the port-out completion timestamp from your softswitch or LNP database, the CDR (call detail record) usage log showing the customer actively used the service through the port date, and the pro-rated final-invoice math showing the disputed amount reflects only service rendered through the port date. With this evidence package, port-out representment win rates run 55-65%.

What chargeback ratio will get my VoIP account closed?

Visa's VAMP and Mastercard's ECM threshold is 1.5%; for telecom continuity-billing MCCs (4814 in particular) the effective monitoring threshold runs tighter because dispute reason codes 13.2 (cancelled recurring on seat-renewals) and 13.1 (service not provided on outages) carry extra scrutiny on the VoIP baseline of ~12.6 disputes per 1,000 transactions. Crossing 1.5% triggers Early Warning monitoring on your VoIP MID. Staying over for 4+ months leads to enrollment in VAMP or ECM, escalating fines of $25,000-$200,000, and possible VoIP MID termination with MATCH listing. Pre-rebill notifications on seat-renewals and Account Updater enrollment are the most effective ratio-management tools on a VoIP MID.

How long does representment take on a VoIP chargeback?

A Visa representment cycle on VoIP disputes resolves in 45-60 days: merchant submits evidence (30 days), issuer reviews (30 days), and the final case status posts in the merchant portal. Mastercard cycles run 45 days. Amex resolves in 20 days. Winning representments recover both the VoIP rebill or top-up amount and the chargeback fee. VoIP representment timelines are unchanged from other continuity-billing categories, but the evidence-package composition is different (consent + cancel-flow + login logs + CDR usage proof + port-out authorization vs. delivery + signature on physical goods).

How is 2Accept different from PaymentCloud, Durango, or Soar Payments for VoIP?

PaymentCloud, Durango, and Soar are ISOs/MSPs similar to 2Accept, but they operate primarily as resellers with variable pricing and don't specialize in VoIP-specific underwriting or telecom regulatory compliance. 2Accept publishes flat-tier pricing upfront (2.89% / 3.49% / 4.95%), includes chargeback alerts, Account Updater, and telecom velocity caps in standard plans, provides dedicated VoIP underwriters who understand FCC Section 214, USF Form 499 filings, CALEA Section 105, E911 / Kari's Law / RAY BAUM'S Act, state PUC registration, HIPAA BAA for healthcare VoIP, port-out-dispute representment, and CPaaS usage-fraud controls, and offers guaranteed 24-48-hour approvals on clean business-VoIP seat-based SaaS with 98% approval rate.

How does 2Accept compare to Recurly, Chargebee, or Maxio for VoIP billing?

Recurly, Chargebee, and Maxio are subscription billing platforms — they handle the subscription lifecycle (sign-up, seat-renewal scheduling, dunning, plan changes, proration, customer portal) but they do not underwrite or settle the funds themselves. They sit on top of an acquiring bank's MID. 2Accept ships native gateway connectors for all three platforms, so you keep Recurly, Chargebee, or Maxio as your VoIP billing engine and replace only the acquiring bank behind it. The subscriber experience stays identical and the data integration is a one-click connector swap.

Can I run two processors at once for VoIP redundancy?

Yes. Running a primary and backup VoIP processor (or multi-MID load balancing across 2-5 VoIP accounts) is standard risk practice for high-volume telecom continuity-billing merchants. 2Accept builds multi-MID structures into Mid-Tier and Top-Tier VoIP plans by default. The cascading gateway routes failed seat-renewals on one MID to the backup MID's vault, so a temporary MID-level decline doesn't translate into an involuntary-service-disconnect event for the customer. Splitting the international long-distance top-up book onto a separate MID from the business-VoIP seat-renewal book is the standard isolation pattern.

What about Stripe Billing migration — can I move my existing VoIP subscribers without forcing re-card-entry?

Yes. Stripe Billing migrators get a one-click data-export tool from 2Accept that ports customers, subscriptions, seat-renewal schedules, and PAN-level tokens to the new MID without forcing subscribers to re-enter card details. The migration uses card-brand-supported token portability under PCI-DSS controls. Account Updater on the new MID picks up any cards that expired during the cutover, so the post-migration involuntary-service-disconnect spike that ruins most VoIP processor migrations is contained — critical because a VoIP service disconnect is far more disruptive to the customer than a missed magazine delivery.

Can I use Shopify Payments for my VoIP storefront?

No. Shopify Payments is powered by Stripe and restricts telecom MCCs (4814 in particular) and continuity-billing categories in its acceptable-use policy. VoIP merchants regularly get frozen on Shopify Payments when their seat-based SaaS scales or international long-distance top-up patterns appear in the dispute mix. 2Accept integrates directly with Shopify as a third-party gateway, replacing Shopify Payments while keeping the native Shopify checkout experience intact — useful for hardware-bundle VoIP storefronts selling IP phones (Polycom, Yealink, Grandstream) and ATAs alongside the recurring VoIP service.

Do you integrate with Twilio-style CPaaS, FreeSWITCH, Asterisk, Kamailio, or commercial softswitches like Sansay, Metaswitch, or Ribbon?

Yes. 2Accept integrates with CPaaS API platforms through REST API with full webhook coverage for usage-metered billing events. Open-source softswitch deployments on FreeSWITCH, Asterisk, or Kamailio integrate through REST API or direct Authorize.net / NMI / USAePay gateway connections. Commercial softswitches (Sansay, Metaswitch, Ribbon, Genband, BroadWorks) integrate via their native billing-export hooks plus 2Accept's gateway connectors. Integration support is free for the lifetime of the VoIP account, including help wiring up dunning hooks on seat-renewals, Account Updater callbacks, pre-rebill notification triggers, and telecom velocity-cap configuration.

Can I keep my current gateway and just switch VoIP processors?

Yes. If you currently use Authorize.net, NMI, USAePay, or any compatible gateway for your VoIP checkout, 2Accept switches only the acquiring bank behind it. Your VoIP checkout, customer vaulting, seat-renewal schedules, dunning logic, customer portal, port-out flow, and call detail record export remain in place with no subscriber-visible change and no re-integration work. The cutover typically completes inside one business day with zero downtime on the active VoIP subscriber book.

How does 2Accept compare to Stripe or Square for VoIP processing?

Stripe, Square, and PayPal are payment aggregators that pool thousands of merchants under one master MID and enforce telecom-MCC and continuity-billing risk caps at the aggregator level rather than per-merchant. Telecom MCCs (4814, 4812, 4813) sit in Stripe's restricted acceptable-use list, and even VoIP accounts they initially approve get frozen the moment continuity-billing chargebacks rise or international long-distance fraud-card-use appears in the dispute mix. 2Accept issues a dedicated VoIP MID from an acquiring bank that explicitly approves MCC 4814 / 4812 / 4813 / 7372, so the account cannot be shut down for doing the VoIP business it was approved to serve unless laws, regulations, or card brand rules change.

Ready to open your voip merchant account?

Underwriting review in 1 business hour. Full approval in 48.

No application fee
98% approval rate
Dedicated human underwriter
More verticals we underwrite

Adjacent industries 2Accept also approves

VoIP operators frequently expand into adjacent recurring-revenue and telecom-adjacent verticals as their business matures — a hosted PBX provider adds a managed-IT subscription tier, a CPaaS platform layers in SMS messaging and email-delivery products, a residential VoIP brand adds an IPTV bundle to compete with cable-replacement packages, an international long-distance retailer launches a money-transfer corridor along the same diaspora customer base, and a contact-center-as-a-service operator rolls out a per-minute tarot or psychic advice platform built on the same softswitch. 2Accept underwrites all of these neighboring verticals under the same acquiring relationships, so a VoIP brand layering a new recurring or telecom-adjacent product line doesn't restart underwriting from scratch.


Many 2Accept VoIP merchants run multiple MIDs as their service mix diversifies — a primary MID for monthly seat-based business VoIP, a separate MID for international long-distance prepaid top-up with elevated telecom-fraud exposure, and a third MID for a hardware-bundle storefront selling IP phones and ATAs under MCC 4812. We structure these as separate accounts under one master underwriting relationship so chargeback ratios are isolated per product line and a telecom-fraud spike on the international top-up book doesn't threaten the established business-VoIP seat-renewal book. Volume load-balances across MIDs through our cascading gateway, and each MID's FCC and USF compliance posture is monitored independently.

GET STARTED