Every business that accepts cards has to protect card data and revalidate PCI compliance each year. Here's what applies to you, which questionnaire to fill out, and exactly how Tampa Bay Pay merchants complete it.
Need help now? Call or text 727-732-3292
Most Tampa Bay Pay card accounts use either the iAccess or the InStore portal. Your welcome email or statement says which one you have. Call PCI Customer Support for a guided walkthrough, or complete it yourself online.
Not sure which portal you have, or on a different processor? Call Tampa Bay Pay and we'll point you in the right direction. All your portal logins are also on our Merchant Logins page.
Call (727) 732-3292The Payment Card Industry Data Security Standard (PCI DSS) is set by the PCI Security Standards Council, founded by the major card brands. It applies to every business that accepts, processes, transmits, or stores card data, from a single food truck to a national chain.
It covers in-person, online, and phone payments alike. If card data passes through your business in any way, PCI applies, and you validate it once a year, usually with a Self-Assessment Questionnaire (SAQ).
The current version is PCI DSS v4.0.1. Version 3.2.1 has been retired, and all v4.0.1 requirements have been mandatory since March 31, 2025.
Those six goals break down into 12 core requirements.
Each card brand assigns merchants a level based on annual transaction volume. The levels shown here are Visa's; Mastercard's are similar, and American Express and Discover use their own thresholds.
Most small businesses are Level 4. For Level 4, your processor decides what you submit, which is usually an annual SAQ, plus quarterly network scans if your SAQ calls for them.
Every SAQ except SAQ D also requires that you don't store card data electronically. Using the wrong SAQ means your validation doesn't cover your real setup, so ask if you're unsure.
E-commerce or phone/mail orders fully outsourced to a PCI-compliant provider, such as a hosted payment page
E-commerce where your website controls part of the payment page, but card data goes to a compliant provider
Imprint machines or standalone dial-out terminals with no internet connection
Standalone, PCI-approved terminals with an IP connection to the processor
Payment application systems connected to the internet, with no electronic card data storage
A hosted virtual terminal, keyed one transaction at a time on an isolated computer
Only hardware terminals in a PCI-listed point-to-point encryption (P2PE) solution
A PCI-listed software-based PIN entry (SPoC) solution, such as an approved phone or tablet setup
Everything else, including any business that stores card data electronically
These come up again and again. None of them is complicated, and all of them matter.
Change default router and admin passwords, keep guest Wi-Fi separate from payment devices, use strong Wi-Fi encryption, and keep POS software updated.
CVV codes, PINs, and full stripe or chip data can never be stored after authorization. A stored card number has to be made unreadable.
PCI requires a unique ID for each person with access. No shared "Manager" logins, and remove access as soon as someone leaves.
Don't write card numbers down. Key them straight into a virtual terminal, or text the customer a payment link.
Your gateway's customer vault stores a token, not the card, so you can charge again without keeping card numbers.
A hosted payment page keeps card data off your website, which usually means a shorter SAQ.
PCI is annual. A new POS, website, or network change can change which SAQ applies, so update it when your setup changes.
Processors set these fees, and paying them doesn't make you compliant. Completing your validation does.
Yes. Every business that accepts payment cards must comply with the PCI Data Security Standard (PCI DSS) and revalidate every year. That includes card payments taken in person, online, and over the phone.
Most Tampa Bay Pay merchants complete PCI through the portal tied to their account. For iAccess accounts, call PCI Customer Support at (877) 277-0998 or complete it yourself at pciapply.com/ipmt. For InStore Portal accounts, call (877) 276-9929 or complete it yourself at pciapply.com/paymentprocessing. Not sure which portal you have, or on a different processor? Call us at (727) 732-3292 and we'll point you in the right direction.
Levels are set by each card brand based on annual transaction volume. For Visa, Level 1 is over 6 million transactions a year, Level 2 is 1 to 6 million, Level 3 is 20,000 to 1 million e-commerce transactions, and Level 4 is fewer than 20,000 e-commerce transactions plus all other merchants processing up to 1 million transactions. Most small businesses are Level 4, and your processor sets exactly what Level 4 merchants need to submit.
It depends on how you take cards. Under PCI DSS v4.0.1 there are nine SAQs for merchants: A, A-EP, B, B-IP, C, C-VT, P2PE, SPoC, and D. For example, SAQ B-IP covers standalone IP-connected terminals, SAQ C-VT covers a hosted virtual terminal used on an isolated computer, and SAQ A covers e-commerce that's fully outsourced to a compliant provider. If you're not sure, ask before you start, because the wrong SAQ doesn't validate your setup.
Many processors charge a monthly non-compliance fee until you complete your annual validation. The fee is set by the processor, not the card brands, and paying it doesn't make you compliant. Completing your SAQ is what stops it.
No. An approved terminal is one piece. You still need to complete your SAQ, secure your network, use unique logins, and handle card data correctly.
Never store the CVV or CVC code, PIN, or full magnetic-stripe or chip data after a payment is authorized, even if it's encrypted. If you need to charge a customer again, use your gateway's secure customer vault, which stores a token instead of the card number, rather than keeping cards in a spreadsheet, CRM, or on paper.
PCI DSS v4.0.1. Version 3.2.1 has been retired, and all v4.0.1 requirements have been mandatory since March 31, 2025.
If you're not sure which portal you use, which SAQ applies, or why there's a PCI fee on your statement, call us. We'll point you in the right direction so you're not guessing.
Weekdays until 7 PM ET · English & Spanish support
Tampa Bay businesses share their experience working with Tampa Bay Pay — from setup through ongoing support.
Founder Zac Gottlieb joined The Paycast Network to talk transparency, interchange, and what it really takes to build a payments brand local businesses trust.
Don't take our word for it — here's what local business owners say after switching to Tampa Bay Pay.