Merchant Account Underwriting: Looking Beyond the High-Risk Label

Two merchants can sell in the same industry, use similar websites, and request the same monthly processing volume—and present very different underwriting risks.

One owns its inventory, delivers promptly, documents customer consent, and has the liquidity to cover refunds. The other depends on an untested supplier, collects payment months before delivery, and cannot clearly explain who is responsible when something goes wrong.

The reviewer needs to understand what those differences mean for delivery, customer obligations, and the acquiring relationship.

At Mentom, we believe there is a meaningful difference between “high risk” and fraud. Higher exposure can come from delivery timing, recurring billing, large transactions, regulatory complexity, or a business with limited operating history. Those characteristics require examination. They do not establish that the merchant is dishonest.

Fraud raises a different question: is someone misrepresenting the business, using unauthorized payment credentials, concealing the actual activity, or taking payment without an intention to provide what was promised? A legitimate merchant can also suffer fraud committed against it. The underwriting team needs to distinguish the merchant’s conduct from the risks affecting its transactions.

For legitimate merchants, that distinction can determine whether the conversation stops at a category label or moves into a substantive review of the business. For partners, it determines whether a difficult placement receives an explanation and a clear next step.

At Mentom, we specialize in underwriting merchants across business models, operating histories, and sizes. Our team brings payments experience, software, and automation to the review so we can connect the evidence, investigate exceptions, and work through the processing structure. That depth can uncover an approval path another provider may miss or lack the appetite to support.

The work is more involved than submitting an application. It connects the merchant, agent, underwriting team, acquiring relationship, payment technology, fulfillment operation, and ongoing risk management. Each has a role in making the account workable after approval.

This guide focuses on U.S. merchant acquiring and the operational framework I use to evaluate it. Requirements and acceptance depend on the actual business, applicable rules, and the authorized acquiring decision.

What Merchant Account Underwriting Evaluates

Merchant account underwriting is the review used to decide whether a business can be accepted for payment processing and under what conditions. Identity and business verification are part of it, but the review also concerns the proposed payment activity and the financial exposure it can create.

The acquiring bank sits behind the merchant’s ability to accept card payments. The processor supplies processing services, and an ISO may coordinate sales, onboarding, underwriting work, and ongoing support within that acquiring relationship. Responsibilities and delegated authority vary. A salesperson’s expectation should not be confused with an authorized approval.

The OCC’s Merchant Processing handbook describes a risk-based approach to merchant review, including business validity, financial condition, sales history, and periodic review. It is supervisory guidance for OCC-supervised institutions, not a checklist that automatically applies to every merchant or every sponsor bank.

For a merchant preparing an application, I would organize the explanation around these questions:

An answer such as “online retail” is a starting point. It does not explain whether the business ships stocked products tomorrow or collects payment for custom orders that take several months to produce.

Those two models deserve different conversations. A merchant category code (MCC) describes a category of activity; it does not explain the delivery cycle, financial capacity, customer experience, or integrity of the people operating it. Accurate classification matters, but it cannot replace the review.

For a more complex business, trace the funds as well as the sale. Identify the merchant of record, the entity receiving settlement, the parties delivering the product or service, and the party responsible for refunds. Explain any marketplace, platform, or third-party collection arrangement explicitly. Payment for another seller’s activity can raise a different acquiring question from payment for the merchant’s own sale.

An ISO’s underwriting work must also fit its acquiring relationship and delegated authority. Mentom’s value is in connecting these responsibilities and preparing a decision supported by the evidence.

High Risk and Fraud Require Different Questions

“High risk” is an imprecise commercial label. Depending on the speaker, it may describe credit exposure, dispute performance, regulated activity, transaction fraud, unfamiliar business models, or a provider’s limited appetite for a category. Ask which risk is actually being discussed.

I separate the review into several questions rather than forcing every concern into one label:

These dimensions can overlap. A legitimate business can be financially weak. An otherwise sound merchant can have an inadequate cancellation process. A polished, well-funded operation can still conceal prohibited or fraudulent activity. No single favorable fact resolves the entire file.

