When Your Business Doesn’t Fit the Payment Processor’s Box
Why Modern Merchant Underwriting Needs to Change
Learn why legitimate businesses get declined for merchant accounts and how flow of funds, MCCs, websites, compliance and proper underwriting can improve approval.
Presented by Allen Kopelman, CEO — Nationwide Payment Systems-Host of B2B Vault: The Biz2Biz Podcast
AI Overview
Modern businesses do not always fit neatly into traditional merchant-account categories. A company may accept payments through a website, invoices, payment links, subscriptions, salespeople, marketplaces, or several channels at once. That complexity does not necessarily make the business high-risk—but if the merchant cannot clearly explain its business model, flow of funds, fulfillment, products, policies, and payment process, an underwriter may interpret that complexity as risk.
The key to successful merchant underwriting is no longer simply completing an application. Businesses increasingly need to present a complete and consistent picture of how they operate.
sponsored by
Complicated Does Not Automatically Mean High-Risk
This was one of the most important topics I discussed recently on the Cents Chat podcast.
A complicated business model and a risky business model are not necessarily the same thing.
Unfortunately, they can look very similar when the merchant's business is poorly explained.
An underwriter may look at a business and initially think it resembles:
Debt collection
Money transmission
Lending
Adult content
Future delivery
Marketplace activity
Subscription billing
User-generated content
Third-party payment aggregation
The merchant may not actually operate in any of those categories.
But underwriting decisions are based on the information available.
When important information is missing, inconsistent or unclear, the processor has to make assumptions—and those assumptions tend to lean toward the more conservative risk interpretation. That was a central theme of my conversation with Cents Chat hosts Kitty and Jason. (CentsChat)
That is why one of the first questions we increasingly ask a merchant is:
What does the flow of funds look like?
The Flow of Funds Tells the Real Payment Story
A business owner may say:
"Customers pay us for our service."
That's a start.
It's no longer enough.
We need to understand what actually happens.
Who is selling the product or service?
Who accepts the payment?
Who owns the funds?
Where does the money settle?
When is the product delivered?
When is the service performed?
Does the merchant collect a deposit?
Does another party receive any portion of the funds?
Who handles refunds?
Can the merchant initiate another transaction later?
Is a card stored for future use?
Are transactions recurring?
Is the merchant paying commissions or proceeds to third parties?
In the Cents Chat discussion, the flow of funds was described as essentially the "plot" of the payment story. Without it, an underwriting department can see individual pieces of a business without understanding how those pieces connect. (CentsChat)
That distinction becomes extremely important when money moves between multiple parties.
Businesses sometimes assume they can simply collect money from customers and then distribute that money to someone else.
Payments do not always work that way.
Depending on the structure, that can raise issues involving payment aggregation, marketplaces, money movement, KYC, AML requirements and card-network rules.
A business model needs to be designed correctly before significant transaction volume begins flowing through it.
The Merchant Category Code Does Not Tell the Whole Story
Merchant Category Codes—or MCCs—remain an important part of the payments ecosystem.
But an MCC is a classification.
It is not a business plan.
Two businesses with the same MCC can have completely different risk profiles.
Consider two service companies.
One performs a service today and collects payment after completing the work.
Another collects $10,000 six months before performing the service.
They might technically operate within the same industry.
From an underwriting perspective, however, they are very different businesses.
The second company creates considerably more future-delivery exposure.
The same issue arises with eCommerce.
An online retailer carrying merchandise in a U.S. warehouse presents a different underwriting profile from a website accepting customer payments before ordering merchandise from an overseas supplier.
Understanding what the merchant sells is only the beginning.
You need to understand how the transaction works.
Your Underwriting File Has to Tell One Consistent Story
One of the easiest ways for a legitimate merchant to create unnecessary underwriting problems is inconsistent documentation.
A good merchant application is much more than an application form.
Depending on the business, an underwriting package may include:
Merchant application
Website
Bank statements
Processing statements
Financial statements
Sample invoices
Customer contracts
Supplier agreements
Fulfillment information
Shipping policies
Refund policies
Cancellation policies
Privacy policy
Terms and conditions
Business licenses
Professional licenses
Insurance
Product documentation
Compliance documents
Flow-of-funds diagrams
All of those documents should describe the same business.
That sounds obvious.
You would be surprised how frequently it does not happen.
I regularly see businesses copy terms and conditions, privacy policies or refund policies from another website and forget to change portions of the document.
The wrong corporation appears.
The address is incorrect.
Another company's name remains buried in the policy.
The refund policy contradicts what the checkout page says.
A business owner may see that as an innocent website mistake.
An underwriter reviewing an unusual business model may see it very differently.
As discussed on Cents Chat, conflicting information across the website, application, contracts, bank activity and other documents can make even innocent inconsistencies look like potential concealment. (CentsChat)
Documentation creates credibility.
Sometimes One Merchant Account Should Not Handle Everything
Another increasingly common issue involves businesses offering several very different products or services.
Business owners naturally want everything to run through one company and one merchant account.
That isn't always the best structure.
Suppose a company offers:
Business consulting
Software subscriptions
Financing-related services
Online courses
A marketplace
Physical products
Putting everything through the same merchant account can create a confusing risk profile.
Sometimes the cleaner approach is separating different lines of business into appropriate merchant accounts or processing structures.
The objective is not to disguise what the merchant is doing.
Quite the opposite.
The objective is to make each business activity easier to understand and properly underwrite.
Startups Need to Think About Payments Earlier
This issue is particularly important for startups.
Founders often spend months building:
Their software
Website
AI technology
Customer acquisition funnel
Pricing strategy
Investor pitch
User interface
Then somebody asks:
How are customers going to pay you?
The answer is frequently:
"We'll use Stripe."
That isn't really a payment strategy.
For straightforward businesses, an online processor may work perfectly well.
But founders building unusual platforms, regulated products, marketplaces, creator platforms, subscription businesses or businesses involving complex money movement need to understand their payments risk before launch.
I discussed an example on Cents Chat involving a creator platform that initially struggled to get approved because banks assumed that user-generated content meant adult content.
It did not.
But user-generated-content platforms carry additional compliance considerations, and we had to explain the business model, compliance structure and actual content before finding the appropriate banking relationship.
That company eventually grew to process more than $1 million per month. (CentsChat)
The lesson isn't that every unusual startup will get approved.
The lesson is:
You need the right underwriting conversation.
"Instant Approval" Can Become a Problem Later
This is one of the most misunderstood areas of payment processing.
A merchant signs up online.
They enter basic information.
Their account activates.
They start processing.
The business owner assumes:
We've been approved.
Not necessarily.
Some payment models perform extensive review later, after transactions begin flowing.
That can become a serious issue for businesses with unusual or unsupported activities.
Once transaction patterns attract attention, the processor may investigate the business more closely.
That can result in:
Additional documentation requests
Processing restrictions
Delayed settlements
Reserve requirements
Account suspension
Account termination
Funds being held
For certain serious compliance problems, merchants can potentially face placement in card-network merchant monitoring or termination databases.
This is why I tell complicated businesses:
Do not confuse account activation with complete underwriting.
The time to understand whether your processor supports your business is before you're processing significant volume—not when hundreds of thousands of dollars are moving through the account.
AI Is Changing Merchant Fraud
There is another reason merchant underwriting is getting harder.
Fraud is getting better.
Years ago, the payments industry frequently dealt with what we called a straw signer.
Someone with a legitimate identity would apply for a merchant account on behalf of someone who might otherwise have difficulty being approved.
Today we increasingly have to worry about synthetic and stolen-identity fraud.
Fraudsters can obtain highly detailed identity information and create extremely convincing merchant applications.
During the Cents Chat discussion, I described a real situation involving an application supposedly submitted by a restaurant-equipment company.
Something didn't look right.
I researched the physical address.
There wasn't a restaurant-supply business there.
There was a dentist's office.
The applicant's identity matched the dentist.
I contacted him.
He had no idea someone was applying for merchant accounts using his identity.
Shortly afterward, he received multiple Clover devices from different payment companies that had apparently approved fraudulent applications associated with his identity. (CentsChat)
Think about what that means.
The application looked legitimate enough to make it through multiple organizations.
AI Is Helping Both Sides
Artificial intelligence makes this problem even more interesting.
Fraudsters can potentially use sophisticated technology to create more convincing:
Websites
Business descriptions
Documents
Communications
Identity profiles
At the same time, payment companies can use technology to examine applications more effectively.
AI-assisted tools can help compare information across documents, identify inconsistencies and flag unusual patterns.
But there is an important distinction:
AI should assist underwriting—not replace judgment.
A computer telling an underwriter that everything matches does not prove a business is legitimate.
Likewise, an automated flag does not necessarily mean a merchant is fraudulent.
Someone still has to understand the business.
That human layer becomes even more valuable as fraud becomes more sophisticated.
Underwriting Should Be About Understanding the Business
Too much of the payments industry still treats underwriting as a box-checking exercise.
Does the merchant have:
Business license? Check.
Bank account? Check.
Website? Check.
Owner identity? Check.
MCC? Check.
That approach works well when the business is straightforward.
Modern commerce increasingly isn't.
Businesses are combining software, payments, subscriptions, marketplaces, digital goods, AI, physical products, services and multiple sales channels.
The payment industry needs to evolve with them.
The better underwriting question isn't:
"Which box does this merchant fit into?"
It is:
"How does this business actually work?"
A Pre-Underwriting Checklist for Complicated Businesses
Before submitting a merchant application, a business owner should be able to clearly answer these questions:
1. What exactly do you sell?
Do not answer with vague descriptions such as "technology," "consulting" or "services."
Explain what the customer is purchasing.
2. Who is your customer?
Consumer?
Business?
Government?
Marketplace participant?
Member?
Subscriber?
3. When does the customer pay?
Before delivery?
At delivery?
After delivery?
Monthly?
Annually?
With a deposit?
4. When is the product or service delivered?
The longer the period between payment and delivery, the more underwriting questions may arise.
5. Where does the money go?
Does 100% settle to the business?
Are funds distributed to third parties?
6. How are payments accepted?
Website?
POS?
Virtual terminal?
Payment links?
Smart invoicing?
Mobile?
Recurring billing?
API?
7. What is your refund and cancellation policy?
Your website, contracts and merchant application should all agree.
8. Do you operate in a regulated industry?
Some products and business models require additional documentation, licensing, registration, monitoring or card-network compliance.
9. Does your website accurately describe the business?
Your website is increasingly part of your underwriting file.
10. Can an outsider understand your business in five minutes?
If not, create a written business explanation and flow-of-funds diagram.
The Website Is Now Part of Your Merchant Application
This deserves special attention.
Twenty years ago, the merchant application might have been the primary underwriting document.
Today your website can be just as important.
An underwriter may review:
Products
Pricing
Checkout
Refund policy
Shipping policy
Privacy policy
Terms
Contact information
Customer-service information
Business address
Product claims
Subscription language
Fulfillment timelines
Your website should accurately describe how the company operates.
Do not build one business and describe another.
Do not copy policies from competitors without reviewing them.
And do not assume a beautifully designed website automatically makes your business easier to approve.
Clarity beats cosmetics.
Payments Should Be Part of Business Design
This is where I believe the conversation needs to move.
Payments should not be something a company thinks about three days before launch.
For modern businesses, payments are infrastructure.
Founders should be thinking about:
Merchant underwriting
Banking relationships
Payment methods
Flow of funds
Chargeback exposure
Refund procedures
Recurring billing
Tokenization
ACH
Digital wallets
Payment links
Smart invoicing
APIs
Compliance
Fraud prevention
Accounting integration
at the same time, they are designing their product and customer journey.
That becomes even more important when your business model isn't ordinary.
When the Merchant Doesn't Fit the Box
The payments industry will always need categories.
Banks need risk models.
Card networks need rules.
Processors need underwriting standards.
But commerce is evolving faster than the boxes we created to describe it.
That means business owners have an additional responsibility.
Make your business understandable.
Explain exactly what you sell.
Explain how customers pay.
Explain when products or services are delivered.
Explain where funds go.
Make sure your documentation agrees.
Make sure your website matches reality.
And work with a payment professional who understands your business model before sending an application to every processor on the internet.
Complicated businesses aren't automatically bad businesses.
But unexplained complexity almost always looks like risk.
How Nationwide Payment Systems Helps Complicated Businesses
Nationwide Payment Systems has worked with merchants since 2001 across traditional, B2B, eCommerce, SaaS, regulated and high-risk industries.
Our role isn't simply submitting merchant applications.
We work to understand the business first.
That can include reviewing:
Business model
Website
Flow of funds
Processing history
Fulfillment
Products and services
Merchant Category Code
Compliance requirements
Banking options
Chargeback exposure
Payment technology
Invoicing requirements
Accounting integrations
API requirements
When necessary, we work directly with processors, sponsor banks and underwriting teams to properly explain business models that may not fit neatly into a traditional underwriting category.
The goal is not to find a loophole.
The goal is to put the right merchant with the right payment solution and the right banking relationship.
Have a Business That's Difficult to Explain to a Payment Processor?
Before submitting applications everywhere, talk to Nationwide Payment Systems.
We can review your business model, payment flow, website and processing requirements and help determine the appropriate path forward.
Schedule a payment technology review with Nationwide Payment Systems.
