Know Your Business in High-Risk Payments: How We Use Middesk at Edge Payment Technologies

I am the Lead Engineer (Tooling) at Edge Payment Technologies, a payment gateway built for high-risk merchants. I build the internal tools our compliance and underwriting teams use to onboard and monitor merchants. Our merchants work in industries that many processors avoid: subscriptions and continuity billing, nutraceuticals, travel, online gaming, CBD, high-ticket coaching and others. These are legitimate businesses, but they draw higher chargeback rates, closer scrutiny from card networks and banks, and more attention from fraudsters who want to hide behind them.

That makes merchant onboarding the most important control we have. Every merchant we approve is a business our sponsor bank and the card networks trust us to vouch for. If we let a shell company, a sanctioned party or a re-badged terminated merchant through, the losses and the regulatory consequences land on us.

This post explains what Know Your Business (KYB) means for a high-risk gateway, why we use Middesk for it, and how its results shape our onboarding decisions.

What KYB is, and why it matters more in high risk

Know Your Customer (KYC) confirms that a person is who they say they are. Know Your Business does the same for a company: that it legally exists, is in good standing, operates where it says it does, and is owned and controlled by the people named on the application.

For a mainstream processor, KYB is mostly about meeting regulatory expectations. For a high-risk gateway it is also our first line of defence against fraud and loss, because the threats we see are specific:

• Shell and synthetic businesses created only to push through card volume and disappear before chargebacks arrive.
• Transaction laundering, where a merchant approved for one business processes payments for another, often prohibited, business.
• Previously terminated merchants returning under a new entity name to get past network match lists.
• Nominee owners fronting for the real beneficial owners, who may be sanctioned or have a history of fraud.
• Misrepresented business models, where the application describes something different from what the website actually sells.

A paper application and a few uploaded PDFs cannot answer these questions reliably. Documents can be edited, and an applicant can say anything in a form. We need independent, authoritative data.

Why Middesk

Middesk is a business identity platform that verifies US companies against primary sources rather than self-reported information. For our compliance team, a few things stand out.

Verification against official records

Middesk checks a business against Secretary of State filings across US states. We see whether the entity exists, where it is registered, its formation date, its current status (active, inactive, dissolved) and the officers and registered agent listed in its filings. A business that claims years of trading history but was formed last month, or one that is no longer in good standing, is immediately visible.

Tax ID verification

Middesk confirms that the business name and EIN on the application match IRS records. A mismatch is one of the most common signals of a synthetic or misrepresented business, and catching it before onboarding saves a great deal of work later.

People and ownership

Officers and directors listed in state filings can be compared with the owners and signers named on the application. When the person signing our agreement does not appear anywhere in the company's official records, we want to understand why.

Watchlist and sanctions screening

Businesses and associated people are screened against sanctions and watchlists such as OFAC. For a payments company, onboarding a sanctioned party is not a risk we can accept, so this check has to be consistent and documented every time.

Address intelligence

Middesk tells us whether an address is a real business location, a registered agent's office, a virtual office or mail drop, or a residence. None of these is automatically a problem, since many small businesses legitimately work from home, but an address that does not match the story on the application is something we look at more closely.

Industry and online presence

Middesk's industry classification and website signals help us compare what a merchant says it sells with what it appears to sell. In high risk, a gap between the declared business and the real one is often where transaction laundering starts.

Ongoing monitoring

KYB is not a one-time event. A business that was in good standing at onboarding can be dissolved, change officers or fall out of compliance months later. Middesk can monitor businesses after approval and alert us to changes, so our risk view stays current through the life of the relationship rather than freezing on the day we said yes.

The advantages for a high-risk gateway

Putting these checks together has made a real difference to how we work.

1. Speed without cutting corners. Checks that once meant manually searching state registries one by one now come back in a single structured report. Good merchants are onboarded faster, which matters in a competitive market.
2. Consistency. Every application goes through the same checks in the same way. That removes variation between analysts and gives us a defensible, repeatable process.
3. An audit trail. Each verification is recorded with its sources and results. When our sponsor bank, a card network or an auditor asks how we approved a merchant, we can show exactly what we checked and what we found.
4. Fraud caught earlier. The cheapest fraud to deal with is the fraud that never reaches a live merchant account. Discrepancies in registration, tax ID, ownership or address surface before any volume is processed.
5. Analysts focused where they add value. Automation handles the routine verification, so our compliance team spends its time on judgement calls rather than data gathering.

How we use the results: proceed, or look closer

Middesk does not make our decisions for us, and we would not want it to. Its results are one factor in our onboarding process, alongside underwriting, processing history, the owner's KYC, website review and the merchant's business model.

The way we use it is straightforward:

• When the KYB results are clean and consistent with the application, with the entity active and in good standing, the tax ID matched, owners appearing in official filings, no watchlist hits and a credible address and online presence, the application can move forward through the rest of underwriting with confidence.
• When the results raise questions, such as a tax ID mismatch, a recently formed or inactive entity, owners who do not appear in filings, a potential watchlist match, an address that does not fit the business, or a website that does not match the declared industry, the application is routed for closer human supervision.

Closer review does not mean rejection. Many flags have innocent explanations: a recent restructuring, a name change, a founder who works from home, or a common name producing a false-positive watchlist hit. In those cases an experienced analyst asks for supporting documents, speaks with the merchant and makes a decision based on the full picture. What the KYB signal does is make sure that the right applications get human attention, rather than spreading that attention thinly across every file.

This balance matters. Automating everything would expose us to the risk of rubber-stamping applications that need judgement. Reviewing everything manually would slow down good merchants and tire out the team. Using KYB results to decide where human attention goes gives us both speed and care.

Closing thoughts

High-risk merchants deserve access to reliable payment processing, and serving them responsibly is what Edge Payment Technologies is built for. Doing that well depends on knowing exactly who we are doing business with. KYB with Middesk gives us independent, authoritative evidence about each business, catches the warning signs of fraud early, and tells us when an application can proceed and when it needs a closer look from a person.

For anyone building onboarding or compliance tooling at a payments company, my advice is simple: treat KYB as a risk signal, not a checkbox. Verify against primary sources, keep monitoring after approval, and let the data tell your team where to spend its judgement.