A concern is a reason to investigate

An entity-name mismatch could be a documented DBA relationship. It could also be an attempt to use a bank account belonging to another business. The reviewer needs evidence that resolves the relationship.

A sudden increase in sales could follow a supported promotion. It could also be inconsistent with inventory, customer demand, or the declared model. Compare the increase with what the operation can actually deliver.

High disputes could reflect delayed fulfillment, confusing billing, unauthorized transactions, or several causes at once. Review reason categories, transaction dates, complaint records, delivery evidence, and corrective actions. A percentage alone does not establish intent, and an explanation alone does not establish that the problem is fixed.

In these illustrative scenarios, the task is to test the explanation against independent information and operational evidence. An unresolved concern needs an owner and a documented resolution.

Controls must address the identified risk

A reserve may help address financial exposure. It does not establish valid customer consent, make a prohibited product permissible, or resolve fabricated ownership documents. Strong transaction screening cannot make an undeliverable order book deliverable.

For each concern, identify the cause, the evidence needed, the proposed control, the person responsible, and the remaining exposure after that control. Decide whether the remaining exposure is acceptable within the acquiring relationship.

The Underwriting System: People, Software, and Automation

Complex underwriting requires a team that understands more than the application screen. Someone must connect identity, financial capacity, customer acquisition, payment acceptance, fulfillment, and the rules governing the activity. Someone must also own the unanswered questions.

Software gives that team a consistent working record. Automation can move repeatable tasks and bring exceptions forward. Experienced people interpret the evidence, challenge unsupported answers, and make or escalate decisions within their authority.

At Mentom, we combine these elements because a complicated merchant should not depend on scattered emails and one person remembering every detail. Our operating model connects onboarding, underwriting, technology, and accountable service. Here is what I expect a strong underwriting system to accomplish.

Build a connected record of the business

The working file should connect legal entities, owners, DBAs, domains, payment channels, settlement banking, processing history, and relevant third parties. Record which evidence supports each relationship and when it was reviewed.

For financial and transaction data, preserve the reporting period, source, units, and definitions. Monthly card volume is different from total revenue. Gross sales differ from net settlement. Refund dollars differ from refund counts. A risk review built on mismatched definitions can reach the wrong conclusion even when every document is genuine.

Record the distinction between verified facts, merchant representations, projections, and unresolved items. Keep enough history to understand changes without confusing an outdated document with the current operating model.

Automate repeatable work with visible exceptions

Useful automation can identify missing fields, request required records, track document freshness, route a specialist review, remind an owner about an unresolved item, and notify the team when information changes. Where document extraction or external data is used, keep the source visible and provide a way to correct errors.

A mismatch should create a question that someone can resolve. It should not silently overwrite the merchant’s explanation or disappear when a new attachment arrives. Reconcile inconsistent results and document the resolution.

Queue design matters too. An item needs an owner, a reason for escalation, and a clear next step. “Pending” is a status; it is not a complete workflow. Protect sensitive records through appropriate access controls and approved submission channels while giving partners useful progress information.

Put experienced judgment at the decision point

The reviewer should understand how the risk travels through the payments ecosystem. A business may be commercially sound but outside one provider’s supported model. A gateway may offer a billing feature that requires separate acquiring review. A certification may satisfy one gate while leaving financial, fulfillment, or customer-experience questions open.

A decision record should state the approved activity, supporting rationale, conditions, limits, unresolved dependencies, and authority behind the decision. When an exception is proposed, explain what changes and why the evidence supports it. Route it to the person or institution empowered to decide.

There should also be a clear outcome when the evidence does not support acceptance. Expertise includes recognizing an unworkable model and explaining what must change.

Carry the approved model into operations

An underwriting decision is useful only if the deployed account reflects it. Transfer the reviewed channels, billing model, transaction profile, conditions, and relevant monitoring needs into onboarding and ongoing account management.

