CardConnect Complaints: The 7 Issues Merchants Report Most Often

Diego Reyes opened his CardConnect statement on a Wednesday in March. He had two hundred leather wallets waiting to ship and was running payroll for three part-time stitchers that week. What he expected to see was the usual processing fee — around 2.6% of the $48,000 he had run through CardConnect that month. What he actually saw was $430 more than that, split across three line items he had never seen on any previous statement.
When he called CardConnect’s customer service number, the representative told him to download the Program Guide from the merchant portal. Diego had been with CardConnect for three years and had never heard of a Program Guide. He logged in, found a 50-page PDF in fine print, and read the first fifteen pages before he realized what it was: the document that governed every fee CardConnect could charge him, including the three that had just appeared on his statement.
Diego’s experience is not unusual. It is one of seven issues that show up in CardConnect complaints over and over again. Some of them are the reason CardConnect is currently defending a federal class action. Some of them are the reason thousands of merchants already settled a prior class action for $7.65 million in 2020. All of them are issues any CardConnect merchant should know how to spot on their own statement before deciding whether they can live with the relationship.
The Program Guide Behind Most CardConnect Complaints
The single most common thread running through recent CardConnect complaints is a document called the Program Guide. It is typically referenced — but not provided — at the moment a merchant signs the Merchant Agreement. The Program Guide is separate, roughly 50 pages, written in small-print legalese, and according to a federal class action filed in July 2024, it is where CardConnect claims the right to add fees and raise rates that were never disclosed at signing.
The 2024 case is Richard E. Obringer PAC v. CardConnect Corp., filed in the U.S. District Court for the Eastern District of Pennsylvania. The plaintiff is a physician assistant office that signed up for CardConnect in 2018. According to the complaint, the merchant never received a copy of the Program Guide, requested one in writing, and was ignored. The suit alleges the cardconnect program guide purports to let the company raise rates with thirty days’ notice and “unilateral and unlimited discretion” to impose charges vastly different from what was in the Merchant Agreement.
Request your Program Guide in writing, by email, with a timestamp. If you did not receive one at signing, that fact is material — both to your current billing and, if you fit the class definition, to your potential standing in the Obringer litigation. Keep the request and any response.
Rate Creep in Month Thirteen
A cardconnect rate increase almost never arrives in month one. It arrives in month thirteen, or month eighteen, or month twenty-four — after the relationship is established, after the merchant has stopped checking the effective rate, after the original sales representative has moved to a different portfolio. The increase typically comes in the form of a “change of terms” notice the merchant either does not read or does not recognize as a rate action. Thirty days later, the new rate takes effect.
The mechanism that makes this legal, according to CardConnect, is the same Program Guide from Issue 1. The Program Guide grants the thirty-day notification window. Once that window passes, the new rate applies to every transaction. This is why CardConnect complaints frequently describe a merchant who “signed at 2.4%” and is now paying 2.9% — the path from one to the other ran through a document they never saw and a notice they did not read as rate-bearing.
Pull your first full month’s statement and your most recent statement. Calculate your effective rate on each: total fees divided by total card volume. Compare. If the gap is more than 15 basis points without a corresponding change in your card mix, you are looking at the rate creep pattern.
The PCI Non-Compliance Fee That Appears on Its Own
The cardconnect pci fee has been a focal point of CardConnect complaints for the better part of a decade. In the 2020 class action settlement, it was one of three specifically named “subject fees” — a $19.95 monthly charge called the PCI Non Comp Fee. It triggers automatically when a merchant does not complete the annual Self-Assessment Questionnaire, a form that takes about twenty minutes and that many merchants do not know exists.
The structure is worth understanding because it is not unique to CardConnect. Every processor assesses a PCI non-compliance fee on merchants who do not attest to compliance annually. What separates CardConnect from better-behaved processors is the aggressiveness of the charge and the dim trail of notification that precedes it. The fee appears on the statement; the questionnaire link usually does not.
Log in to your CardConnect merchant portal, locate the PCI compliance section, and complete the Self-Assessment Questionnaire. Most small merchants qualify for the short version. The non-compliance fee should drop from the next statement. More on the mechanics in our PCI compliance fee explainer.
The Customer Service Maze: Fiserv, CardPointe, or the ISO
CardConnect customer service is genuinely hard to reach, and the difficulty is not a coincidence of staffing. CardConnect is owned by Fiserv. Its gateway product is CardPointe. Most merchants were sold the account by an Independent Sales Organization (ISO) — a third-party reseller with its own support line. When something goes wrong, the merchant has three phone numbers to choose from, and each one can credibly tell them to call one of the other two.
The pattern in CardConnect complaints about customer service is almost always the same: a merchant calls the main number, gets routed through a tree, reaches a representative who takes down the issue, and is told someone will call back. No one calls back. When the merchant calls again, they reach a different representative with no record of the prior conversation. Escalation requires an escalation request. Escalation requests go into the same queue.
The only reliable version of this workflow involves keeping three pieces of information in one place: your Merchant ID (MID), the name and direct phone number of your original ISO sales representative, and your Fiserv case number if one was ever issued. Use the ISO first — they have a financial interest in your account staying open that the main support line does not.
Statements That Require a Decoder Ring
If you want to understand why cardconnect hidden fees is a search term with real volume — and why most CardConnect complaints about opaque billing trace back here — read a CardConnect statement line by line. The 2020 class action settlement named three specific line items that merchants alleged had never been disclosed to them: the “Pulse Fee” at $9 annually, the “Cardpointe Fee” at $15 monthly, and the “PCI Non Comp Fee” at $19.95 monthly. All three still appear on some CardConnect statements today, under the same names or close variants.
Beyond those three, the typical CardConnect statement layers a batch fee, a monthly minimum fee if card volume falls below a threshold, a voice authorization fee, an address verification service (AVS) fee, and on some statements an unexplained “admin fee” or “infrastructure fee.” None of these are large individually. Aggregated, they commonly run sixty to a hundred dollars a month on top of the transaction percentage, and they are the reason a merchant quoted at 2.4% can end up with an effective rate closer to 2.9% without a single rate change ever showing up in writing.
Guidance on reading a statement end to end is in our merchant processing statement walkthrough. For CPAs looking at a client’s statements at tax time, the line-item guide for tax professionals covers the same ground from an audit angle.
Long Contracts With Teeth on the Way Out
The typical cardconnect contract is a three-year initial term with a one-year automatic renewal unless the merchant provides written notice within a specified window before the renewal date. The window is usually ninety days, sometimes sixty. Miss it, and the contract renews for another year. Try to leave during a live term, and the early termination fee applies — commonly $250 to $500, occasionally higher on accounts that were quoted aggressive promotional rates.
CardConnect complaints about contract teeth almost always come from merchants who did not realize the auto-renewal clause was active, or who assumed the ETF had expired when the initial three years ended. In most cases, the ETF does not expire — it resets with each auto-renewal. The clock starts over.
The question is almost never “can I leave?” — it is “does the savings from leaving cover the ETF?” Our early termination fee breakdown and the ETF breakeven calculator run the math for you. For most merchants paying a rate 30 basis points or more above market, the ETF pays for itself inside six months.
The CardPointe Gateway Lock-In
Cardpointe complaints overlap substantially with CardConnect complaints because CardPointe is the gateway product CardConnect sells. For merchants running card-not-present volume — online, phone orders, recurring billing — CardPointe stores customer card data as tokens, which is the industry-standard way to handle compliance while still letting a merchant charge a returning customer without asking for the card number again.
The problem is portability. When a merchant leaves CardConnect for a different processor, CardPointe tokens do not come with them. The new processor cannot read the old tokens. Depending on how much recurring billing a merchant runs, this can mean re-tokenizing hundreds or thousands of customer records — in practice, asking every customer to re-enter their card data on the new system. That friction is the quiet lock-in, and it surfaces in CardConnect complaints from subscription businesses more than any other vertical. Merchants who might otherwise leave stay because the switching cost for their customer base feels too high.
There are ways to handle this. Some processors will accept a one-time encrypted export of card data for re-tokenization on the new gateway, subject to a formal PCI-compliant transfer process. Others can import account-updater data that reduces the customer-facing ask. The option that does not exist is “the new processor reads the old tokens directly.” Plan for the transition as a project, not a switch.
The Structural Cause Behind All Seven
Seven issues sounds like seven problems. The pattern across CardConnect complaints is that they are not seven problems. They are one problem with seven surfaces. The underlying structure is an onboarding model built around ISO resellers, a contractual framework governed by a Program Guide most merchants never read, and a fee architecture that layers small charges across multiple line items — each small enough to ignore individually, each large enough to matter in aggregate.
Diego did not sue anyone. He did four things in sequence. He requested his Program Guide in writing and got a copy. He completed the PCI Self-Assessment Questionnaire. He called the ISO that had originally sold him the account — not the main support line — and pushed them to document the $430 in surprise fees on his March statement. And he started a statement-by-statement comparison so that any future rate movement would show up in thirty days rather than thirteen months.
The four steps took him about two hours total. The $430 in March did not come back. The pattern of fee layering going forward did stop, at least for the next two statements. Whether that holds for the next twelve months is a question every merchant in a similar position has to answer on their own statements, not on someone else’s. The only version of CardConnect complaints that actually get resolved are the ones where the merchant did the reading CardConnect was supposed to do at signing.
Frequently Asked Questions
The Program Guide is a separate document — typically around 50 pages of small-print legalese — referenced but not provided when a merchant signs the Merchant Agreement. The 2024 federal class action Obringer v. CardConnect Corp. alleges the Program Guide is where CardConnect claims the right to add fees and raise rates never disclosed at signing, with thirty days notice and “unilateral and unlimited discretion” to impose charges different from the Merchant Agreement. The single most useful step a current merchant can take is to request the Program Guide in writing, by timestamped email. If you didn’t receive one at signing, that fact is material to both current billing and any future dispute.
A CardConnect rate increase almost never arrives in month one. It arrives in month thirteen, eighteen, or twenty-four — after the relationship is established, after the merchant has stopped checking the effective rate, after the original rep has moved on. It typically comes as a “change of terms” notice the merchant either doesn’t read or doesn’t recognize as a rate action; thirty days later the new rate takes effect, via the Program Guide’s thirty-day notification window. To verify, pull your first full month’s statement and your most recent, then calculate the effective rate (total fees divided by total card volume) on each. A gap over 15 basis points without a change in card mix is the rate-creep pattern.
The difficulty isn’t a staffing coincidence. CardConnect is owned by Fiserv; its gateway product is CardPointe; most merchants were sold the account by an ISO — a third-party reseller with its own support line. When something goes wrong, the merchant has three phone numbers, and each can credibly tell them to call one of the other two. The reliable workflow is keeping three things in one place: your Merchant ID (MID), the name and direct number of your original ISO rep, and your Fiserv case number if one was issued. Use the ISO first — they have a financial interest in your account staying open and the relationships to escalate within Fiserv that an inbound caller doesn’t.
CardPointe is the gateway CardConnect sells. For card-not-present volume — online, phone, recurring billing — it stores customer card data as tokens. The portability problem: when a merchant leaves CardConnect, CardPointe tokens don’t come with them, and the new processor can’t read them. For subscription or recurring-billing merchants, that can mean re-tokenizing hundreds or thousands of records — asking every customer to re-enter their card. That switching cost is the quiet lock-in. Some processors will accept a one-time encrypted export of card data for re-tokenization under a formal PCI-compliant transfer. Confirm token portability or transfer support before committing to the switch.
The CardConnect ETF commonly runs $250 to $500, occasionally higher on accounts quoted aggressive promotional rates. The contract is typically a three-year initial term with one-year automatic renewal unless written notice is provided 60 to 90 days before the renewal date. The ETF doesn’t expire when the initial three years end — it resets with each auto-renewal. The question is almost never “can I leave” but “does the savings from leaving cover the ETF.” For most merchants paying 30 basis points or more above market, the ETF pays for itself inside six months. Run the breakeven math against current quotes before assuming the ETF is the wall.
More on CardConnect and the Switching Decision
If You Recognize More Than Two of These on Your Own Statement
Diego’s March statement hit three of the seven in one month. If yours is hitting more than two, the fee pattern is probably not an accident, and it is usually cheaper to document it on paper before the next statement cycle than after. We will read your current CardConnect or CardPointe statement line by line, name the fees that are recoverable, and give you the math on whether switching clears the ETF. No obligation, no sales pressure.
Request Your Free Statement ReviewNo obligation • No pressure • Response within one business day
Sources: Obringer v. CardConnect Corp., E.D. Pa. 2:24-cv-03034 • Consumer Financial Protection Bureau — small business merchant guidance