Opening an enterprise merchant account through 2Accept gives a multi-entity organisation one acquiring relationship that is shaped like its org chart — a dedicated MID for each legal entity, business unit and brand, settlement reports that tie back to the general ledger entity by entity, tokenisation and point-to-point encryption that take systems out of PCI scope, and a named account team that answers procurement, treasury and security questions in writing. Our enterprise merchant accounts include holding companies with several operating subsidiaries, multi-brand retail and hospitality groups, private-equity portfolio roll-ups, multi-location healthcare and service organisations, manufacturers and distributors, and companies running stores, e-commerce, a call centre and invoicing at the same time.
The process of opening an enterprise merchant account with 2Accept takes four steps. First, complete the online application with the parent company's EIN and formation documents, an organisation chart showing every legal entity that will accept cards, beneficial-ownership details, recent financial statements, three months of processing statements for each existing MID, and a list of your channels, gateways, ERP and current token vault. Second, a dedicated underwriter reviews entity structure, volume by entity and channel, card mix, dispute history and funding requirements within one business hour, and returns an underwriting decision within 48 hours. Third, your account team works through security review, contract terms and the MID hierarchy with your procurement, treasury and IT teams, then issues MIDs after each entity signs its merchant processing agreement. Fourth, entities go live in phases — new channels first, vaulted cards after the token migration completes — with entity-level reporting, account updater and chargeback alerts already configured.
Rates for an enterprise merchant account on 2Accept start at 2.89% + $0.20 for low-risk verticals, and interchange-plus pricing is standard above roughly $250,000 a month, which most enterprise groups exceed at the parent level. Pricing depends on combined and per-entity volume, the split between card-present, e-commerce, keyed and invoiced transactions, the share of commercial cards that can carry Level 2 and Level 3 data, cross-border volume, dispute ratios, and the risk tier of each business unit's vertical — a regulated subsidiary prices at its own tier, not the group's.
Enterprise buyers do not evaluate a processor on rate alone. Finance asks whether deposits will reconcile to the ledger, IT asks what stays in PCI scope, procurement asks what the contract commits each side to, and operations asks who picks up the phone when a batch fails to settle. 2Accept covers each of those questions below and underwrites the entity structures, channels and reporting configurations listed here.
The card networks expect the merchant of record to be the legal entity that actually sells to the cardholder, so an enterprise with twelve subsidiaries does not have one merchant account — it has at least twelve. 2Accept boards each legal entity under its own EIN and its own merchant processing agreement, then arranges the MIDs in a hierarchy: parent, entity, brand or business unit, and channel or location beneath that. The right MCC is assigned per unit instead of one code stretched over the whole group.
The hierarchy is what makes everything else work. Reporting rolls up or drills down along it, user permissions follow it so a regional controller sees only their entities, descriptors carry the brand the customer recognises, and each unit's dispute ratio is measured separately. When the group acquires a company or launches a brand, a MID is added to the tree against the ownership documents already on file.
Apply for a MID Hierarchy →Month-end is where a payments setup shows its quality. A controller needs every bank deposit to tie to a batch, every batch to its transactions, and every fee, refund and chargeback to the entity and cost centre that owns it. 2Accept sets up settlement so each MID funds the bank account of the entity that earned the revenue, with deposit-level reports listing the transactions, interchange and adjustments inside each transfer. Funding is typically next-day, on a schedule agreed with treasury at onboarding.
Reports are delivered as scheduled exports or through the gateway API in a layout your team maps once to SAP, Oracle NetSuite, Microsoft Dynamics 365 or whichever ledger you run. Where the acquirer supports it, fees can be billed monthly instead of netted daily, so each deposit matches the day's batch total. Multi-currency settlement is available for units with cross-border sales.
Apply for Entity-Level Settlement →A merchant processing more than six million Visa or Mastercard transactions a year is a PCI DSS Level 1 merchant, validated by an annual on-site assessment and Report on Compliance instead of a self-assessment questionnaire. The cost of that assessment tracks the number of systems that store, process or transmit card data. The design goal is therefore to make that number as small as possible before the assessor arrives.
Hosted fields and hosted payment pages keep card numbers off your web servers, PCI-validated point-to-point encryption terminals encrypt at the point of read so store networks carry no clear card data, and vault tokens replace card numbers in the ERP, CRM and order systems. For your vendor-risk process we answer security questionnaires in writing and gather the PCI Attestations of Compliance for the gateway and processing platforms in the proposed stack.
Apply for a PCI Scope Review →Most enterprises built their payment stack one channel at a time: a terminal provider for the stores, a different processor behind the website, a virtual terminal someone set up for the call centre, and invoices paid by bank transfer. Each has its own contract, rates, reports and token format. 2Accept boards every channel under one relationship — EMV and contactless terminals for card-present, a gateway or REST API with hosted fields for e-commerce, a virtual terminal for mail and telephone orders, and payment links for invoicing.
Each channel gets its own MID or sub-account so card-present volume is not priced or risk-scored like keyed volume, and a shared vault lets a card saved online be charged by the call centre or billed on an invoice. For telephone orders, a payment link sent to the caller keeps the card number out of the call recording and off the agent's screen.
Apply for Omnichannel MIDs →The stored cards behind your subscriptions, accounts and repeat customers belong to your business, but they sit in your current processor's vault as tokens only that processor can read. Moving them is a provider-to-provider transfer: your current processor exports the card numbers and expiry dates in encrypted form to the new PCI DSS Level 1 vault, the new vault issues its own tokens, and you receive a mapping file that pairs old token with new so your systems can be updated without a customer typing anything.
Two limits are worth knowing up front. Security codes are never stored, so they cannot move, and network tokens issued to the old provider are normally re-provisioned instead of transferred. The timetable is set largely by the outgoing processor and commonly runs to several weeks.
Apply for a Vault Migration →Enterprise accounts are assigned a named account team, led by the underwriter who built the file and including a contact who runs boarding and cut-over. The same people handle a held batch, a new-entity request and the periodic account review, so nobody re-explains the org chart to a queue. Pricing is quoted as interchange plus a fixed markup, with every recurring and per-item fee listed in a schedule your procurement team can read before anyone signs.
Accounts are month-to-month with no early-termination fee, which most procurement teams find simpler than negotiating an exit clause. One thing stated plainly: 2Accept places and manages your accounts but is not the bank or the gateway, so platform uptime commitments come from those providers, and we show you theirs instead of writing our own.
Apply for an Enterprise Account Team →Every high risk merchant account is priced by risk tier, and an enterprise group is priced entity by entity. Each business unit's vertical, volume and chargeback ratio determine the tier it underwrites at. Low-risk units sit on the low tier with interchange-plus standard above roughly $250,000 a month; a unit in a regulated or high-dispute vertical prices at its own tier without pulling the rest of the group up with it. Rates are average and may vary depending on individual circumstances and risk profile. Interchange may be passed to merchants for more challenging approvals.
Complete the 4-minute application. No credit pull, no application fee, no long-term contract.
A 2Accept underwriter reviews your entity chart, volume by business unit and channel, card mix and dispute history within 1 business hour.
The underwriting decision lands within 48 hours; security review, contract terms and vault migration then set the pace of the rollout.
Board business units in phases with entity-level settlement, tokenised channels, and a named team handling each new MID and acquisition.
Connect your merchant account to the storefront, POS, accounting, and CRM software you already run.
2Accept enables smooth payment operations across Shopify stores.
2Accept connects with Clover POS for seamless point-of-sale transactions.
2Accept syncs payments with QuickBooks to simplify accounting and reconciliation.
2Accept supports BigCommerce to facilitate online payment processing.
2Accept integrates with Authorize.net for secure transactions.
2Accept connects with Salesforce to streamline customer relationship management.
2Accept extends payment capabilities to WooCommerce-powered online stores.
Aggregators give an enterprise a login, not a structure. A pooled account has no notion of a subsidiary, so brands and entities end up as tags on one balance, one payout and one risk file — and finance rebuilds the entity view in spreadsheets every month-end. Security questionnaires go to a help centre, and contract terms are a click-through. A dedicated MID hierarchy from 2Accept gives each legal entity its own account, its own deposits and its own dispute ratio, with a person accountable for the answers.
| Feature | 2Accept | Stripe | Square | PayPal |
|---|---|---|---|---|
| Own MID and MCC for each legal entity and brand | ✓ | ✕ | ✕ | ✕ |
| Dispute ratio isolated per entity, not pooled | ✓ | ✕ | ✕ | ✕ |
| Underwriting completed before volume, not after | ✓ | ✕ | ✕ | ✕ |
| Named account team from the first application | ✓ | ✕ | ✕ | ✕ |
| Each channel priced on its own MID, not one blended rate | ✓ | ✕ | ✕ | ✕ |
| Dedicated MID (not aggregator pool) | ✓ | ✕ | ✕ | ✕ |
| Human underwriter (not chatbot) | ✓ | ✕ | ✕ | ✕ |
Every 2Accept high risk merchant account includes the monitoring and mitigation stack needed to keep each entity's MID under card-network dispute and fraud thresholds — measured per entity and per channel, so one business unit cannot hide another's problem.
Ethoca and Verifi alerts are routed to the entity that owns the sale, so the right customer-service team refunds a disputed order before it posts against that unit's MID.
Rules are tuned per channel — AVS and CVV on keyed and call-centre orders, velocity and device checks online — because a store, a website and a phone room attract different fraud.
3-D Secure 2 shifts fraud liability to the issuer on authenticated e-commerce orders and is switched on per business unit, where the fraud exposure justifies the extra step.
Our dispute team assembles evidence from the unit that made the sale — signed receipts, delivery records, call logs, invoices — with cases typically resolving within 45 days.
For an enterprise, multiple MIDs are structural: each entity and channel has its own, so a dispute spike in one unit stays there, and a second acquirer can stand behind critical checkouts.
Dynamic descriptors show the brand and location the cardholder dealt with instead of the parent company's legal name, a common cause of unrecognised-charge disputes.
"We had nine subsidiaries on one processor login and a spreadsheet to work out whose money was whose. Now each entity has its own MID and its own deposits, and month-end close for payments takes an afternoon."
"I expected the vault migration to be the part that went wrong. They told us up front it would take weeks and that security codes would not come across, and that is exactly what happened."
"Procurement sent a long security questionnaire and got written answers from a person with a name. That alone put them ahead of the two larger providers we were comparing."
An enterprise merchant account is a dedicated payment-processing relationship that acquiring banks issue to an organisation made up of several legal entities, business units or brands, structured as a hierarchy of MIDs that follows the corporate structure, priced on interchange-plus, and built to meet the settlement-reporting, PCI DSS, procurement and multi-channel requirements that a single pooled account cannot.
The account permits card-present, e-commerce, mail and telephone order, invoiced and recurring transactions across every entity in the group, settles each MID to the bank account of the entity that made the sale, and operates under underwriting terms that include entity-level reporting, role-based access, tokenisation and point-to-point encryption, Level 2 and Level 3 data for commercial cards, multi-currency settlement, Ethoca and Verifi alerts, account updater, and discount rates from 2.89% or interchange plus a fixed disclosed markup.
An enterprise is not usually high risk because of what it sells. It is awkward for an aggregator because of how it is organised. A pooled platform models one merchant with one balance; an enterprise is many merchants that happen to share an owner. When subsidiaries are run as labels on one account, the card networks' expectation that the merchant of record is the entity making the sale is blurred, a dispute problem in one unit shows up against all of them, and finance has no clean way to say which deposits belong to which ledger. Enterprises also bring requirements a self-service platform is not built to answer: a vendor-risk questionnaire, a PCI assessor's scoping questions, a treasury team that needs funding on a known schedule, and stored cards that must move from the previous provider without asking customers to re-enter them. Acquirers underwriting an enterprise weigh the ownership structure and financial statements of the parent, the volume and vertical of each entity, the mix of card-present, online and keyed transactions, existing processing history per MID, and how card data is handled across the estate.
Opening an enterprise merchant account differs from opening a single-business account in three ways. First, underwriting is done on the group and on each entity: ownership documents and financials are reviewed once at the parent, then each legal entity signs its own agreement and receives its own MID, so adding the next subsidiary is an addition to an existing file. Second, the deliverable is a structure and not just an account — a MID tree, a settlement and reporting design agreed with finance, and a card-data design agreed with security. Third, the timetable is honest about dependencies: the underwriting decision takes 48 hours, but security review, contract review and a token vault migration are driven by your own teams and your outgoing processor, and a full rollout is usually measured in weeks.
2Accept underwrites enterprise merchant accounts for holding companies and their subsidiaries, multi-brand retail and hospitality groups, private-equity portfolio companies, multi-location healthcare and service organisations, manufacturers and distributors, and membership and subscription businesses across the United States. Applications are reviewed by a dedicated underwriter within one business hour and decided within 48 hours depending on documentation, then boarded entity by entity via gateway, REST API, virtual terminal or card-present terminal after each entity signs its merchant processing agreement.
Acquiring banks look at an enterprise by its ownership structure, the number of selling entities and the channels each one uses. The groups 2Accept underwrites most often are:
A dedicated enterprise merchant account gives a multi-entity organisation advantages a pooled aggregator account cannot, because the account structure is drawn from the corporate structure instead of being forced into a single login:
Qualifying for an enterprise merchant account means documenting the parent and each selling entity to the standard an acquiring bank reviews during underwriting. Standard qualification criteria include:
Keeping an enterprise merchant account healthy is mostly a matter of governance: acquirers re-review MIDs on a rolling basis and the card networks monitor each one separately, so a weakness in one business unit has to be seen and fixed at that unit before it becomes a group problem. The strategies that keep an enterprise MID hierarchy in good order are:
No. Accounts are month-to-month with no early-termination fee. Each legal entity signs its own merchant processing agreement on the same terms.
An organisation chart of every entity that will accept cards, formation documents and EINs for each, beneficial-ownership details, recent financial statements for the parent, three months of processing statements per existing MID, and ID for each authorised signer.
The underwriting decision arrives within 48 hours of a complete application. Going live across a group takes longer: security review, contract review and a vault migration depend on your teams and your outgoing processor, and usually run for several weeks.
Each legal entity signs its own agreement and gets its own MID, but the group is underwritten once. Ownership documents and financials are reviewed at the parent, then entities are added to that file.
Yes, and most groups do. A pilot entity or a single channel goes live first, and further MIDs are added to the same underwritten file as each unit is ready.
The initial review is a soft check with no credit pull, and for an established company the financial statements carry the file. Any hard pull is disclosed before it happens.
A named account team led by the underwriter on your file. Security questionnaires, fee schedules and contract questions are answered in writing by those people, not by a ticket queue.
No. The application and underwriting review are free.
Low-risk business units start at 2.89% + $0.20, and above roughly $250,000 a month interchange-plus is standard: network interchange passed through plus a fixed markup set out in a written fee schedule.
Both. The markup is quoted with the group's combined volume in view, so smaller entities benefit from the parent's scale. The risk tier, though, is set entity by entity: a subsidiary in a regulated or high-dispute vertical prices at its own tier and does not move the others.
Corporate and purchasing cards carry higher interchange. Sending Level 2 and Level 3 data — tax, purchase order and line-item detail — can qualify those transactions for lower commercial categories than the same sale sent without it.
No. Size earns interchange-plus and a keener markup, but the vertical sets the tier. A large company selling a product acquirers treat as high risk still prices at that product's tier.
Interchange, network assessments and our markup appear as separate lines per MID, so finance can see what the card networks charged and what the processor charged, entity by entity.
Where the acquiring bank supports it, yes. Monthly billing means each deposit matches the day's batch total, which makes reconciliation simpler. It is agreed per entity at onboarding, not assumed.
Funding is typically next-day to each entity's own bank account, on a schedule agreed with your treasury team at onboarding.
A per-dispute fee, commonly $15–$25, is disclosed in the fee schedule and charged to the MID that received the dispute, so the cost lands on the right entity.
Card-network rules expect the merchant of record to be the entity that sold to the cardholder. Running several companies through one account blurs that, mixes their funds, and pools their disputes into one ratio.
At least one per legal entity that sells, then more where a brand, channel or vertical needs its own descriptor, pricing or MCC. The underwriter proposes the tree from your organisation chart.
They can, but separate MIDs or dynamic descriptors usually serve better: customers recognise the brand on their statement, and reporting splits by brand without manual work.
The new entity is added to the existing file with its own formation documents, bank account and agreement. If it has stored cards elsewhere, a vault migration is scheduled alongside.
Its MID is closed or, on a sale, the buyer opens an account in its own name. A merchant account does not transfer with the business, because the underwriting was of the previous owner.
Not as part of the corporate hierarchy. Franchisees are independently owned businesses, so each needs a MID in its own legal name and its chargebacks must not sit on your account. We run that as a franchise programme alongside the enterprise structure; the two share an account team but not liability.
Yes. That unit is underwritten at its own tier, often with a different acquiring bank, and its dispute ratio is kept apart from the group's low-risk MIDs.
Our core placements are for U.S. entities. Multi-currency settlement is available for cross-border sales, and foreign subsidiaries are reviewed case by case; some are better served by an acquirer in their own country.
They are designed to. Each deposit comes with the batches, transactions, fees and adjustments inside it, tagged to the MID, and your team maps that layout once to the ledger. We do not claim a pre-built connector to any named ERP; the route is a scheduled file or the gateway API.
Yes. Each MID settles to a business account in that entity's legal name, which keeps intercompany balances out of the payments process altogether.
Visa and Mastercard set Level 1 at more than six million of their transactions a year, validated by an annual Report on Compliance. Your acquirer confirms your level, and below it most entities validate by self-assessment questionnaire.
Tokens replace card numbers in your own systems, and validated P2PE terminals encrypt at the point of read, so fewer servers and networks handle card data and fewer fall inside the assessment.
Yes, in writing, and we gather the PCI Attestations of Compliance for the gateway and processing platforms proposed, so your reviewers see the providers' own evidence.
We will not invent one. 2Accept is not the bank or the gateway; uptime commitments come from those providers, and we put theirs in front of you during review.
Yes. Reporting and refund permissions follow the MID hierarchy, so staff see only the entities they are responsible for.
Multi-currency settlement is available for units with cross-border sales, on a schedule agreed at onboarding.
Yes. Your current processor exports card numbers and expiry dates in encrypted form directly to the new PCI DSS Level 1 vault, which issues new tokens and a mapping file. Customers are not contacted and recurring billing continues.
Security codes, because nobody is permitted to store them, and usually network tokens, which are re-provisioned by the new provider. Card numbers, expiry dates and your customer references do move.
Commonly several weeks, and the outgoing processor sets most of the pace. We schedule cut-over for vaulted cards after the import is verified, and new sales can start on the new MIDs before then.
Established processors have an export process for this, though some are slow and some charge. Check your current contract for data-portability terms.
Yes. A phased cut-over, one entity or channel at a time, is the normal approach.
Agents send a payment link or the caller uses a hosted form, so card numbers are not spoken into recordings or typed into your CRM.
Yes, where the channels share a vault. A card stored at web checkout can be billed for a telephone order or an invoice, within the consent the cardholder gave when it was stored.
NMI or Authorize.net gateways, a REST API with hosted fields, hosted payment pages, virtual terminal, invoicing and payment links, card-present terminals and e-commerce plugins.
Stripe and Square place every business on a pooled platform account with a standard agreement. 2Accept gives each of your legal entities a dedicated MID, entity-level settlement and a named team that answers procurement in writing.
Sometimes, yes. A global group processing billions with its own payments engineering team may be better served by a direct contract with a large acquirer. 2Accept fits organisations that want that structure without building the team to run it.
A bank offers one acquirer and its standard risk appetite, which is fine until one business unit falls outside it. 2Accept places entities across more than 40 acquiring banks, so a regulated or higher-risk subsidiary can be boarded without moving the rest of the group.
Often, yes. If it is NMI, Authorize.net or another gateway the acquirer supports, new MIDs can sit behind it and the vault may not need to move at all.
If the challenge is one store's scale — flat-rate cost, growth reserves, failover — our high-volume e-commerce account covers that in depth. This page is for groups whose difficulty is the number of entities, channels and internal stakeholders.
Yes. Critical checkouts can sit on MIDs at two acquiring banks with gateway routing between them, so an outage at one does not stop sales.
Rarely. U.S. entities are placed domestically. Offshore acquiring is used only where a unit's vertical or customer base calls for it.
Month-to-month is our standard and suits most buyers. If your policy requires a defined term or rate protection in writing, raise it with your account team during contract review.
Send us your organisation chart and a recent statement from each processor you use today, and we'll come back with a proposed MID hierarchy and an interchange-plus quote. The review is free, there's no application fee, and the underwriting decision takes 48 hours.
Start Your ApplicationEnterprise groups are rarely one kind of business. A retail parent owns an e-commerce subsidiary with its own growth curve, a services group sells software on subscription, a brand expands through franchised locations it does not own, a distribution arm invoices other businesses on commercial cards, and a healthcare division carries its own compliance file. Each of those underwrites on a different basis even when they roll up to one balance sheet. 2Accept underwrites these adjacent categories under the same acquiring relationships, so a group can add a MID for a new business unit without restarting underwriting from scratch.
If your group operates across several verticals — say, a retail parent, an e-commerce subsidiary, a subscription software unit and a distribution arm invoicing other businesses — 2Accept structures a separate MID for each legal entity under one master underwriting relationship. Each MID settles to its own entity's bank account, carries its own descriptor and tier, and is monitored independently, so a dispute spike in one business unit does not threaten the others.
Apply now and let's build your business — without hesitation.
SPEAK TO A PAYMENT EXPERT