After launch, compare actual activity with the approved model. A new website, longer delivery cycle, sudden ticket-size change, or altered product offering can require another conversation. Changes should return to the appropriate reviewer with the context from the original decision.

For merchants, Mentom brings experienced people to the questions that can hold up a complex application. For agents and referral partners, we connect that review with onboarding, technology, and ongoing support, with people accountable for the next step.

Why Delivery Timing and Cash Flow Matter

A completed card sale can still be disputed. If a merchant cannot meet its obligations or cover the resulting amounts, the acquiring relationship may face losses. That possibility is one reason underwriting asks questions that resemble a credit review even when the merchant is not applying for a business loan.

Think about the time between collecting money and completing the customer’s purchase. During that interval, the merchant has received payment but still owes something.

An illustrative example of outstanding obligations

Assume an online business captures and settles $10,000 per day for orders that take 30 days to deliver. In a simplified steady-state example, with no cancellations, partial deliveries, or variation in sales:

$10,000 per day × 30 days = $300,000 in paid orders awaiting delivery.

If delivery stretches to 60 days at the same sales pace, the figure becomes $600,000.

This is an illustration of unfulfilled paid orders, not a network formula, a predicted loss, or a reserve calculation. Real exposure depends on the order book, delivery progress, refund obligations, dispute rights, and other facts.

The point is that a longer delivery cycle can change the payment conversation without changing the merchant’s advertised product.

Before submitting an application, I would want the merchant to be able to explain how it funds production, what happens if a supplier is late, and how it would repay customers if delivery becomes impossible. A sales forecast does not answer those questions on its own.

Documents to Prepare for a Merchant Account Application

Ask the onboarding team for the requirements for your specific business before gathering sensitive records. The requested package may be limited for a straightforward account or more extensive for a complex model.

As preparation, organize the following information and be ready to provide the applicable evidence through the approved submission channel:

This is a preparation menu. It does not mean every merchant must submit every item.

Explain legitimate differences instead of leaving them unresolved

A legal entity, storefront name, website brand, and bank account title may legitimately differ. The reviewer still needs to understand their relationship.

For example, a business may trade under a registered DBA while its banking documents show the LLC’s legal name. Include the explanation and the applicable supporting record. Do not assume the reviewer will infer the connection from a logo.

If ownership recently changed, state what changed and when. If the business moved, distinguish the current operating location from an older address that still appears on a record.

Submit complete records securely

Provide the period and pages requested. A cropped screenshot may omit information needed to evaluate a document. Ask which formats and redactions are acceptable rather than altering the evidence yourself.

Use the provider’s approved secure process for identity, banking, and financial records. An initial website inquiry is not the place to paste account numbers or a Social Security number. At Mentom, the public inquiry form specifically asks visitors to leave sensitive information out of that submission.

Keep a submission record so you know what was provided and which version is current. That is particularly useful when the merchant, agent, accountant, and onboarding team are contributing different parts of the application.

Describe the Payment Activity You Actually Expect

Underwriting preparation should include a payment profile that the business can explain.

Separate card volume from total revenue

If the business expects $150,000 in monthly revenue but only $90,000 in card payments, identify both figures correctly. Bank deposits may also include ACH payments, loans, transfers, or other receipts, so they should not automatically be described as card-processing history.

Distinguish the current run rate from the projection. If you expect a significant increase, describe the reason and the evidence behind it: additional locations, signed contracts, a new sales channel, or a planned campaign.

Explain average and largest expected transactions

Average ticket size helps describe typical activity. It does not reveal the largest sale you plan to process.

A business collecting mostly $100 purchases and occasionally charging $8,000 should explain the larger transactions separately. Describe what they purchase, whether they are deposits or full payments, and how fulfillment works.

An occasional large transaction is easier to discuss when it is part of the original explanation rather than a surprise after activation.

Identify every payment channel and billing model

Estimate how customers will pay. Include website checkout, in-person acceptance, phone orders, invoices, and recurring payments where applicable. If a channel is planned but not yet operating, say so.

