How High-Risk Merchant Underwriting Works

What an underwriter reads in your file, how the four steps of high-risk underwriting run, why files get declined and how to prepare a file that gets placed.

  • By the OpenGate underwriting desk
  • Updated
  • 10 min read

Merchant underwriting is the review an acquiring bank runs before it agrees to carry your chargeback and fraud risk. The underwriter reads your business model, your processing history, your sales funnel and your compliance record, then prices the risk or declines it. In high-risk acquiring, this review decides your rates, your reserve and your limits.

What the underwriter is deciding

The underwriter decides whether an acquiring bank will carry your risk, and at what price. When a customer disputes a transaction and you cannot cover it, the bank funds the refund and chases you for the money. When a merchant violates scheme rules, the bank pays the fines. The underwriter’s job is to estimate how often those events happen, how severe they get and whether your business can absorb them.

Three variables drive the estimate. First, dispute likelihood, which comes from your vertical, your price point and your history. Second, dispute severity, because a travel package creates a bigger loss than a subscription. Third, recoverability, meaning whether your margins, your reserve and your balance sheet can cover chargebacks and refunds. The underwriter prices all three into one number and one structure, then defends that structure in front of the bank’s credit committee.

High-risk underwriting differs from mainstream underwriting in one respect. A mainstream acquirer runs the same checks mostly to decide yes or no. A high-risk acquirer runs them to decide how, meaning which reserve, which cap, which monitoring and which pricing make the file acceptable. The decline is the fallback. The structure is the product.

What underwriters check: the four pillars

An underwriter checks four things, in this order: the business model, the processing history, the funnel and the people who own the company.

The business model

The underwriter starts with what you sell, to whom, at what price and how the product reaches the customer. Physical goods with tracked shipping behave differently from digital goods with instant delivery, and subscriptions behave differently from one-time sales. The model maps to a merchant category code, and that code sets the scheme rules that apply to you. An underwriter who understands your vertical reads the model on its own terms. One who does not will price it by the worst stereotype of the industry, which is exactly what a specialized gateway is built to avoid.

The model also defines the vertical licenses and the markets. A telemedicine clinic and a nutraceuticals store may show similar volumes, but the underwriter treats them differently because the delivery risk, the refund behavior and the scheme rules differ. Precision in the application matters more than persuasion. Write what you actually do, in the language the underwriter uses.

Processing history

If you processed before, the underwriter reads your statements month by month: volume, average ticket, refund rate, chargeback count and ratio, authorization rate, decline patterns. History that matches the model you described is the strongest single signal in the file. History that contradicts it raises questions that must be answered. A merchant who claims a 50 dollar ticket but shows a 400 dollar average has a credibility problem before the review starts. New businesses without history can still be placed, usually with a lower cap and a higher reserve that get reviewed after a few clean months.

The funnel and the website

The underwriter walks your site the way a customer would, from landing page to checkout to the confirmation email. They check that the price shown matches the price charged, that the refund policy exists and matches the product, that delivery promises are realistic and that the terms on the site match what you wrote in the application. Misleading funnels kill files faster than bad ratios. Each claim on the page is a liability the bank inherits, so the site gets the same scrutiny as the numbers.

The funnel review covers the claims, the pricing presentation and the post-purchase path. Negative option billing, where a free trial converts silently into a paid subscription, is the most common funnel reason for decline in continuity verticals. The fix is a checkout page that states the price, the rebill schedule and the cancellation path in plain language, because that page becomes the evidence file when disputes arrive.

Compliance, ownership and identity

The last pillar is who owns the business and whether they are who they say they are. The file needs corporate registration, a clear shareholder structure and identity documents for directors and ultimate beneficial owners. The underwriter runs sanctions and adverse media screening, checks politically exposed persons, and confirms the vertical licenses, or proof that the license application is filed, where the vertical requires one. Opaque ownership is the most common structural decline in high-risk underwriting, because the bank cannot assess a risk it cannot see.

The screening runs against public lists: sanctions, enforcement actions, negative media. A director with a past enforcement action is not an automatic decline, but it must be disclosed and explained, because the underwriter compares what you declare against what the screening finds. Discrepancies here end files, because they call the rest of the application into question.

The four steps of merchant underwriting

A competent high-risk gateway runs underwriting as a written process. The process OpenGate publishes runs in four steps, and it matches how serious acquirers work.

  1. The file. You describe the model in one page and send the listed documents: corporate records, ownership structure, processing history, website and vertical licenses.
  2. The analysis. An underwriter reads the file against the standards of the acquirers that could take it. The funnel, the policies and the numbers get checked before any bank sees the file. Gaps come back to you as a written list.
  3. The offer. The file is matched to an acquirer that fits your jurisdiction and vertical, and you receive the terms in writing: rates, reserve, caps, payout schedule and fees, sized to your volume. You compare them with what you pay today, then you decide.
  4. Go-live. After signature and KYC, integration and test transactions follow, then monitoring starts with the first live payment.

