The envelope is the clue. Look through Usio’s payment products and you find the expected machinery: bank transfers, card processing, software interfaces. Then you find printing and mailing. A company selling embedded finance also offers to put a bill in the post. That small incongruity explains more about Usio than the usual fintech vocabulary does.
A payment begins before anyone clicks “pay.” Somebody must calculate a balance, present it, collect it, reconcile it, and sometimes return it. Usio has assembled a business around those neighboring tasks. The interesting question is why a company born to put bills online eventually decided that paper belonged in the picture.
- Usio connects payment acceptance, payouts, and billing.
- Software partners bring it customers already doing business inside an application.
- Its return to printed bills shows how stubbornly practical money movement can be.
Seven people and a second attempt
In 1998, Louis Hoch and Michael Long founded the business as Billserv.com. Electronic bill presentment was its original territory. The proposition was straightforward: companies generating recurring paper bills could deliver them electronically. The economics were less cooperative.
The 2003 annual report describes continuing losses and difficulty securing capital. That July, the company sold substantially all its operating assets to Saro. It received $4.1 million at closing, with another $700,000 contingent on earnouts. By year-end, seven employees remained. Renamed Payment Data Systems, the company concentrated on electronic payments.
This was a forced narrowing of the business. Financing constraints helped determine what could survive. The distinction matters when reading any tidy corporate history: an attractive idea and a sustainable operation are separate achievements.

Seventeen years after that sale, Usio bought the assets of Information Management Solutions. The December 2020 transaction cost about $5.9 million in cash, plus warrants. IMS brought electronic billing, document handling, printing, mailing, and hundreds of customers. Management expected more than $13 million in additional annual revenue; that was the deal’s forecast, not a guaranteed outcome.
The return to billing had a different shape. By then, Usio could put collection and disbursement beside the document. A utility’s statement and its customer’s payment could belong to the same commercial relationship.
The software already has the customer
Consider a medical practice using PracticeSuite, or a booster organization using BoosterHub. Both are software partners featured by Usio. Their users already have a reason to open the application. Add payment acceptance there, and collecting money becomes part of work already underway.
Usio’s PayFac-in-a-Box supplies payment facilitation infrastructure for software applications. The software company can offer integrated payments and participate in the economics without independently building every banking, onboarding, and processing function. Usio handles the underlying payment service; responsibilities still depend on the arrangement.
partner→Merchant
workflow→Usio
payments
Put the transaction where the customer already works.
This is distribution with a useful shortcut: one software relationship can introduce a processor to many merchants. Usio’s investor materials describe a partner-focused model for both payment facilitation and ACH. It fits a market where the software vendor increasingly controls the moment a bill becomes a transaction.
Stripe Connect and Finix offer overlapping platform-payment services. Usio’s particular pitch combines that software channel with ACH expertise, prepaid programs, and document operations. Breadth is valuable when a buyer needs several of those functions. A business buying only card acceptance has a narrower comparison to make.
Let the recipient finish the job
Sending money presents another coordination problem. An organization knows what it owes. The recipient knows how they want to receive it. Requiring everyone to accept the same payment method can turn a simple refund into an administrative project.
Consumer Choice starts with payment information delivered to Usio through an API or batch file. Usio notifies recipients by email or text and lets them select a supported payout method. Options include a prepaid card, bank transfer, push-to-debit payment, or printed check. The envelope returns, this time carrying money out.
“Usio Output Solutions is one of our most reliable vendors.”
Director of Operations, Brilliant Energy
Customer testimonial published by Usio
For governments and nonprofits, the details can include merchant-category spending controls, transaction records, and physical or virtual cards. Usio features the City of Phoenix in its public materials. These are programs where access and accountability have to coexist, and a convenient digital interface is only part of the assignment.
The institutional roles also matter. Usio supplies technology and program services. Its website identifies Sunrise Banks as the issuing bank for Akimbo and Usio cards, under a Mastercard license. Buyers should understand who performs each function before treating a payment platform as a single interchangeable supplier.
Follow the costs, too
Usio earns revenue across processing, prepaid services, document operations, and interest. Revenue is distinct from the much larger sums moving through payment systems. It is also distinct from profit. In 2025, Usio reported $85.4 million in revenue, $19.7 million in gross profit, and a $2.5 million net loss.
Gross profit still has to cover operating expenses. The year ended with a $2.5 million net loss.
The more recent picture improved. Second-quarter 2026 revenue reached $23.7 million, up 19% from a year earlier, with approximately $0.3 million in GAAP net income. Yet prepaid card services revenue fell 10%. Different activities inside the same company can move in opposite directions.
For a buyer, the useful lesson is to price the whole job: integration, processing, exceptions, reconciliation, and support. A software platform with little payment volume may struggle to justify the implementation. A program whose recipients need unsupported methods will need another route. Delegating payment work also requires agreement about who handles disputes and compliance.
What can another business copy? Start where customers already work. Identify the financial task immediately beside that workflow. Make it easier to finish. Usio’s unusual contribution is the willingness to include the unfashionable pieces. Sometimes the next step is an API call. Sometimes it needs a stamp.