For subscriptions, explain the first charge, later charges, trial conversion if applicable, cancellation process, and evidence of the customer’s agreement. For deposits or advance payments, explain the delivery timetable and the amount remaining due.

Before launching a new billing arrangement, confirm the applicable requirements with the acquiring team. The ability to configure a gateway setting does not establish that the arrangement has been reviewed or that the customer disclosures are sufficient.

Give processing history enough context to be useful

If you already accept cards, prepare a short explanation of the activity in the requested statements. Identify which businesses, websites, locations, and merchant accounts they cover. A combined total can conceal an important difference between an established storefront and a newly launched online channel.

Explain significant refunds, disputes, volume changes, or prior account restrictions rather than waiting for a reviewer to discover them. If there was a problem, describe the cause, what changed, and the evidence showing whether the correction worked. Moving to a new provider does not resolve an underlying delivery or customer-service issue.

When discussing a dispute rate, identify the source, reporting period, and calculation. A count-based rate and a dollar-based rate answer different questions. Different network programs may also use different populations and timing. Do not present a dashboard percentage as interchangeable with every network metric.

What an Ecommerce Website Should Make Clear

An ecommerce application should allow the reviewer to understand the same transaction the customer will experience. A polished homepage is useful, but it cannot explain an unfinished checkout or an inaccessible product catalog.

I recommend checking the following before submission:

• Products and services have understandable descriptions and accurate prices.
• The customer can identify the business and find a working support channel.
• Delivery expectations reflect how orders will actually be fulfilled.
• Refund, return, and cancellation policies are accessible and consistent with checkout.
• Subscription terms explain the billing amount and frequency, including any trial conversion.
• The proposed billing descriptor is discussed with the provider and can be connected to the business customers recognize.
• Every relevant sales website is disclosed, including alternate brands and checkout domains.

These are practical preparation checks. Specific disclosure obligations depend on the transaction, applicable network rules, consumer law, and acquiring requirements.

Visa’s public dispute guidance emphasizes clear refund and cancellation policies, communication about delivery delays, and recognizable merchant names. Those are useful reasons to review the customer journey before the first live transaction.

Give the reviewer a way to see the purchase

If the site is not public yet, ask how the team wants to review it. Provide approved preview access or a demonstration without exposing credentials in an ordinary email.

Walk through the landing page, product offer, checkout, confirmation, fulfillment, and support process. Identify anything still being built. The reviewer should be able to distinguish the planned experience from the one that is ready to launch.

Match the policies to the actual operation

A policy promising shipment within two days does not describe a business whose supplier routinely takes three weeks.

Likewise, a refund policy is only useful if the business can carry it out. Who authorizes the refund? Where does the money come from? How does the customer receive confirmation?

For recurring models, make cancellation understandable and test that it works. Mastercard’s public subscription overview explains why unclear recurring transactions can create complaints and disputes. Confirm the current detailed requirements for your model with your provider.

Why Merchant Account Applications Take Longer Than Expected

There is no approval timeline that fits every business. A useful status update should explain what remains unresolved and what happens next.

Information does not agree across the file

The application describes immediate delivery, the website advertises preorders, and the supplier agreement suggests a much longer timetable. Sending another copy of the same bank document will not reconcile that difference.

Identify the current operating model, correct inaccurate information, and explain the change. Keep the original evidence available when the team needs to understand the history.

The business explanation is incomplete

Labels such as “consulting,” “wellness,” or “marketing services” leave room for materially different activities. Describe the deliverable, customer, price, sales method, and responsibility for providing the service.

If a third party performs part of the work, explain the relationship. A reviewer should not have to reconstruct the business from scattered invoices and website claims.

A request is answered with a document that does not answer the question

Suppose the team asks how the business can support refunds while customers wait for delivery. A projected revenue spreadsheet may show expected sales, but it does not necessarily demonstrate available liquidity.

Ask what concern the request is intended to resolve and which evidence is acceptable. That can prevent several rounds of technically complete but unhelpful responses.

Additional review or an outside dependency remains