A complete file can move from first review to go-live in as little as two weeks. Incomplete files take longer, and the missing documents are usually the merchant’s to produce. That is why an offer of instant approval on a high-risk merchant account deserves a second look: nobody has read the file yet.

The documents, end to end

A complete file has five blocks, the merchant account requirements every acquirer shares. Corporate: certificate of incorporation, current registry extract, articles of association. Ownership: shareholder structure and identity documents for directors and ultimate beneficial owners, with source of funds for the larger stakes. Processing: monthly volume, refund and chargeback reports for the last three to six months, or a written explanation of why none exist. Banking: a corporate account in the company’s name, ready to receive settlement. Operations: the live website with terms, refund policy and the full checkout flow, plus the vertical licenses or proof the application is filed.

Assemble the blocks before you apply, not after. Underwriting stalls almost always trace to one missing block, and each stall costs days while the queue moves. The document list is the bank’s way of pricing risk it cannot see.

Why files get declined

Declines fall into a short list of causes, and most of them are fixable:

  • The ownership structure is unclear, or UBO documents are missing. The bank cannot underwrite what it cannot see.
  • Processing history contradicts the described model, on volume, ticket size or geography.
  • The website’s terms conflict with what is sold: forbidden claims, missing refund policies, promises the business cannot keep.
  • A required license is absent, and no application is pending.
  • The merchant sits on MATCH or TMF with an unresolved cause. Read the MATCH guide before you reapply.
  • Underwriting questions go unanswered for days. Silence reads as risk.
  • The website shows a different company than the application. Mismatched legal names, logos or addresses make the bank ask which entity it is actually boarding.
  • The model itself sits outside every acquirer’s appetite: counterfeit goods, unlicensed financial solicitation, anything illegal in the merchant’s own jurisdiction.

A decline is information. Good files get declined for fixable reasons, and the fix is usually specific.

How to prepare a strong file

  • Write the model on one page: product, price, market, delivery method, refund policy, current volume.
  • Pull six months of processing statements and separate refunds from chargebacks before you send them.
  • Align the website with the application before submitting. Terms, refund policy, contact details and delivery times must match the written description.
  • Disclose the awkward parts first: past terminations, MATCH listings, chargeback spikes, ownership changes. Explain the cause and the fix. The underwriter will find them anyway, and finding them unannounced is worse.
  • Have license copies ready, or proof the application is filed, where the vertical is licensed.
  • Answer underwriter questions within a day or two. Response speed is part of the file.

A strong file changes the offer itself: better rates, a smaller reserve, higher caps and a faster path to go-live. The pricing mechanics behind those terms are explained on the pricing page.

How the offer is built from the file

The underwriter’s review converts directly into the four numbers on your offer. The rate starts from interchange and scheme fees, then adds the acquirer’s margin for your vertical and your history, the structure behind interchange plus pricing. The reserve follows your dispute exposure: a file with clean history gets a smaller hold than a file with a spike. The cap follows your volume evidence, because the bank will not underwrite volume it has never seen. The settlement cycle follows your model, so a subscription business and a marketplace do not get the same payout schedule.

Each number traces back to something in the file, which is why the strongest negotiating position is a file that documents itself. If the underwriter has to assume, the assumption lands against you, and the number lands higher. The mechanics behind each of the four numbers are explained on the pricing page.

To see the four numbers your own file draws, assemble the five document blocks and send the file for review. The reply comes from a human underwriter within 1 business day and takes one of three forms: an offer, a list of missing documents, or an honest no. The review is free, and nothing binds you until you accept the written offer.

FAQ

Frequently asked questions

Do I need processing history to get approved?

No. A new business with a sound model can be placed with a lower cap and a higher reserve, reviewed after a few months of clean processing. History makes the offer better. Its absence makes the offer more cautious.

What is the single biggest reason files get declined?

The file says one thing and the website says another. When the application, the terms on the site and the processing history contradict each other, the underwriter stops trusting the file, and everything after that gets read with suspicion.

Can I apply while my license application is pending?

For licensed verticals, proof that the application is filed can start the review. Activation usually waits for the license itself, because the acquirer boards licensed businesses, not intended ones.

How long does underwriting take?

A complete file can move from first review to go-live in as little as two weeks. The bottleneck is almost always documents, which is why the document list should reach you before you start, not after you stall.

What should I do if my file was declined elsewhere?

Bring the decline with you, and the file as it stands. An honest gateway reads the previous decline as part of the history and tells you which parts of it are fixable, which acquirers would read the file differently, and which parts would follow you anywhere. A decline is a data point, not a verdict.

OpenGate Payments

Prefer to talk it through?

Every guide ends where the desk begins. Send your file and get a written answer.

Free to apply. A human answer within 1 business day.

Apply to start processing