Opening a CRM software merchant account through 2Accept covers both sides of a CRM vendor's payment problem: a dedicated MID for the subscriptions and seats you bill yourself, and a partner route that lets your customers invoice and collect inside your product, each on a dedicated MID of its own that we underwrite, so you add payments to the CRM without registering as a payment facilitator or standing behind your customers' chargebacks. Our CRM software merchant accounts include horizontal sales CRMs, vertical CRMs for real estate, automotive, home services and healthcare, white-label agency CRMs, and field-service and practice platforms built on a CRM core under a single underwriting relationship.
The process of opening a CRM software merchant account with 2Accept takes four steps. First, complete the online application with your EIN, Articles of Incorporation, three months of bank and processing statements, your subscriber count and plan mix, and, if you intend to embed payments, the verticals your customers work in, their typical invoice sizes, how they take payment today, and which gateway your product integrates or plans to. Second, a dedicated underwriter reviews your own billing and the profile of the customer base you want to board within one business hour, and tells you which embedded-payments model fits. Third, you receive a dedicated MID for your subscription revenue and integrate an NMI or Authorize.net gateway, or the REST API with hosted fields, once in your product after signing the merchant processing agreement. Fourth, you go live in 48 hours, and each customer you refer is underwritten on its own MID on the same timeline.
Rates for a CRM software merchant account on 2Accept start at 2.89% + $0.20 for the vendor's own subscription billing, with interchange-plus pricing standard above roughly $250,000 a month. Your customers are priced on their own accounts by their own vertical: a real estate brokerage, a car dealership and a medical practice do not share a tier because they share a CRM. Pricing depends on monthly volume, average ticket, card mix, chargeback history, and how each business takes payment.
A CRM vendor weighing payments is making a structural decision, not choosing a rate: who is the merchant, who verifies each customer, who is liable when one of them goes wrong, and how much of that work the vendor wants on its own balance sheet. 2Accept covers each of those questions below and underwrites the vendor types, payment models and customer verticals listed here.
2Accept underwrites the companies that build and sell CRM software: horizontal sales and pipeline CRMs, vertical CRMs written for one industry, white-label CRMs that agencies resell under their own brand, and field-service or practice-management platforms where the CRM is the core and scheduling, quoting and invoicing sit around it. The vendor's own account covers what it bills its subscribers. The larger question is what happens when those subscribers want to charge their own customers from inside the product.
That second question changes the file. A vendor billing 2,000 subscribers is one merchant. A vendor whose 2,000 subscribers each take card payments is the front door to 2,000 merchants, in whatever trades they happen to be in. The underwriter needs to know which verticals those are, what their tickets look like, and what role the vendor wants to play.
Apply for a CRM Vendor MID →There are three ways to put payments inside a CRM. A registered payment facilitator is sponsored by an acquiring bank and registered with the card networks through it; it signs sub-merchants under its own master account and is liable for what they do. Payfac-as-a-service rents that infrastructure from a provider already registered, with the liability split set by contract. In a partner or referral model the vendor integrates a gateway, and each customer gets its own merchant account from an acquirer or ISO.
Registration is a heavy undertaking: sub-merchant underwriting, sanctions screening, transaction monitoring, funding and reconciliation, dispute handling, PCI DSS validation as a service provider, and the staff to run them. For most CRM vendors the partner model is the right answer, and it is the one 2Accept provides. You integrate once, your customers are boarded on dedicated MIDs, and payments stay a feature of your product, not a second regulated business inside it.
Apply for an Embedded Payments Review →Whoever boards a business to accept cards has to know who it is. That means verifying the legal entity and its beneficial owners, screening them against sanctions lists and the card networks' terminated-merchant file, checking that the business does what it says it does, and confirming the bank account. A payment facilitator carries those duties for every sub-merchant. In the partner model they sit with the acquirer and with 2Accept, and your product supplies the application link.
In practice your customer clicks through from the CRM to a 2Accept application carrying the business details you already hold, an underwriter reviews it within one business hour, and an approved account is live in 48 hours with gateway credentials your product stores. That is not the instant activation an aggregator offers, and we would not claim it is. It is an account sized to that business's real ticket and volume.
Apply for Customer Onboarding →Payments revenue and payments risk travel together. A registered payfac keeps the most margin on each transaction and absorbs the loss when a sub-merchant takes deposits and disappears. A payfac-as-a-service contract pays a share and, depending on its terms, can leave the platform responsible for sub-merchant losses and negative balances; read that clause before the revenue table. A referral partner earns the smallest share and carries none of the merchant credit risk.
With 2Accept the credit risk on each customer account sits on the acquiring side, not with the software vendor. Partner terms, including any revenue share on accounts you refer, are set out in a written partner agreement before you build anything. One limit to plan around: because each customer is the merchant on its own MID, you cannot skim a platform fee off each transaction at settlement the way a payfac split does.
Apply for Partner Terms →A vertical CRM inherits the payment habits of its vertical. Home-services customers take a deposit on an accepted estimate, progress payments on larger jobs and a final payment on site. Dealerships take deposits to hold a vehicle, down payments and service tickets, often keyed or paid by link. Healthcare practices collect patient balances after insurance and keep a card on file with consent. Real estate teams bill desk, marketing and coordination fees, while earnest money is escrow money under state trust-account rules.
One flat-rate pooled account treats all four the same, which is why a contractor's first $18,000 deposit or a dealership's run of large keyed tickets ends in a hold. 2Accept places each customer by trade, with ticket sizes agreed at approval, card-present terminals where the work is on site, and HSA and FSA cards accepted for practices under a healthcare merchant category.
Apply for a Vertical CRM Program →Your own revenue is a software subscription, and it needs what any subscription book needs: account updater so reissued and expired cards on file keep billing, network tokens in place of stored card numbers, retries that follow the decline reason, and merchant-initiated transactions flagged correctly for seat additions and plan changes. Annual plans are underwritten at approval so a prepay discount does not surprise anyone.
Keep this account separate from customer payments. Your subscription MID carries your descriptor and your dispute ratio, and nothing your customers process touches it. If you bill through Chargebee, Recurly or your own code, the MID connects through an NMI or Authorize.net gateway that the billing system supports, or through the REST API with hosted fields.
Apply for a Subscription MID →Pricing follows risk tier, and each business's own vertical sets its tier. A CRM vendor's own subscription billing underwrites at the low tier, with interchange-plus standard above roughly $250,000 a month. Customers boarded through your product are priced individually, so a home-services contractor and a healthcare practice each get terms that match their own business, not a single blended platform rate. 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 subscription billing, your customers' verticals and ticket sizes, and the payments model you want within 1 business hour.
Sign your MPA, receive your own MID, and integrate NMI, Authorize.net, or the REST API with hosted fields into the CRM one time.
Send customers an application link from inside the CRM; each is underwritten on a dedicated MID and collects payments in your product.
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.
Aggregator platform products make it quick to switch on payments inside software, and for many early-stage products that is the right first step. The trade-off is that your customers are onboarded by an automated model, priced at one flat rate whatever their trade, and held or closed by a risk team neither you nor they can reach. With 2Accept each customer has a dedicated MID, underwritten by a person who knows the vertical, placed at a bank that wants that business.
| Feature | 2Accept | Stripe | Square | PayPal |
|---|---|---|---|---|
| Each of your customers boarded on its own MID | ✓ | ✕ | ✕ | ✕ |
| Customer files underwritten by vertical, by a person | ✓ | ✕ | ✕ | ✕ |
| Placement across 40+ acquiring banks by trade | ✓ | ✕ | ✕ | ✕ |
| Gateway integration portable between acquirers | ✓ | ✕ | ✕ | ✕ |
| Interchange-plus pricing for your larger customers | ✓ | ✕ | ✕ | ✕ |
| Dedicated MID (not aggregator pool) | ✓ | ✕ | ✕ | ✕ |
| Human underwriter (not chatbot) | ✓ | ✕ | ✕ | ✕ |
Every MID 2Accept opens for a CRM vendor or its customers carries the same monitoring and mitigation stack, tuned to the trade behind it, so a dispute problem at one customer is found early and stays on that customer's account.
Ethoca and Verifi alerts are enabled per customer MID, so a contractor or practice can refund a questioned invoice before it posts as a chargeback on its account.
Rules are set for the trade, not the platform: velocity and AVS checks on a dealership's keyed deposits differ from those on a clinic's card-on-file patient balances.
3-D Secure 2 can be applied to large payment-link and invoice payments, shifting fraud liability to the issuer on the authenticated high-ticket payments your customers send.
Our dispute team builds each case from the records your CRM already holds, such as the signed estimate, invoice history and customer messages, typically resolving within 45 days.
Your larger customers can hold 2–5 MIDs for separate locations or business lines, and your own subscription volume stays on an account none of them touch.
Each customer's descriptor carries its own trading name and phone number, never the CRM's brand, so a homeowner or patient recognises the business they paid.
"We spent two months costing out payfac registration before someone told us plainly that we did not need it. Our contractors are on their own accounts now and we went back to building product."
"Our dealers kept getting held on large deposits with the old embedded option, and the complaints came to our support desk. Individually underwritten accounts ended most of those tickets."
"What sold us was the liability answer. With the platform product we had been quoted, a customer's bad month was contractually our loss. Here each practice is the merchant on its own account."
A CRM software merchant account is a dedicated payment-processing relationship that an acquiring bank issues to a company selling customer-relationship software, covering the vendor's own subscription and seat billing and, where the vendor embeds payments, extended through a partner arrangement in which each of the vendor's customers is underwritten on a merchant account of its own instead of as a sub-merchant under the vendor.
The vendor's account permits card-not-present subscription billing with stored credentials, account updater, network tokenization and decline-aware retries, at discount rates from 2.89% + $0.20 or interchange plus a fixed disclosed markup at volume. The partner arrangement adds a single gateway integration through NMI, Authorize.net or the REST API with hosted fields, an application path your customers reach from inside the CRM, and for each approved customer a dedicated MID with its own pricing, descriptor, funding, Ethoca and Verifi alerts, and card-present terminals where the trade needs them.
Embedding payments turns a software company into part of the payments chain, and the card networks care which part. A payment facilitator is a registered role: an acquiring bank sponsors it, the networks list it, and it becomes responsible for underwriting, monitoring and funding its sub-merchants and for their losses. The networks also limit how large a sub-merchant can grow before it must contract with the acquirer directly. Payfac-as-a-service providers shorten the path by lending a registered platform, but the contract decides who pays when a sub-merchant fails, and it is often the software vendor. Aggregator platform products add a further issue for vertical CRMs: one automated model and one flat rate applied to dealerships, clinics, contractors and brokerages alike, with holds on exactly the large tickets those trades depend on. Acquirers reviewing a CRM vendor therefore ask what verticals its customers are in and who the vendor intends to be in the transaction.
Opening a CRM software merchant account differs from adopting an aggregator's platform product in three ways. First, the merchant on every transaction is your customer, on an account in its own name, so its chargebacks, reserves and funding are its own and not a liability on your books. Second, each customer is underwritten by a person for its actual trade, which is what lets a contractor take a five-figure deposit or a dealership key a large down payment without a hold. Third, your integration is to a gateway, not to a single processor, so accounts can be placed across different acquiring banks, or moved, without rewriting the payments code in your product.
2Accept underwrites CRM software merchant accounts for horizontal sales CRMs, vertical CRMs serving real estate, automotive, home services and healthcare, white-label agency CRMs, and field-service and practice platforms across the United States. Applications are reviewed by a dedicated underwriter within one business hour and are typically live in 48 hours depending on documentation, for the vendor and for each customer referred, then connected through NMI, Authorize.net or the REST API after signing the merchant processing agreement.
Acquiring banks look at a CRM vendor's own billing first and at the trades of its customers second. The CRM businesses 2Accept underwrites most often are:
A CRM software merchant account built on dedicated MIDs gives a vendor the product benefit of embedded payments without the regulatory weight of facilitating them, because the acquirer and 2Accept do the underwriting and each customer stands on its own account:
Qualifying means documenting your own business in the usual way and, if you plan to embed payments, describing the customer base you will refer so the acquiring bank knows what is coming. Standard qualification criteria include:
Embedded payments stay healthy when the vendor treats them as a product with support, data and reporting duties, and leaves underwriting and risk to the parties that carry them. Acquirers review each customer's MID on a rolling basis, and the practices below keep those reviews uneventful for you and for the businesses on your platform:
No. The vendor's merchant account is month-to-month with no early-termination fee, and so is each customer's.
EIN and formation documents, three months of bank and processing statements, your plan mix, and ID for each principal. If you plan embedded payments, add your customers' verticals, typical invoice sizes and your gateway integration plan.
Yes, and many vendors do. The subscription MID is approved on your own business. Embedded payments are reviewed when you are ready, using what we already know about you.
Yes. Each is the merchant on its own account, so each completes an application and is underwritten. Pre-filled details from the CRM keep it short.
For your own billing, a live product with pricing is enough. For embedded payments we can review the design before it ships.
It is one input among several. The business model, statements and dispute history weigh more for a software vendor.
A gateway integration with hosted fields is usually days to a few weeks of engineering, depending on how invoicing already works in your product.
No. There is no application fee for you or your customers.
Subscription software underwrites at the low tier, from 2.89% + $0.20. Above roughly $250,000 a month interchange-plus is standard, with the markup fixed in writing.
Individually, by their own vertical, volume and history. A general contractor, a dealership and a medical practice will not receive identical terms, and that is deliberate: a single blended platform rate overcharges your low-risk customers to cover the others. Each customer sees its pricing before signing.
Not as a guarantee. We can agree a standard starting schedule for a vertical you serve, but every file is still underwritten and an individual customer's terms can differ.
Partner terms, including any revenue share, are agreed in a written partner agreement. Ask your underwriter for them before you scope the integration.
Not at settlement. Each customer is the merchant on its own MID and is funded directly, so there is no payfac-style split. Vendors charge for payments features through their own subscription pricing.
Only where underwriting requires one, at 0–10%, set on that customer's account alone. Deposit-heavy trades with long lead times are the usual case. Nothing is held on your account for it.
Next-day funding is typical, paid directly to each customer's bank account.
Commonly $15–$25 per dispute, stated in each customer's own agreement. It is not charged to the CRM vendor.
A company registered with the card networks through a sponsoring acquirer to process for sub-merchants under its own master account. It onboards, monitors and funds them, and is liable for their activity.
A sponsor bank agreement, network registration, sub-merchant underwriting and monitoring programmes, PCI DSS validation as a service provider, funding operations and dedicated staff.
A registered provider's platform that you build on. You get onboarding APIs and a fee share; the contract decides who bears losses.
Your software integrates a gateway and refers customers, and each one gets its own merchant account from an acquirer or ISO, which carries the underwriting and risk.
The partner model. Full registration only pays back at very large payment volume with staff to match, and most vendors want payments as a feature, not a second business.
When activation must be instant and fully self-serve. If you expect thousands of very small merchants who sign up, take a first payment within minutes and never speak to anyone, a payfac-as-a-service platform fits that pattern better than individual underwriting does, and we will tell you so.
In the partner model your company does not hold or move customer funds. Structures where a platform does can raise state licensing questions, which are for your counsel to answer.
Yes. Because your integration is to a gateway and your customers hold their own accounts, nothing about starting here prevents a different structure once volume justifies it.
Verification of the business and its owners, sanctions and terminated-merchant screening, a review of what the business sells and how it takes payment, and confirmation of the bank account. It is the same review any merchant account requires.
An underwriter reviews a complete application within one business hour and approved accounts are typically live in 48 hours. It is not instant, and it is not automated.
The customer, on its own merchant account. If it cannot pay, the loss is dealt with on the acquiring side under that merchant agreement, not passed to the CRM vendor.
About 98% of complete, compliant applications are approved. A decline is explained to the customer directly, and it does not affect your account or other customers.
Funding, disputes and account questions come to 2Accept. Questions about invoices and how payments appear in the CRM stay with your support team.
It should not. Hosted fields or a hosted payment page send card numbers straight to the gateway and return a token.
No. Transaction monitoring sits with the acquirer and 2Accept.
Often, if it runs on a gateway your product integrates. Otherwise they can open a new MID with us and keep the old one.
Usually a deposit when an estimate is accepted, progress payments on longer jobs, and a final payment on site by terminal or payment link. Deposit size and lead time are what underwriting looks at.
Ticket size. Vehicle deposits and down payments are large and often keyed, and deposit disputes follow deals that fall through. Limits and refund terms are agreed at approval.
Treat those separately. Funds held for a client fall under state trust-account rules and many acquirers will not take them on card. Fees a brokerage or agent charges for its own services are ordinary card volume.
Practices need consent for cards on file, and payment data should be kept apart from clinical records. Check HIPAA questions with compliance counsel.
Generally yes for practices boarded under a healthcare merchant category.
Surcharging is governed by card-brand rules and state law and is not permitted everywhere. A customer should confirm its own position first.
Yes. Multi-location businesses commonly hold a MID per location or entity so funding, reporting and dispute ratios stay separate, and your product stores credentials for each.
Yes, at the tier that vertical prices at. Tell us which trades are on your platform and we will say which are routine, which carry a reserve, and which a bank is unlikely to take.
A platform product gives instant onboarding and transaction-level fee splits on a pooled model with flat pricing. 2Accept gives each customer an underwritten dedicated MID, priced by trade, with no platform liability.
For a young product with many small, low-ticket, low-risk merchants and a need for instant sign-up, it is hard to beat, and it earns you a per-transaction fee. The case for dedicated MIDs grows with ticket size and with how often your customers are held.
Yes, and it is a sensible design. Some vendors keep an instant aggregator option for the smallest customers and offer a dedicated MID to those with larger tickets, a trade the aggregator restricts, or a history of holds. Your gateway abstraction decides how much work that is, so plan for two providers early.
Several do, usually as a payfac or on a payfac-as-a-service platform. They reached that at very large scale.
You can, if you integrate several gateways. The cost is support: every processor behaves differently and the questions come to your team. Vendors usually pick one or two gateways and a partner who boards accounts behind them.
No. They are gateways. The merchant accounts behind them are what 2Accept provides, for you and for each customer.
If that account works with a gateway your CRM supports, usually yes. If not, a 2Accept MID behind your gateway is the simpler route.
Rarely for its own billing. Offshore acquiring is used for customers whose vertical or location needs it, decided file by file in underwriting.
Tell us which verticals your customers work in and how they take payment today, and we'll show you which embedded-payments model fits and what your customers would be approved for. There's no application fee, and an underwriter responds within one business hour.
Start Your ApplicationA CRM is rarely only a CRM for long. The vendor's own revenue is a SaaS subscription, the agencies that resell it white-label run retainers of their own, the studios that implement it bill projects and care plans, and the larger customers on the platform need enterprise terms with several MIDs and interchange-plus pricing. Each of those underwrites on its own basis. 2Accept underwrites these adjacent categories under the same acquiring relationships, so a vendor, its partners and its customers can all be placed without restarting underwriting each time.
If your company runs more than one product or entity, for example a core CRM subscription, a separately branded vertical edition, and a services arm that bills implementation projects, 2Accept can structure a separate MID for each under one underwriting relationship. Your customers' accounts sit apart from all of them, each monitored on its own, so a dispute spike at one dealership or practice affects neither your subscription billing nor the other businesses on your platform.
Apply now and let's build your business — without hesitation.
SPEAK TO A PAYMENT EXPERT