Global Reach Internet Productions, LLC

PCI Compliant Bank Website Platform

Financial institutions that accept, process, or facilitate payment card transactions are responsible not only for their own PCI compliance but for the compliance posture of their third-party vendors. Under PCI DSS requirements and FFIEC vendor oversight guidance, a bank or credit union cannot discharge that responsibility by assuming their website platform vendor meets adequate security standards. It must be verified. SiteViz Banking has held PCI DSS certification as a service provider for over a decade and maintains documentation your institution can include in its vendor oversight program.

Your institution is responsible for your vendor's security posture

PCI DSS explicitly requires financial institutions to manage the compliance of their service providers. If a website platform vendor stores, processes, or transmits cardholder data, or operates infrastructure that could affect the security of cardholder data, that vendor's PCI compliance status becomes part of the institution's own compliance responsibility. Examiners reviewing a bank's third-party vendor risk program under GLBA Safeguards Rule requirements will expect the institution to have verified its website vendor's security certifications, not simply assumed them.

Choosing a platform vendor with a verified, documented, and continuously maintained PCI certification is one of the most direct ways to close that gap in a vendor oversight file.

What SAQ-D 3.2 certification means for your institution

SiteViz Banking is certified as a PCI DSS compliant service provider at the SAQ-D 3.2 level. SAQ-D is the most comprehensive Self-Assessment Questionnaire classification available, covering the full range of PCI DSS security requirements applicable to service providers. It applies to vendors whose scope includes application and software development, hardware, physical hosting infrastructure, web services, and shared hosting environments.

SiteViz Banking's certification scope covers all of those areas: application and software development, hardware, physical colocation space, storage, web services, shared hosting, and internet and e-commerce services. This means the certification covers the full stack of services your institution relies on when hosting its website on the platform, not a partial scope that leaves gaps for your compliance team to address separately.

Weekly scanning, not quarterly minimums

PCI DSS requires service providers to conduct vulnerability scans at minimum once every three months. SiteViz Banking runs vulnerability scans weekly. This is four times the required frequency, and the scans are conducted both by the internal team and by independent third-party security providers.

For a bank IT director building a vendor oversight file, weekly scanning with independent third-party verification represents a material improvement over a vendor that meets only the minimum PCI scanning cadence. It also means that security issues are identified and addressed on a significantly faster cycle, reducing the window between a potential vulnerability appearing and being remediated.

Documentation for your vendor oversight program

When examiners review a financial institution's third-party vendor risk program, they expect to see evidence that the institution has evaluated its vendors' security posture, not simply relied on the vendor's assertions. SiteViz Banking can provide compliance documentation to support your institution's vendor oversight file, including certification details and scanning records relevant to your review.

This documentation, combined with the SOC 2 compliance maintained across the platform, gives compliance officers and IT directors a substantive basis for completing their third-party vendor assessments rather than a gap they need to explain to examiners.

Frequently Asked Questions

Does my bank's website vendor need to be PCI compliant?

If your website vendor stores, processes, or transmits cardholder data, or operates infrastructure that could affect the security of cardholder data on your site, PCI DSS requires you to manage and verify that vendor's compliance as part of your own security program. FFIEC guidance on vendor oversight further reinforces this obligation for financial institutions. Choosing a vendor with a verified, documented PCI certification reduces your institution's exposure in that review.

What does SAQ-D 3.2 mean and why does it matter for our institution?

SAQ-D is the most comprehensive PCI Self-Assessment Questionnaire classification for service providers. It covers the full set of PCI DSS requirements applicable to vendors operating application development, hardware, hosting, web services, and shared hosting environments. SiteViz Banking's SAQ-D 3.2 certification means the entire scope of services your institution relies on is covered by the certification, with no partial-scope gaps that require separate evaluation.

How often is SiteViz Banking scanned for vulnerabilities?

SiteViz Banking runs vulnerability scans weekly, well above the quarterly minimum required by PCI DSS. Scans are conducted both internally and by independent third-party security providers, providing continuous monitoring rather than a compliance-interval review.

Can we obtain PCI compliance documentation for our vendor oversight file?

Yes. SiteViz Banking can provide compliance documentation to support your institution's third-party vendor review process. Contact the team to discuss what documentation is relevant to your specific oversight requirements.

 

A collage of Global Reach's program for PCI compliance.

 


Let’s Talk

Verifying your website vendor's PCI compliance is part of your institution's own compliance program. Confirm SiteViz Banking meets your vendor oversight requirements in a 30-minute demo.

* Indicates a required field
© 2026 Global Reach Internet Productions, LLC. All rights reserved.