Home > PCI compliance > PCI non-compliance fees
PCI non-compliance fee on your statement? How to stop it
Look at your monthly card processing statement. If you see "PCI non-compliance," "non-validation" or "PCI non-compliant fee," your processor is charging you because they have no current proof that your business protects card data. Here is what it means and how to make it go away.
The short answer
- The fee is charged by your card processor, not the government and not the card brands directly.
- It usually appears when the processor does not have a current, completed PCI Self-Assessment Questionnaire (SAQ) and, if required, a passing quarterly scan.
- It commonly runs about $20 to $100 or more per month, which can add up to well over $1,000 a year.
- The usual fix is to complete the correct questionnaire, pass any required scans, and keep them current every year.
- It is not a penalty you have to keep paying. Once your account shows compliant, the fee normally stops.
Why processors charge it
Card brands such as Visa and Mastercard require businesses that accept cards to follow the PCI Data Security Standard. Your processor is responsible for making sure its merchants do. When they have no proof on file, they charge a non-compliance fee to cover their risk and to push merchants to finish the paperwork. Many businesses pay it for years without knowing what it is.
How to find it on your statement
- Look in the fees or monthly charges section, not the per-transaction rates.
- Common names: "PCI non-compliance," "PCI non-validation," "non-compliant fee," "PCI program fee not validated."
- Do not confuse it with a "PCI compliance fee" or "PCI program fee," which some processors charge everyone, compliant or not. That one may stay even after you comply.
- Compare a few months. If the amount stays the same every month, it is likely a fixed monthly fee you can stop.
Steps to stop the fee
| Step | What it involves |
|---|---|
| 1. Find your PCI portal | Your processor names the company that runs it. Your statement or welcome email usually has the link. |
| 2. Pick the right questionnaire | The SAQ type depends on how you take cards: standalone terminal, POS on your network, online store or a mix. |
| 3. Answer honestly | Questions cover firewalls, passwords, updates, Wi-Fi, who can access card data and staff training. |
| 4. Fix what is not in place | Firewall, network separation, updates and written policies, as needed. |
| 5. Pass any required scans | Quarterly external scans, if your SAQ type requires them. See failed PCI scan fixes. |
| 6. Confirm with the processor | Check that your account shows compliant and that the fee is gone from the next statement. |
Keep it from coming back
- Set a reminder before the questionnaire expires each year.
- Save the portal login and your answers where the business, not one employee, can find them.
- Keep firewall and router firmware updated so scans keep passing.
- Keep card terminals on their own network. See card terminal network separation.
- Train staff to spot phishing, since the questionnaire asks about it. See phishing training.
How WENO helps you stop the fee
Questions people ask
Is the fee legal?
It is part of the merchant agreement you signed with your processor. Your agreement and fee schedule describe it. If you are unsure, ask your processor for the fee explanation in writing.
Can I get past fees refunded?
Sometimes. Some processors will credit recent months once you become compliant, but they do not have to. It is worth asking.
I only take a few cards a month. Does this apply to me?
Yes. Every business that accepts cards is expected to validate PCI compliance. Small businesses usually qualify for the simplest questionnaire.
Will switching processors fix it?
Not by itself. A new processor will ask for the same proof. Completing the questionnaire is usually faster and cheaper.
Sources
- PCI Security Standards Council: PCI DSS and Self-Assessment Questionnaires
- Visa: merchant data security requirements
General information, not legal or financial advice. Fees and requirements vary by processor and are set in your merchant agreement.
