Why Processors Flag Web Design Agencies and How to Get Approved
Need a web design merchant account? Learn why underwriters flag large upfront payments and what to submit to lower the odds of reserves, caps, and holds.

Photo: Pixabay
On this page 7 sections
- Why a Web Design Merchant Account Is Considered Medium Risk
- Future Delivery Risk and Large Ticket Sizes
- The MCC for Web Design Services and Why It Matters
- Documents That Speed up Underwriting for Web Developers
- Avoiding Reserves and Ticket Limits on Big Projects
- Warning Signs Before a Processor Holds Your Funds
- Next Steps for Your Agency
Key takeaways
- Underwriters treat large deposits for work delivered weeks later as future delivery risk, because unfinished work can turn into chargebacks the processor has to cover.
- Your MCC and business description must match what you actually sell. Accurate coding protects your account, and miscoding can get it terminated.
- Milestone contracts, clear refund terms, and realistic volume and ticket estimates are among the best ways to reduce the chance of reserves and low caps.
- Holds usually follow visible triggers, such as volume spikes, oversized tickets, or rising disputes, so tell your processor before a big project charge.
Applying for a web design merchant account often surprises agency owners. You build websites, not supplements or travel packages, so why does the processor ask for contracts, pause a large deposit, or approve you with a reserve? This guide explains how underwriters judge agency risk, why big upfront project payments draw attention, and how your merchant category code (MCC) shapes your account. It also covers the documents that speed up approval and the warning signs that come before a hold, so you can plan large charges with fewer surprises.
Why a Web Design Merchant Account Is Considered Medium Risk
Is a web design agency high risk? Usually not in the way vape shops or adult sites are. Agencies are often treated as medium risk. The service is legal and well understood, but the way agencies get paid makes underwriters careful:
- Large, irregular tickets. A single redesign deposit can be bigger than a month of maintenance billing.
- Payment before delivery. Clients often pay weeks or months before they see a finished site.
- Card-not-present transactions. Agency payments typically come through online invoices, keyed entries, or stored cards for retainers. Many agencies rarely see a card at a terminal.
- Subjective deliverables. "The site isn't what we wanted" is harder to settle than "the package never arrived."
- Mixed revenue streams. Design, development, hosting resale, SEO, and ad management can all run through one account, and each has its own dispute profile.
None of these will disqualify you on its own. Together, though, they tell the underwriter that losses are possible, and the account terms will reflect that.
Future Delivery Risk and Large Ticket Sizes
Most agency reserves come down to future delivery risk. If a processor puts a reserve on your merchant account, this is usually the reason.
How Underwriters Think About Undelivered Work
When a client pays by card, the acquiring bank behind your processor is ultimately on the hook if that client disputes the charge and your agency can't cover it. If you take a deposit today for a site you'll deliver in ten weeks, the bank carries ten weeks of exposure on that money.
Underwriters add up that exposure across all your open projects. Picture the worst case: the agency closes or stops responding, and every client with unfinished work files a dispute at once. The total of paid-but-undelivered work is what the bank could lose.
Illustrative example: An agency that normally processes a modest amount each month in retainers suddenly charges a deposit several times that size for an e-commerce build. To the risk team, average ticket and monthly volume both jumped overnight, and the work behind the charge won't be finished for months. Automated risk monitoring is built to catch exactly that combination.
Keyed and Recurring Payments Add Their Own Questions
- Keyed transactions. When you type a client's card number into a virtual terminal for phone and invoice payments, you lose the protections of chip or authenticated online checkout. Underwriters watch keyed volume for fraud, especially from new clients.
- Recurring billing. Maintenance and hosting plans are often seen as lower risk because tickets are smaller and service is ongoing. Disputes still rise when clients forget they signed up or can't easily cancel, so clear terms and receipts matter. Our guide to automating monthly retainer billing covers the setup.
The MCC for Web Design Services and Why It Matters
Your processor assigns your account a four-digit merchant category code based on what your business sells. The MCC affects how card issuers classify your charges, which interchange categories can apply, and which risk thresholds your account is monitored against.
There isn't one universal MCC for web design services. Depending on your revenue mix, an agency might be coded under a computer programming and systems design category, an advertising services category, or a broader business services category. Processors decide based on your application, website, and interview. To find out which code you have, check your processing statement or ask your processor.
What matters for you:
- Describe your business accurately. If most of your revenue comes from managing client ad budgets or reselling hosting, say so. A code that doesn't match your real transactions is a compliance problem, not a technicality.
- Never ask to be coded as something else to get better terms or lighter underwriting. Miscoding violates card network rules and can lead to termination. Terminations for rule violations can also lead to placement on the MATCH list, which makes future approvals much harder.
- Tell your processor when your mix changes. If you add a new service line, such as selling software licenses or taking payments on behalf of clients, your original approval may no longer fit.
One more line not to cross: don't process your clients' sales through your agency's merchant account. Running another business's transactions through your account is a serious violation, even as a temporary favor. If you're building a store for a client, read whose merchant account a client checkout should run through before launch.
Documents That Speed up Underwriting for Web Developers
A merchant account for web developers tends to get approved faster when the underwriter can see how you deliver work. Gather these before you apply:
Standard business documents
- Business formation documents and EIN
- Government-issued ID for each owner who meets the processor's ownership threshold
- Business bank account verification, such as a voided check or bank letter
- Recent business bank statements
- Prior processing statements, if you've accepted cards before
Agency-specific documents
- A sample client contract or statement of work showing scope, timeline, and payment schedule
- Your refund and cancellation policy, including what happens to a deposit if the client walks away mid-project
- A typical project timeline from deposit to launch, with average duration
- A revenue breakdown by service line: builds, retainers, hosting, SEO, and ad management
- Realistic estimates of your average ticket, largest expected ticket, and monthly volume
- A live website that clearly describes your services, pricing approach, contact details, and policies
| Underwriter Concern | What Addresses It |
|---|---|
| Large upfront payments | Contract showing milestone billing instead of full prepayment |
| Long delivery windows | Project timeline with defined phases and sign-offs |
| Subjective disputes | Signed scope, change-order process, written approval at each milestone |
| Keyed fraud risk | AVS and CVV checks, plus authenticated online invoices |
| Unclear business model | Revenue breakdown by service and an accurate website |
| Track record | Prior processing statements and bank statements |
Newer agencies often have no processing history, and that's normal. Expect the underwriter to lean more on your contracts and policies, and possibly to start you with more conservative limits.
Avoiding Reserves and Ticket Limits on Big Projects
Processors use a few tools to manage future delivery risk:
- Rolling reserve: a share of each settlement is held for a set period, then released on a rolling basis.
- Capped or upfront reserve: a fixed amount is held, either collected upfront or built up over time.
- Ticket and volume caps: limits on the size of any single transaction and on total monthly processing.
Terms vary by processor and by merchant, so confirm the exact structure in your agreement. You can't always avoid these tools, but you can make them less likely or smaller.
Structure Payments Around Milestones
Splitting a project into deposit, design approval, development, and launch payments lowers the amount of undelivered work you're carrying at any one time. For many agencies, this is one of the most useful changes they can make. Our guide to deposit and milestone payment terms walks through how to word them.
Ask for Limits That Match Reality
Don't understate your largest ticket to look safer on the application. A limit set too low means your next big deposit may be held or declined. State your real numbers and back them up with a sample contract.
Call Before the Big Charge
If an unusually large project payment is coming, contact your processor before you run it and send the signed contract and invoice. A charge the risk team already expects is less likely to trigger an automatic review.
Offer ACH for the Largest Invoices
Bank transfers follow different dispute rules than cards and can take pressure off your card limits. Some agencies also look at cost programs. MannyPay offers cash discount, dual pricing, and surcharging where permitted. If you're considering that route, read about passing card fees on large web design invoices and confirm the rules that apply in your state.
Use Authenticated Online Payments
A payment link or invoice that supports 3D Secure authentication adds a verification step for card-not-present charges, which keying in card numbers yourself doesn't provide.
Warning Signs Before a Processor Holds Your Funds
Holds usually follow visible triggers. Watch for these:
- Volume or ticket size above your approved limits, even for a single transaction.
- A sudden jump in average ticket compared with your history.
- Rising refunds or chargebacks, especially several from one project or in one month.
- Many keyed transactions from first-time clients, particularly with failed address or security-code checks.
- A business description that no longer matches your sales, such as new product lines, resold software, or payments taken for clients.
- Website changes that remove policies or contact details, or that list services you didn't disclose.
- Unanswered emails from the risk team. A request for an invoice or contract is a chance to clear a review quickly. Ignoring it usually makes things worse.
If funds are already held, respond quickly with the contract, invoice, proof of completed work, and client communication. The steps are similar across providers. See why Stripe holds big web design payments for a walkthrough. When disputes come in after launch, our guide to winning chargebacks after a site launches covers the evidence issuers look for.
Next Steps for Your Agency
Processors flag agencies because of how and when you get paid, not because of the work itself. Large deposits, long timelines, and card-not-present payments create future delivery exposure. Milestone contracts, honest volume estimates, and early communication give underwriters what they need to approve you on workable terms.
Before you apply:
- Gather your sample contract, refund policy, and project timeline.
- Estimate your average ticket, largest ticket, and monthly volume honestly.
- Confirm that your website and business description match your actual services.
- Decide how you'll handle the largest invoices: cards, ACH, or both.
MannyPay provides merchant accounts for low- and high-risk businesses, along with virtual terminals, online gateways such as Authorize.net and NMI, and integrations including QuickBooks and Salesforce. Learn more about payment processing for web design agencies, or request a free quote and a MannyPay specialist will respond within one business day. Approval and account terms depend on underwriting.
This article is general information, not legal or financial advice. Confirm contract, fee, and compliance questions with a qualified professional and your processor.
This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.