Some applications require a specialist decision, verification from another party, or an applicable license or certification. Document collection, underwriting, and those external processes may have different owners.

For healthcare models, our telehealth underwriting guide discusses the additional questions that can arise. Our healthcare payment processing article also explains why coordination between certification and acquiring review matters to merchants and partners.

Status is too vague to act on

“Still pending” does not tell the merchant whether it needs to do something.

I would ask for the specific outstanding item, the person responsible, whether the submitted response was accepted, and when the next update is expected. If the decision is waiting on the acquiring institution, say that clearly rather than giving the merchant another task without a reason.

How Underwriting Conditions Affect the Merchant

An approval may include conditions. Understand them before treating the account as ready for the business’s full operating plan.

Depending on the relationship, those conditions may address processing volume, transaction size, payment channels, products, fulfillment, reserves, or funding arrangements. They should be evaluated using the actual approval and governing agreement, not a general description from a sales conversation.

Reserves and funding arrangements

A reserve sets aside funds to support obligations under the agreement. A reserve is distinct from a processing fee, and its existence does not mean the merchant has already caused a loss.

The OCC handbook discusses reserves and delayed settlement as possible tools for managing merchant exposure. It does not prescribe one reserve percentage or release schedule for every account.

If a reserve is proposed, ask how it is funded, how the balance is reported, what obligations it secures, and how release or review works. Ask what happens if processing stops while obligations remain outstanding. Request the applicable terms in writing.

For funding, distinguish a routine settlement schedule from a risk-related delay or hold. Confirm cutoff times, business-day treatment, deductions, and any conditions that affect availability. Model the cash flow using the actual arrangement offered.

Limits should fit the operating plan

If the business is preparing to process substantially more than the reviewed volume, discuss that before the campaign begins. The same applies to a transaction that is materially larger than the activity originally described.

Ask how increases are reviewed and what evidence will be needed. Splitting a sale or moving activity to another account to evade a control is not a substitute for discussing the underlying business need.

Personal guarantees deserve attention

If a personal guarantee is part of the agreement, understand its scope before signing. Do not assume an LLC’s existence overrides obligations an individual separately accepts. Have the actual agreement reviewed if its meaning or financial implications are unclear.

The merchant should know which terms are requirements for this approval, which reflect the provider’s policy, and which can be discussed. Do not describe every acquiring condition as “a Visa rule” or “a Mastercard rule.”

How Mentom Supports Merchants, Agents, and Referral Partners

An experienced underwriting team creates value when it can explain the opportunity, identify the right acquiring fit, and carry the decision into a workable launch.

That is what we want merchants and partners to bring to Mentom: the complete business, including the parts that have been difficult to place. We specialize in underwriting across different sizes and operating models, from straightforward acceptance needs to opportunities requiring a deeper review of billing, delivery, third parties, or regulated activity.

When another provider has said no

A decline can reflect incomplete evidence, unresolved operating weaknesses, prohibited activity, or a mismatch with a provider’s supported categories and risk appetite. Those are different starting points.

Mentom can review the available explanation, assess the actual business, and determine whether a supportable path exists in the appropriate acquiring relationship. That may involve better evidence, a specialist review, changes to the customer journey, or a processing structure with conditions that fit the exposure. A previous decline does not by itself answer those questions.

Our understanding of underwriting and the payments ecosystem can reveal approval paths other providers may not recognize or support. We work through the evidence and the acquiring fit to determine what is possible. Acceptance remains with the authorized decision process.

For the merchant, the resulting setup must also work economically and operationally. We connect that review with payment processing, appropriate technology, onboarding, and ongoing service. An approval that cannot support the merchant’s real delivery cycle or cash needs is an incomplete solution.

The partner’s role should match the relationship it has agreed to own.

Agents managing the application

An agent involved in the sales and application process can reduce avoidable confusion by preparing the business explanation before submission.

I recommend a short summary covering what the merchant sells, who buys it, how payments occur, fulfillment timing, expected volume, and any material issues that need review. Include the relevant evidence and explain gaps honestly.

