Twenty Vermont businesses said yes. Beginning in 2010, Payment Systems Corp. called local merchants, arranged sales visits and offered a familiar proposition: spend less to accept credit cards. There would be processing services. There would be equipment. There would be savings. But inside that attractive arithmetic was a word with considerable power: “qualified.” Which cards qualified, and which cards customers actually carried, would become the expensive part of the story.
- The business: payment acceptance, terminals and merchant support.
- The catch: a qualified-card rate could leave other transactions costing more.
- The lesson: compare the whole bill, including the lease.
- The status: a historical business, with former merchants transferred to i3 Verticals.
01 / A checkout counter in a suitcase
Payment Systems Corp., also known as Merchant Processing Solutions, was established in 2007. Its market was the everyday business of getting paid. A shop needed card acceptance. A restaurant needed a terminal. A merchant selling through a website needed a way to connect an online order to a payment. The company assembled those needs into a merchant-services offering sold across the United States.
Its expertise lay in assembling and distributing payment services. Its company description listed banking and card-network relationships, equipment leasing, website integration, gift cards, private-label cards and PCI compliance products. CardFellow described it as a registered ISO and MSP of Wells Fargo Bank. Those intermediary roles help explain its place in the market: a merchant-facing business connecting customers to a larger payments system.
The hardware made that relationship tangible. Historical equipment listings included VeriFone and First Data terminals. MobilePay offered smartphone acceptance. Virtual-terminal and e-commerce tools extended payment entry to a computer or website. The portfolio also covered checks, gift cards and an in-store ATM option. A merchant could buy access to several ways of collecting money through one sales relationship.
That breadth was its competitive proposition. The company sold a combination of acceptance, equipment and support to businesses with different checkout needs. Its model attached continuing processing and lease charges to the relationship. For the merchant, convenience therefore had to be assessed over time. A useful terminal on installation day and an economical agreement over its full term are separate questions. The business owner needed an answer to both before the salesperson left.
Historical offering. Service map, not a diagram of funds flow.
02 / The word doing the work
A bundle like that has an obvious appeal. The proprietor can spend less time choosing separate systems. But comparing bundles creates a problem: the products are visible, while their combined cost takes calculation. Processing charges, equipment commitments and additional fees must eventually meet on the same piece of paper. A low number at the top of a proposal cannot perform that calculation by itself.
Consider the historical MobilePay price listing: 1.00 percent for qualified swiped transactions, plus nine cents per transaction and a $150 activation fee. A hypothetical $100 qualifying sale therefore produces $1.09 in those transaction charges, before other applicable costs. The qualification matters. Treating the percentage as a price for every card would change the meaning of the offer.
Vermont’s 2014 account exposed that distinction. The attorney general alleged that promised savings depended on merchants accepting only qualified, non-rewards cards. Rates for many participating businesses went from one percent to 3.79 percent. The settlement required $169,568 in restitution and $100,000 to the state. It also restricted savings claims to calculations covering all cards. These were settlement terms resolving allegations, rather than a trial verdict.
03 / The people behind the pitch
The machinery of acquiring merchants was human. The company maintained offices in several cities, including Los Angeles, Dallas and Orlando. Its surviving YouTube channel puts a face on that distribution network. Alongside appointment-feedback and Salesforce tutorials sit birthday greetings, Halloween clips and a video titled “Tie Cutting Ceremony: Andrew.” It is a surprisingly informal archive for a business selling financial infrastructure.

Employee recollections add texture, with the usual limits of individual testimony. Indeed reviews describe travel, commissions, incentives and friendly colleagues; others describe pressure and disorganization. Together with the training archive, they suggest a sales-centered workplace. They do not establish a single experience shared by everyone. They do help explain how a payment bundle reached a small business: someone made an appointment, then someone made a pitch.
04 / An acquisition, then a long tail
Mergr records an i3 Verticals acquisition of Payment Systems in June 2014. CardFellow now labels its company entry historical and says i3 Verticals handles the former merchants. The product catalog belongs to that earlier business. Reading it as a present-day invitation to sign up would miss the ending.
The disputes continued beyond the transaction. In 2016, Expert Auto Repair and another plaintiff brought a class action against i3 Verticals as an alleged successor to Merchant Processing Solutions. They alleged unfair sales practices and improper fees. i3 Verticals later disclosed a $995,000 settlement, funded on April 8, 2019, and reported the matter concluded. That disclosure records a resolution; it does not turn every allegation into a proven fact.
05 / Bring your own arithmetic
What can a merchant copy from this history? Start a comparison with an actual month of transactions. Ask each provider to calculate its charges against those same sales, including the same card mix. Add the equipment cost, recurring charges and any exit obligations. Keep the processing agreement beside the lease. The exercise makes it harder for different assumptions to masquerade as different prices.
A useful question“What would your complete bill have been for my actual transactions last month?”
A service bundle can be useful when its tools fit the business and its obligations are understood. The calculation becomes unreliable when it assumes customers will carry different cards, omits a continuing lease or prices a service the merchant will barely use. Payment Systems Corp.’s history leaves a concrete test for the next sales visit: put the proposal beside the transactions. Then do the arithmetic.
Historical web address: paysysco.com ↗