The moment a customer taps “pay,” the transaction looks finished. A receipt appears. A confirmation email begins its short trip. Somewhere, a dashboard adds one to today’s sales. But for the merchant, the money has only begun to move. It passes through a gateway, a processor, card networks, banks, risk controls, a batch, and finally a deposit. Each stop creates data. Each handoff creates another place for ambiguity to hide. Craig Gass has built a career in that gap between the appearance of payment and the arrival of cash.
His shorthand for the problem is almost aggressively plain: Where is my money? It is the question beneath settlement reports, recurring billing, merchant underwriting, disputes, and embedded finance. It is also the question that turned a lawyer into an operator and, in 2014, helped animate Qualpay, the San Mateo payments company he co-founded with a group of industry veterans.
The origin is less cinematic than most founder stories. There was no garage mythology or dramatic consumer epiphany. Gass had spent years working with financial institutions and payments businesses, including BA Merchant Services and Merchant e-Solutions. He began as in-house counsel. Over time, proximity to management became a desire to join it. He went back to school for an MBA at the University of Oregon, adding it to a political science degree from Washington State University and a law degree from Willamette University College of Law.
“Sometimes the solution is a process not a single answer.”Craig Gass on the lesson he carried from law into management
01 / The operator’s educationBreak the problem into parts
A line from Francis of Assisi, passed to him by his wife, gave Gass a way to describe his operating method: start with what is necessary, move to what is possible, and let the impossible become a sequence rather than a wall. His interpretation was distinctly lawyerly. Separate a problem into issues. Work them one at a time. Do not demand that a complicated system yield one magical answer.
Payments rewards that temperament. A transaction is both software and contract, customer experience and risk decision, a moment measured in milliseconds and a financial obligation that can remain contested for months. Gass’s career sat across those boundaries. The law taught him to find the clauses and exceptions. Management made him responsible for what happened after the analysis.
At Qualpay, the parts became product architecture. The company brought a merchant account and payment gateway into the same cloud platform, then surrounded them with reporting, recurring billing, tokenized data, a virtual terminal, dispute tools, ACH capability, and APIs. The pitch was not that any one piece was novel. The pitch was that a merchant should not need to stitch together several vendors to follow a sale into the bank.
02 / A collapsing mapWhen every channel became one store
In 2016, Gass sat down for a live conversation about omnichannel retail. The word sounded technical, but the customer behavior was already ordinary. People researched on a phone, bought on a laptop, and returned in a store. They expected prices, promotions, and service to survive the trip. Merchants, meanwhile, often had a different payment system behind each door.
Gass argued for a centralized payment experience inside one merchant account. The important artifact was not the transaction alone, but the shared record around it. With channels connected, a business could recognize purchase history, handle a return without detective work, and see the economics of the whole customer rather than one isolated checkout.
“The key to omnichannel is being able to do all of it in a single merchant account.”Craig Gass, 2016
The same thinking shaped his writing about subscriptions. Recurring revenue looks serene on a spreadsheet, yet its mechanics are full of small cliffs. Cards expire. Banks replace compromised numbers. A customer who still wants the service can disappear into involuntary churn because one credential went stale. Account-updater services and flexible recurring billing turn those cliffs into background maintenance. The payment layer becomes part of customer retention.
This is where Gass’s legal habit and product instinct overlap. Both care about continuity. A contract should survive the foreseeable exception. A payment system should, too. The operator’s job is to anticipate the boring breakage before it becomes a customer decision.
03 / The hard chapterRisk is also a product decision
The story of a payment processor cannot stop at convenience. The same infrastructure that helps a legitimate merchant collect revenue can give a deceptive operation access to the card system. Underwriting and monitoring are not back-office formalities. They decide who gets to move money and for how long.
In 2020, the Federal Trade Commission alleged that Qualpay ignored warning signs while processing payments for MOBE, a business-coaching scheme that the agency had sued. The complaint said Qualpay processed nearly $80 million for MOBE and continued parts of the relationship despite chargeback signals and internal concerns. Qualpay settled. The order barred it from processing for business-coaching companies and certain high-risk merchants, required more careful screening and monitoring, and imposed a roughly $46.8 million judgment that was suspended because of the company’s financial condition.
The processor’s conflict
More volume creates more revenue. The very merchant generating that volume may also create consumer harm, chargebacks, network exposure, and legal risk.
The system works only when evidence can outweigh the income attached to an account.
The settlement is not a footnote to Gass’s operating story. It is the sharpest version of the question his company was built to answer. Knowing where the money is matters. Knowing why it is moving, who is harmed, and when it should stop matters just as much. Visibility without judgment is merely a better dashboard.
There is no neat lesson to paste over that record. There is, instead, a durable constraint on payment leadership: speed and scrutiny must occupy the same system. A processor needs to welcome good merchants quickly while treating inconvenient evidence as more than friction to revenue.
04 / The second actFrom a platform to specific industries
Qualpay kept building. In 2022, Synovus announced an agreement to take a 60 percent ownership interest in the company. The bank also planned to use Qualpay’s technology in Maast, an embedded-finance initiative intended to let software providers offer payments and banking features through one integration. For Gass, it was a move from payments platform toward platform-as-a-service: the machinery would sit inside someone else’s product and brand.
At the same time, Qualpay became more specific. Its integrations reached energy businesses that deliver propane and heating oil, operations where seasonal billing, card updating, interchange costs, and back-office software have their own peculiar rhythm. In 2025 it announced an integration with DRM, whose software serves hundreds of fuel and propane dealers. In July 2026, Qualpay became an endorsed payments partner of the National Waste & Recycling Association, offering tools for recurring billing, fleet-oriented operations, reconciliation, and reporting.
Gass and a team of payments veterans co-found Qualpay.
The FTC settlement adds restrictions and enhanced monitoring obligations.
Synovus agrees to acquire a 60 percent interest and connect Qualpay to an embedded-finance strategy.
The DRM integration extends the platform into energy marketers’ back offices.
The NWRA partnership brings Qualpay deeper into waste and recycling operations.
The shift is revealing. Generic infrastructure benefits from scale, but merchants live in particulars. A propane dealer, a software vendor, and a waste hauler may all accept cards, yet their calendars, customer relationships, and reconciliation problems are not interchangeable. One core platform has to respect different last miles.
05 / Collective leadershipThe CEO among co-founders
Gass has said that becoming CEO required a thoughtful approach because he was leading fellow co-founders. Authority could not depend on pretending the surrounding experience did not exist. He describes effective leadership in terms of the collective, the power of the team, difficult questions, empathy, and thorough analysis.
That vocabulary feels consistent with the arc of his career. He did not abandon law so much as widen the brief. The questions grew from what an agreement allowed to what a company should build, whom it should serve, which risks it should accept, and how a group of experienced peers could make a decision together.
“It’s important to consider the collective versus the individual.”Craig Gass on leading fellow co-founders
More than a decade after Qualpay opened, the company continues to make the invisible middle of commerce its subject. Recent release notes are full of unglamorous details: reporting filters, webhook behavior, ACH data, recurring-billing dates, customer vaults, and dispute statistics. This is what infrastructure looks like from inside. Progress arrives as fewer double submissions, clearer fields, faster reports, and one less reason to call support.
Gass’s public story offers no clean founder fable. It offers something more useful: an operator moving between abstraction and consequence. He learned to divide problems into parts, built a platform to reunite the parts of a payment, endured a regulatory case about the cost of inadequate scrutiny, and kept pushing the product toward industries where the details resist generic answers.
The customer still taps “pay.” The merchant still waits for cash. Between those two moments sits a set of choices about design, evidence, responsibility, and trust. Craig Gass has spent three decades working in that middle, where the quietest question on the screen can become the loudest question in the room.