Do not promise approval, a reserve waiver, or a funding arrangement that has not been authorized. If an exception is needed, identify the requested exception and the business reason. Describe it to the merchant as a request until the appropriate decision is made.

Keep one current list of outstanding items. Confirm that the merchant understands each request, and avoid sending contradictory answers through multiple contacts.

Bring us the operating details early, especially when a merchant has been reduced to a category label elsewhere. Our team can engage on the underlying risk, clarify what evidence is needed, and work through the potential structure. That gives the agent a substantive underwriting conversation to support the merchant relationship.

Referral partners making an introduction

A referral partner may simply introduce the business and provide useful context. It should not need to become an underwriter or collect sensitive financial records to make that introduction.

Mentom’s referral partner program describes that distinction: the partner connects the opportunity, while Mentom handles the sales conversation, application, onboarding, and ongoing merchant relationship.

A useful referral explains the business’s payment need and puts the right people in contact. You can refer a complex business without having to decide yourself whether it is “high risk” or how it should be underwritten. The merchant can then provide sensitive information directly through the appropriate onboarding process.

Preserve the relationship through clear communication

When a question is difficult, help the merchant understand why it matters. Avoid describing every request as unnecessary paperwork or implying that withholding information will make approval easier.

Our Agent vs. ISO guide explores the operating responsibilities behind a payments business.

Approval and Technical Readiness Are Separate Checks

A gateway account, a programmed terminal, or a successful test transaction demonstrates a technical step. Confirm separately that the merchant has the required authorization for live processing and has met any pre-activation conditions.

Before launch, I recommend verifying:

1. The written decision covers the business, channels, and activity you plan to launch.
2. Any conditions required before activation have been satisfied.
3. The equipment or checkout is configured for the approved setup.
4. Sales, voids, refunds, receipts, and recurring workflows have been tested where applicable.
5. Funding and reporting arrangements are understood.
6. The merchant knows how to reach support and who receives risk or account notices.

Payment security remains part of operating readiness

Using a hosted checkout or outsourcing processing can reduce the merchant’s PCI DSS scope. It does not remove every merchant responsibility.

PCI SSC’s outsourcing FAQ states that merchants remain responsible for appropriate provider oversight and must confirm their validation obligations with the organization managing their compliance program. The applicable assessment depends on the actual environment and eligibility; a provider’s compliance status is not the merchant’s own validation.

Ask which systems and providers are involved, which responsibilities the merchant retains, and what validation is required for the deployed payment flow. Mentom’s Online Payments page describes available payment configurations, but the final setup should be reviewed for the specific business.

Keep the Acquiring Team Informed as the Business Changes

The original application describes a business at a particular point in time. Growth can change the facts that supported that review.

As operating guidance, discuss material changes with the provider before implementation and confirm the notice or approval requirements in the agreement. Examples include a new owner, a new product category, another sales website, recurring billing, longer delivery times, or a substantial increase in expected volume.

Explain the planned change and the controls supporting it. A new supplier may affect delivery. A subscription launch may affect customer consent and cancellation. A large promotion may increase both revenue and outstanding orders.

Monitor whether the actual activity still matches the plan. Review refunds, customer complaints, delivery delays, and disputes alongside sales. Respond promptly when the acquiring team requests information.

For deeper coverage of network monitoring, see our Visa VAMP guide. Network-program thresholds and the acquiring institution’s own risk decisions should be understood separately.

Merchant Account Application Readiness Checklist

Use this checklist to prepare for the onboarding conversation. It is not an approval score or a substitute for the provider’s requirements.

Business and payment model

• I can explain what the business sells and who is responsible for delivery.
• I have identified the legal entity, trading names, owners, and authorized signer.
• I have disclosed the relevant locations, websites, and payment channels.
• I have separated historical card volume from projected activity.
• I can explain the average sale, largest expected sale, and any seasonal changes.
• I have identified deposits, advance payments, subscriptions, and delivery delays.

Records and customer experience

