MerchantE and the last mile of getting paid

Imagine a distributor selling replacement parts. The customer pays online. Somewhere else, an invoice waits to be closed, a bank account waits for its deposit, and a finance employee waits to understand which payment belongs where. The checkout has done its job. The business still has work to do.

That ordinary gap is where MerchantE becomes interesting. The company supplies payment processing, acquiring, gateway technology, and software connections. Its customers include mid-market businesses and the software companies serving them. The product is partly the ability to accept money, partly the ability to make that money intelligible.

01 A bank’s cancelled projects

MerchantE began as Merchant e-Solutions in 1999. Sharif Bayyari had run Bank of America Merchant Services. Jim Aviles worked alongside him. Their account of leaving, published in The Green Sheet, turns on a surprisingly familiar corporate event: management changed the priorities.

Aviles recalled being told that the development work would stop. The problem, in the founders’ telling, was losing the freedom to invest in the merchant business. Bayyari left, and colleagues followed. They built a company around bringing payment capabilities together.

This gives the origin story a useful specificity. The founding disagreement concerned who controlled the infrastructure and its development. More than two decades later, MerchantE still makes infrastructure ownership part of its pitch.

“all of your product development projects have been cancelled”

Jim Aviles, recalling the decision that preceded the founders’ departure

02 Follow the payment past the button

A payment gateway accepts transaction information and passes it into the processing system. Acquiring connects the merchant to the card-payment system. Reporting gives the business a record it can use. MerchantE combines front- and back-end processing with direct connectivity to major card brands.

Its developer portal makes that scope concrete. Alongside the Payment Gateway API sit tools for account updates, reporting, batch processing, split funding, and sub-merchant management. An ACH API supports payments using checking-account information. Each entry points to another piece of work a software company might otherwise need to arrange.

For the distributor, that might mean offering online payment while keeping useful transaction data available to the finance team. For a software vendor, it means connecting payment capabilities to an existing application. The appeal is having fewer disconnected pieces to operate.

There is a maintenance story here, too. The Account Updater Service is intended to keep stored card details current for recurring payments. Reporting endpoints let developers bring transaction information into their own tools. These capabilities are less photogenic than a checkout screen, but they address the work that returns every billing cycle.

03 The invoice gets a doorbell

Consider MerchantE Invoice, launched in June 2021. Its premise was direct: send an electronic invoice with a route to a secure payment page. Product materials describe card and ACH acceptance, recurring billing, reminders, and a dashboard for receivables.

Those details matter because sending a bill and collecting it are different tasks. A link puts the next action beside the amount due. A reminder gives the task another chance to reach someone’s attention. A dashboard helps the seller see what remains unpaid. None guarantees a punctual customer; each removes a little clerical friction.

For B2B transactions, information has another role. MerchantE documents support for Level II and III processing, where eligible commercial-card transactions carry additional details. Passing the required data can help qualify a payment for reduced interchange rates. Eligibility and the acceptance method matter; a wholesale business cannot assume every transaction qualifies.

04 The division that changed hands

MerchantE’s history requires some careful sorting. Cielo acquired the business in 2012. Integrum bought it from Cielo in 2022. That November, Opn announced its own acquisition, pairing MerchantE’s U.S. processing capabilities with its payments business in Japan and Southeast Asia.

The acquisition announcement put the combined businesses above $19 billion in payment volume and 20,000 businesses in 2022. Those figures describe the combination. They are not a current count of MerchantE customers.

In July 2024, Fortis acquired MerchantE’s NetSuite payments division, whose integration history reached back to 2004. A buyer following an old MerchantE NetSuite recommendation therefore needs to establish which company supplies the service today.

The Opn deal also generated litigation. An August 2025 Delaware opinion records $325 million payable at closing and another $50 million deferred. The court dismissed the buyer’s fraud counterclaim against the seller and aiding-and-abetting claim against Integrum. The allegations should not be mistaken for findings of wrongdoing.

05 Ask for the whole bill

MerchantE’s Adobe Commerce marketplace listing describes customized processing pricing. That makes evaluation a conversation about a particular business: transaction volume, payment channels, integration needs, and applicable fees. A quoted rate alone cannot describe all the work involved.

There are credible alternatives. Stripe and Adyen compete for online and platform payments; Fiserv and Global Payments serve merchant acquiring. For ERP-centered workflows, providers include Fortis and Versapay. MerchantE’s case rests on the fit between its processing infrastructure and the customer’s operational needs.

A business needing only a straightforward checkout may put little value on that breadth. A company with difficult invoice matching, several payment channels, or embedded-payment ambitions has more reason to investigate. Support, funding conditions, and the cost of integration deserve a place in the demonstration.

The useful lesson is easy to copy: follow one invoice all the way through. Watch the customer pay. Watch the payment become a deposit. Watch someone match the records. Then ask how many people, systems, and exceptions were needed. That is where a payment provider earns its place.