Opening a web design merchant account through 2Accept fits the way a studio is actually paid, a deposit to start, milestones along the way and a final invoice at launch, by boarding you on a dedicated MID where your largest invoice is agreed at approval instead of held for review when it arrives, putting hosting and care-plan retainers on recurring billing with account updater behind them, and giving you a dispute team that knows a signed scope and an approval email are the evidence that matters. Our web design merchant accounts include freelance designers and developers, small studios, full-service web agencies, e-commerce build specialists, white-label production shops, and hosting and maintenance providers under a single underwriting relationship.
The process of opening a web design merchant account with 2Accept takes four steps. First, complete the online application with your EIN and formation documents, or your DBA registration if you work as a sole proprietor, three months of bank statements and any processing statements, your typical and largest project invoice, your deposit and milestone schedule, how many clients are on monthly hosting or care plans, a sample proposal or contract, and your current chargeback and refund history. Second, a dedicated underwriter reviews your ticket sizes, payment schedule, project length, recurring revenue and dispute history within one business hour. Third, you receive a dedicated MID and start invoicing through payment links, a virtual terminal, a hosted payment page, or an NMI or Authorize.net gateway that your invoicing software supports, after signing the merchant processing agreement. Fourth, you go live in 48 hours with recurring billing, account updater, chargeback alerts and agreed ticket limits already configured.
Rates for a web design merchant account on 2Accept start at 2.89% + $0.20, with interchange-plus pricing standard above roughly $250,000 a month. Pricing depends on monthly volume, average and largest invoice, the split between project work and recurring retainers, how far ahead of delivery deposits are taken, the share of corporate cards, and chargeback history. A studio that takes half up front on a four-month build is underwritten differently from one that bills on completion, and both can be approved.
A web studio judges a processor on a handful of moments: the day a $12,000 deposit lands, the month a build runs late and the client goes quiet, the renewal run for forty care plans, and the afternoon a client who has the finished site disputes the final invoice. 2Accept covers each of those below and underwrites the studio types, billing schedules and service models listed here.
2Accept underwrites web work at every size: solo designers and developers, studios of three to fifteen people, full-service web agencies, specialists in e-commerce builds on platforms such as Shopify and WooCommerce, production shops that build under other agencies' brands, and providers whose revenue is mostly hosting and maintenance. Tickets run from a few hundred dollars for a small fix to tens of thousands for a store or a custom application, and most of it is invoiced, not sold through a checkout.
What the underwriter wants to understand is the gap between payment and delivery. A logo refresh paid on completion has none. A five-month rebuild with half paid on signing has a long one, and that is where disputes come from. A sample contract and an honest account of how long your projects really take answer most of the file.
Apply for a Web Design MID →Most studios bill in stages, commonly a deposit on signing, one or two payments at design approval and development hand-off, and the balance at launch. To an acquirer each stage is a payment for work not yet finished, and the deposit is the most exposed because the dispute window can run from when the service was due, not from the day the card was charged. A deposit taken in February on a build that stalls in June is still open to dispute.
2Accept underwrites the schedule itself. Your deposit percentage, milestone points and typical project length are recorded at approval, each stage is invoiced by payment link or virtual terminal against the same client record, and the account's ticket limit is set above your largest stage payment. Tying every charge to a named milestone in the contract is what makes it defensible later.
Apply for Milestone Billing →A web project dispute rarely says the client did not pay for a website. It says the site is not what was promised, or was never finished, usually after scope grew through emails and calls nobody wrote up. The difficulty is that the client keeps the deliverable: the site is live on their domain while the bank decides whether you keep the fee. There is nothing to return, so the case is won or lost on paper.
The paper that wins is specific. A signed scope listing pages, features and revision rounds. Change orders for anything added. An approval at each milestone, even a one-line email. The launch date, and evidence the client has used the site since. Our dispute team assembles those into the response. No one can promise the issuer's decision, but a studio with sign-offs wins disputes that a studio with a handshake cannot contest.
Apply for Dispute Defense →Recurring revenue is what steadies a studio between projects: hosting, maintenance and care plans, support blocks and SEO upkeep billed to a card on file each month. These charges are small and long-lived, and the client's card will expire or be reissued long before the relationship ends. For a hosting provider a failed charge is more than a missed payment; an automated suspension can take a client's site offline over an expired card.
The MID includes recurring billing with account updater and network tokenization, so stored cards are refreshed before the renewal runs, and declined charges are retried before anything is suspended. Hosting providers using billing software such as WHMCS connect the account through a gateway that software supports. A descriptor that names your studio and the word hosting keeps a new bookkeeper at the client from disputing a charge they do not recognise.
Apply for a Retainer Billing MID →Small web businesses have lumpy revenue. Three quiet weeks, then two deposits and a final payment in four days. An aggregator's risk model is built on consistency, and a sudden large payment into an account that normally sees small ones is exactly what it is designed to stop. The result is familiar to most freelancers: funds paused, a request for the contract and invoice, and a wait of days or weeks while your own bills fall due.
A dedicated MID replaces the guess with an agreement. Your largest expected invoice and a realistic monthly ceiling are set with the underwriter at approval and can be reviewed with a phone call before a bigger project lands. Funding is typically next-day. One caution: a stranger who offers a large build, pays by card at once and asks you to forward part of it to a third party is running a known scam on designers.
Apply for a Higher Ticket Limit →A good share of web work is sold under someone else's name. A production studio builds for agencies that own the client relationship, an agency subcontracts development and marks it up, and many studios resell hosting, domains, premium themes, plugins and platform subscriptions they have already paid for. When a client disputes a charge that included resold services, the studio loses the fee and is still out the hard cost.
Underwriting separates these lines. Agency-to-studio invoices are business-to-business and low in disputes. Charges to end clients carry the name the client knows. Resold services are itemised on the invoice so a dispute over design does not sweep in a domain renewal. Studios selling pay-monthly websites with no upfront fee get recurring billing and contract terms that state what happens to the site if payments stop.
Apply for a White-Label MID →Every merchant account is priced within a risk tier set by the vertical. Web design and development underwrites at the low tier, with interchange-plus standard above roughly $250,000 a month. Within the tier, terms respond to how much money you hold before work is delivered: long builds with large deposits may carry a modest reserve, while studios with steady retainers and short projects usually do not. 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 invoice sizes, deposit schedule, project length, retainer revenue, and contract within 1 business hour.
Sign your MPA, receive a dedicated MID, and invoice by payment link, virtual terminal, hosted page, or NMI and Authorize.net.
Take deposits, milestones and the final payment within agreed limits, and run hosting and care plans on recurring billing with account updater.
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 suit a designer taking a few small payments a month. They fit less well as invoices grow. A pooled account models you on your history, so a freelancer who normally bills $900 and then charges $14,000 for a build looks like an anomaly, the payout is paused, and a request for documents arrives while the developer you subcontracted is waiting to be paid. A dedicated MID from 2Accept is approved with that invoice size already on file.
| Feature | 2Accept | Stripe | Square | PayPal |
|---|---|---|---|---|
| Largest project invoice approved in advance | ✓ | ✕ | ✕ | ✕ |
| Deposit and milestone schedule underwritten up front | ✓ | ✕ | ✕ | ✕ |
| Dispute team that builds scope and sign-off evidence | ✓ | ✕ | ✕ | ✕ |
| Ticket and monthly limits agreed in writing | ✓ | ✕ | ✕ | ✕ |
| Project and retainer revenue on separate MIDs | ✓ | ✕ | ✕ | ✕ |
| Dedicated MID (not aggregator pool) | ✓ | ✕ | ✕ | ✕ |
| Human underwriter (not chatbot) | ✓ | ✕ | ✕ | ✕ |
Every 2Accept web design merchant account includes the monitoring and dispute tooling a project business needs, built around the fact that your disputes are rarely fraud and almost always a disagreement about scope, timing or sign-off.
Ethoca and Verifi alerts give you a short window to call the client and settle a disputed milestone or a forgotten care-plan charge before it posts as a chargeback.
AVS, CVV and amount checks on payment links catch the stolen-card overpayment scam aimed at designers, where a new client pays at once and asks for money forwarded.
3-D Secure 2 on large invoice links shifts liability for fraud disputes to the issuer. It does not cover a client who claims the site was not what they ordered.
Our dispute team responds with the signed scope, change orders, milestone approvals and proof the site is live and in use, with cases typically resolving within 45 days.
Studios with several service lines can split project invoices and recurring retainers across 2–5 MIDs, so a dispute over one large build does not touch the retainer account.
Descriptors carry the studio name the client hired plus the service, such as hosting or care plan, so a client's finance team recognises a monthly charge years later.
"I sent my biggest invoice ever and PayPal held it for most of a month. I had a contractor to pay out of that deposit. Now the limit is agreed before I send the proposal."
"A client disputed the final payment on a site that had been live for two months. We sent the signed scope and their launch approval email, and the dispute team did the rest."
"Sixty care plans and every month a few cards failed and someone had to chase them. With account updater running that list is nearly empty, and nobody's site goes down over an expiry date."
A web design merchant account is a dedicated payment-processing relationship that an acquiring bank issues to a freelancer, studio or agency that designs and builds websites, set up for invoiced project work paid as a deposit, milestones and a final balance, for monthly hosting and maintenance retainers charged to cards on file, and for the scope and delivery disputes that arise when a client pays in advance for custom work.
The account permits card-not-present payments by invoice, payment link, virtual terminal and hosted payment page, stores cards for recurring hosting, maintenance and care-plan charges, and operates under underwriting terms that include a ticket limit set above your largest stage payment, a monthly volume ceiling agreed in writing, account updater and network tokenization on recurring charges, Level 2 and Level 3 data on corporate-card invoices, Ethoca and Verifi alerts, 3-D Secure 2 on large payment links, and discount rates from 2.89% + $0.20 or interchange plus a fixed disclosed markup at volume.
Web design is ordinary, legitimate business-to-business work, and acquirers treat it as low risk. What they notice is the billing pattern. Revenue arrives as a few large payments instead of many small ones, so one disputed invoice can be a meaningful share of a month. Deposits are taken weeks or months ahead of delivery, which is future-delivery exposure even on a small scale. The product is custom and cannot be returned, so a dissatisfied client's dispute is a judgment about whether the work matched the agreement. Aggregators do not weigh any of that individually. Their models compare each payment with the account's past, which is why freelancers and small studios, whose income is irregular by nature, see large payments paused and documents requested at the moment they most need the cash. An acquirer underwriting a dedicated account looks at the contract, the payment schedule, typical project length, the share of recurring revenue and the dispute record.
Opening a web design merchant account differs from using an aggregator in three ways. First, your invoice sizes are agreed before you send them: the underwriter records your largest expected payment and monthly ceiling at approval, so a five-figure deposit is routine. Second, the account is structured for both halves of a studio's income, with project invoices billed by link or virtual terminal and hosting and care plans on recurring billing with account updater behind them. Third, disputes are handled by people who understand what a web project leaves behind as evidence, namely a signed scope, change orders, approvals and a live site, and who build the response from it.
2Accept underwrites web design merchant accounts for freelance designers and developers, small studios, full-service web agencies, e-commerce build specialists, white-label production shops, and hosting and maintenance providers 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, then used through payment links, a virtual terminal, a hosted payment page, or an NMI or Authorize.net gateway after signing the merchant processing agreement.
Acquiring banks group web businesses by invoice size, how far ahead of delivery they are paid, and how much of their revenue recurs. The web design businesses 2Accept underwrites most often are:
A dedicated web design merchant account gives a studio what a pooled account cannot, because the limits are set around your real invoices by a person who has seen your contract, and the dispute support is built for custom work:
Qualifying for a web design merchant account means showing the acquiring bank what you sell, how you invoice it, and what your contract says when a project changes or stops. Standard qualification criteria include:
A web design merchant account stays healthy when every charge can be traced to something the client agreed to in writing. Acquirers review accounts on a rolling basis, and for a business with few transactions a single dispute moves the ratio a long way, so the paperwork habits below matter more here than in almost any other trade:
No. The account is month-to-month. You can leave at any time and there is no early-termination fee.
Business registration and EIN or tax ID, three months of bank statements, any processing statements, a sample proposal or contract, your typical and largest invoice amounts, and photo ID for the owner or principals.
Yes. You do not need to be incorporated. A sole proprietor with a DBA, a tax ID, a portfolio site and bank statements showing design income is a normal application for us.
Yes. A hold on an unusually large invoice is an outcome of automated modelling, not a mark against you. Bring the invoice and contract with you.
No. Low transaction counts with high tickets are how this trade works, and the account is set up on that basis.
It is considered, not decisive. Your contract, invoicing history and bank statements matter more in a design file.
Send a payment link with each invoice, key a card in the virtual terminal when a client pays by phone, or connect the MID through a gateway your invoicing software supports.
No. There is no application fee.
Web design sits at the low tier, from 2.89% + $0.20 per transaction. Interchange-plus pricing is standard above roughly $250,000 a month and is quoted with a fixed markup.
It depends on your invoices. If you bill a few thousand dollars a month in small payments and have never had a payout held, an aggregator is simple and adequate, and you should keep it. The case for a dedicated MID is large invoices, deposits that fund subcontractors, and a recurring book you cannot afford to have frozen.
Surcharging is controlled by card-brand rules and state law, is not allowed everywhere, and never applies to debit cards. Check your state's position before adding it to an invoice.
Often not. Where one applies it is 0–10% and is set at approval. Long projects with large non-refundable deposits are the usual reason, and a clean history is the usual reason it is removed.
Commercial cards carry higher interchange than consumer debit. On interchange-plus, sending Level 2 or Level 3 invoice data can qualify those payments for lower commercial rates.
Any monthly, gateway or minimum fees are listed in the pricing schedule you receive before signing. Ask for it in writing and compare the total against what you pay now on your real invoice sizes.
Next-day funding is typical, so a deposit is usually available the following business day.
A fee of commonly $15–$25 per dispute, plus the disputed amount if the case is lost. Both are stated in your agreement.
There is no fixed rule. Deposits of a third to a half are common in web work and are underwritten routinely. What matters more is how long the client waits between paying and receiving something.
That is a contract decision for you and your lawyer. From a card perspective, whatever the policy is must be shown to the client and accepted before payment.
Commonly around 120 days, and for services the period can run from the expected delivery date instead of the payment date.
Document it. Emails chasing content and a contract clause covering client delays show that the work was available and the hold-up was not yours.
Yes, with their written agreement to the schedule and amounts. Each stage is then charged against that consent and receipted.
It depends on the tool, so check before you plan around it. The MID connects through NMI or Authorize.net, and software that supports either can use it. Several popular freelancer suites accept cards only through their own processing or an aggregator. In that case you keep the tool for proposals and contracts and send a 2Accept payment link for the money.
You can, but you should not. A payment with no signed scope behind it is the hardest kind to defend, and it gives the client nothing to hold you to either.
Whatever is agreed at approval. Tell the underwriter your largest realistic stage payment and the limit is set above it. For an exceptional project, ask for a review before you invoice.
Yes. Recurring billing runs on stored cards monthly or annually, with the client's written agreement to the amount and frequency. Account updater and network tokens keep the cards current, and declined charges are retried.
Account updater usually supplies the new details before the charge runs. If a charge still fails it is retried, and you can contact the client before any service is suspended.
Hosting businesses commonly bill through software such as WHMCS. The MID connects through a gateway that the software supports; check its current gateway list for NMI or Authorize.net.
Yes. Send a reminder before a yearly charge. Annual renewals that arrive unannounced are the recurring charges clients dispute most.
They can share one. Larger studios often separate them so a disputed build cannot affect the account their recurring revenue depends on.
Cancel the recurring charge the day they ask and confirm it in writing. Charges after a cancellation are disputes you will lose.
Yes, with a contract stating the term and site ownership.
Yes, with notice before the first charge at the new amount, in line with your agreement. An unannounced increase invites a dispute.
Claims that the site was not as described or not finished, deposits disputed after a project stalls, final invoices disputed after launch, and forgotten hosting charges. Card fraud is uncommon in this trade.
A signed scope, change orders for additions, dated client approvals at each milestone, the handover email, and proof the site is live on the client's domain and in use.
It helps to show the work was delivered and is being used, which belongs in the response. It does not decide the case alone; the issuer weighs what was agreed against what was supplied.
Take legal advice first. Your contract's ownership and licence terms govern that, and acting without them can create a larger problem.
Our dispute team files the response, and cases typically resolve within 45 days.
Only from fraud claims, where it shifts liability to the issuer. It has no effect on a dispute about scope or quality.
They tell you a client has questioned a charge before it becomes a chargeback. With a known client that is time to phone them and settle it, often with a credit.
Not by itself. With few transactions a single dispute produces a high ratio for that month, and underwriters read it in that context. A pattern of disputes is what causes concern.
Aggregators are quick to start and suit small, regular payments. 2Accept gives you a dedicated MID with invoice limits agreed in advance, recurring billing for retainers and dispute support built for project work.
Their risk models compare each payment with your account's history. A payment many times your usual size looks like possible fraud or a delivery risk, so funds are paused until you supply documents. It is automatic and says nothing about your work.
For some clients that is sensible, and we would not talk you out of it: transfers cost little and are hard to reverse. Many clients still prefer or require a card for points, cash flow or company policy, and refusing cards slows deposits. Most studios offer both and keep a card option that will not stall on a large amount.
Yes. Some designers keep one for small ad-hoc payments and use the dedicated MID for projects and retainers.
It is usually an aggregator or payfac under another name, with the same pooled risk model. It is convenient, and for small invoices that may be enough. Check whether the app also lets you connect your own gateway.
No. They are gateways that carry the payment. The merchant account behind them is what we open for you.
Usually. Stored cards can generally be transferred between providers, or clients can re-enter a card through a hosted link.
Almost never. U.S. studios are placed with domestic acquirers. Offshore placement exists for business models or locations that need it, which ordinary design work does not.
Send us a sample contract and tell us your largest invoice and how many clients you bill monthly, and we'll tell you what limits and terms you would be approved on. The review is free and you'll hear from an underwriter within one business hour.
Start Your ApplicationWeb studios grow sideways as much as upward. A designer adds SEO and paid-media retainers and becomes a marketing agency, a studio turns its internal site builder into a subscription product, a developer starts implementing CRM systems for clients, and an e-commerce specialist ends up running a client's store on a revenue share. Each of those underwrites on a different basis from project work. 2Accept underwrites these adjacent categories under the same acquiring relationships, so one studio can hold several MIDs across related services without starting again.
If your studio runs several lines of work, for example custom builds invoiced by milestone, a hosting and care-plan book billed monthly, and a separate entity selling a template or plugin online, 2Accept can structure a separate MID for each under one underwriting relationship. Each MID has its own descriptor, limits and dispute ratio, so a disagreement over one large project does not touch the recurring revenue that pays the studio's fixed costs.
Apply now and let's build your business — without hesitation.
SPEAK TO A PAYMENT EXPERT