• I know which documents the onboarding team requires and the accepted submission method.
• I have current records for the requested periods and explanations for legitimate differences.
• My website and checkout describe the business and billing accurately.
• Customers can find support and understand delivery, refunds, and cancellation.
• I can explain the resources available to meet fulfillment and refund obligations.

Decision and launch

• I know what remains outstanding and who owns each next step.
• I have reviewed the actual approval conditions and relevant agreement terms.
• I understand funding, reserve terms if applicable, and the process for reviewing limits.
• I have confirmed live-processing authorization separately from technical setup.
• I know my payment-security responsibilities and support contacts.
• I know how to discuss a material business change with the provider.

For an agent, use the checklist to guide preparation with the merchant. For a referral partner, use it to explain what onboarding may involve and let the team handling the application manage the detailed collection.

Frequently Asked Questions

How long does merchant account underwriting take?

Timing depends on the business, the completeness of the information, verification work, and any additional decisions required. Ask whether the estimate covers document collection, underwriting, technical activation, or all three. When the file is pending, request the outstanding item and the next update rather than relying on a generic timeline.

What documents do I need to open a merchant account?

Ask for the requirements for your specific business. Be ready to discuss identity, ownership, settlement banking, payment activity, fulfillment, and customer policies. Existing merchants may be asked for processing history; more complex models may require additional financial or operational evidence. The preparation table in this guide helps organize the conversation.

Can a new business get a merchant account without processing history?

A new business has no historical processing statements to provide. Disclose that clearly and ask what evidence is needed instead, such as the operating plan, financial resources, supplier arrangements, and proposed customer journey. Acceptance and terms remain subject to review.

Does underwriting include a personal credit check?

It may, depending on the provider and application. Ask whether a consumer credit report will be obtained, whose report is involved, which authorization is required, and how the inquiry will be handled. Do not assume every merchant application uses the same credit-review process.

Why does underwriting want bank or financial statements?

Those records may help evaluate the business’s financial position and ability to meet its obligations. Ask which concern needs to be addressed and which records are acceptable. A document supplied to verify deposit instructions may not answer a separate question about liquidity.

Does every merchant need a reserve?

No universal reserve applies to every account. If a reserve is part of the proposed arrangement, request the actual funding, use, reporting, and release terms. Evaluate the cash-flow effect before accepting the arrangement.

Why would a business already processing elsewhere need another review?

The new provider must decide whether the business fits its own acquiring relationship and policies. Provide a clear account of the existing setup, performance, and reason for switching. An earlier approval does not establish the new provider’s decision.

Does “high risk” mean the merchant is fraudulent?

No. The label can refer to structural exposure, regulated activity, dispute potential, or a provider’s appetite. Evaluate those concerns separately from evidence of deception or unauthorized transactions. A legitimate merchant can still present unacceptable exposure for a particular acquiring relationship; that does not establish fraud.

Can Mentom help with a merchant another provider declined?

We can review the business and the available explanation for the decline, assess the evidence, and explore whether an appropriate processing path exists. Our experience with complex underwriting can identify opportunities a provider with different capabilities or appetite may not support. Share the actual model, prior concerns, and supporting records so the review starts with an accurate picture.

Does software replace the underwriter?

Software and automation can organize evidence, move tasks, and surface exceptions. Interpretation, specialist review, and authorized decisions still require accountable judgment. The strongest process connects those functions and carries the decision into ongoing operations.

What should I do if the application is declined?

Ask what information the provider can share and whether a correction or additional evidence could change the decision. Distinguish a fixable information problem from a business model the provider does not accept. Do not submit a different description of the same activity to make it appear eligible.

Can my agent approve the account?

Only rely on approval communicated through the authorized process for that acquiring relationship. An agent can help explain the business and coordinate the application, but its sales role does not by itself establish approval authority.

About the Author

Dave Wilson is Chief Operating Officer at Mentom Payments. His work connects merchant onboarding, underwriting, risk, compliance, support, payment technology, and partner operations. Read more from Dave.