PCI compliance for churches

Navigating PCI Compliance for Churches

Your church offers a giving link on its website, and maybe a kiosk in the lobby. Each one is a way donors trust your church with their card details. PCI compliance is how a church shows those details are handled with care.

In practical terms, it’s the card industry’s security standard for any organization that accepts card gifts. For churches, it usually means a yearly questionnaire through your merchant account provider, the company that processes your card gifts, and in some cases a security scan.

Whether you are a finance director, an administrator, or a pastor, you are likely fitting this in alongside a long list of other responsibilities.

This guide covers what PCI compliance is, why it applies to churches, and how to make each step easier to finish.

What is PCI compliance for churches?

PCI compliance means meeting a set of security rules for handling card payments, called the Payment Card Industry Data Security Standard (PCI DSS). It is a baseline set of technical and operational requirements for protecting payment account data, and it applies to anyone who stores, processes, or transmits that data.

The rules come from the PCI Security Standards Council, the group that writes them and keeps them current. It was founded by American Express, Discover, JCB, Mastercard, and Visa. The standard has 12 requirements covering things like network security, access to accounts, testing, and written policies.

For your church, being compliant means answering questions about your own setup and signing a statement that your answers are accurate. Your provider may call this validation or certification, so you may see either word.

Why does a church have to be PCI compliant?

A church has to be PCI compliant because it accepts card gifts, and the card brands expect every organization that does so to protect card data. The standard is meant for all organizations that handle payments, regardless of size or transaction volume.

Here is how the pieces fit. Visa, Mastercard, and the other founding card brands each run their own compliance programs, and the brands decide whether a small organization has to complete the questionnaire. Your merchant account provider is the one who asks your church to complete it.

Processors can charge a monthly non-compliance fee if the questionnaire is not completed on time. Amounts and grace periods vary by provider, so your merchant agreement is the place to check.

Beyond fees, the yearly questionnaire is a check that the basics are in place: who has access, how donors give, and how card data is handled.

Who is responsible for PCI compliance: the church, the giving platform, or the processor?

Responsibility is shared. Your giving platform and processor secure the systems that handle card data, and your church is responsible for the parts of the setup it controls.

For the church, that usually means:

  • How donors reach your giving page from your website
  • Who has a login to your giving accounts
  • Any kiosk and the internet connection it uses
  • Making sure card numbers are never written down or stored


PCI levels group providers by how much card activity they handle, and Level 1 is the highest tier. It calls for a full assessment by an independent outside assessor. 

SecureGive is a Level 1 service provider, and our partner gateways and processors are PCI compliant as well, which leaves only a small share of the work with your church. 

To see what to ask any provider, read our guide to security questions to ask your giving provider.

What are the steps to complete PCI compliance?

Most churches complete PCI compliance in five steps, and the same steps repeat each year.

  1. Find your PCI portal and login. The portal is the website where your provider hosts the questionnaire. Your login arrives when your merchant account opens, and if you need a reset, your giving platform’s support team can help.
  2. Confirm how your church accepts gifts. Online link, embedded form, kiosk, mobile app, or more than one. This decides which questionnaire you complete.
  3. Complete the questionnaire. Answer each question about your own setup. If an item does not apply, the portal lets you mark it not applicable with a short explanation.
  4. Run a scan if your setup calls for one. A scan is a security check of your website or network address. The next two sections explain when one applies.
  5. Sign and plan for next year. Sign the statement confirming your answers are accurate, which the portal calls attesting. Your church is complete once you sign, so add next year’s renewal date to your calendar.

Which questionnaire does a church complete?

The questionnaire your church completes depends on how you accept gifts. In the portal you will see them by letter: 

  • SAQ A
  • SAQ C
  • SAQ D 


SAQ stands for Self-Assessment Questionnaire, a form where you answer questions about your own setup. The letters are just labels, not abbreviations, and they run from the simplest questionnaire to the most involved.

If your church accepts gifts...
You'll see
What to expect
Online and mobile, with a hyperlink on your website
SAQ A, the shortest questionnaire
No scan
Online, with a redirect or embedded form
SAQ A
A website scan
Through a kiosk only
SAQ C, the questionnaire for internet-connected devices like a kiosk
A scan of the kiosk's internet connection
Online and through a kiosk
SAQ D, the longest questionnaire
A kiosk scan, plus a website scan if you use a redirect or embedded form

Take a church with a giving link on its website and a kiosk in the lobby. It would typically complete SAQ D. A longer questionnaire means more questions about your setup, and the portal lets you mark items that do not apply.

These are the pairings we see for churches using SecureGive with CardConnect. Text-to-give, SecureGive Tap, and check scanning do not change which questionnaire applies. Other providers may assign them differently.

If you are not sure which questionnaire fits your church, check with your merchant account provider before you begin, since they receive your completed questionnaire. 

If you use SecureGive with CardConnect, the CardPointe portal names the questionnaire during setup, and our support team is glad to confirm it with you.

When does a church need a website or network scan?

A church needs a scan if donors reach its giving page through a URL redirect or an embedded form on the church website, or if a kiosk connects to the church’s internet. Three terms come up here:

  • Hyperlink: a link or button that takes the donor directly to your hosted giving page.
  • URL redirect: a web address your church controls that automatically sends visitors to your giving page.
  • Embedded form: a giving form displayed inside one of your own web pages.


A scan matters for embedded forms because the giving form appears on a page of your own website. Attackers sometimes tamper with the scripts on a page like that to capture card details as donors enter them, which is sometimes called e-skimming.

A scan matters for URL redirects because the redirect is an address your church controls. If someone gains access to your website, they could change where the redirect leads and send donors to a counterfeit giving page.

A scan checks your website or network address for known weaknesses, and results usually arrive within a day or two. If it passes, you move on to signing. If it finds issues, the report lists the fixes, which your website host or IT contact usually handles, and then you scan again.

One detail helps. Confirm the network address you are scanning, because some portals pre-fill the address of whatever device you are using, which may not be your website or your kiosk’s connection.

How can a church make PCI compliance easier?

Name one PCI contact and a backup, put the renewal on the calendar, and keep a short list of who has a login to your giving accounts. Those three habits take care of most of the process.

After more than 20 years of working with churches, our support team hears the same few questions: whether a scan applies, who holds the portal login, and which questionnaire fits. Each has a clear answer once you know how your church accepts gifts. A few habits make the rest easier:

  • Name a PCI contact and a backup. Portal logins and renewal notices go to one person. A backup means the renewal does not depend on a single inbox.
  • Set a renewal reminder. The questionnaire repeats yearly, so a calendar date a few weeks ahead leaves room for a scan and any fixes.
  • Keep a list of who has access. Know who has a login to your giving accounts, avoid shared logins, and remove access promptly if a staff member or volunteer leaves.
  • Never let donors write down card numbers. Paper card details bring extra questions into the questionnaire. Without them, several items simply do not apply.
  • List your service providers. Your giving platform, processor, and web host should each be PCI compliant, and a simple list makes the questionnaire easier to answer.
  • Know who manages your website and network. If a scan finds something, that person or team handles the fix.
  • Use strong, unique passwords with two-step sign-in (also called multi-factor authentication) where it is offered. The Council lists weak and default passwords among the leading causes of payment data breaches. Our guide to strengthening church data security goes deeper.
  • Decide who to call if you suspect a breach. A one-line plan is enough to answer the related questions.

 

The Council also offers free resources for small organizations, including a Guide to Safe Payments, Questions to Ask Your Vendors, and a Data Security Essentials Evaluation Tool.

Has PCI compliance changed recently?

Yes. The standard was updated to version 4.0.1, and its newest requirements became mandatory on March 31, 2025. The previous version, 3.2.1, was retired on March 31, 2024.

For most churches, the change shows up as updated questionnaires and instructions, so it helps to read each question fresh each year. In early 2025, the Council also adjusted the shortest questionnaire, SAQ A, to ask whether a website is exposed to script tampering. That makes how your giving page connects to your website a good thing to confirm with your provider.

If you use SecureGive with CardConnect

If your church uses SecureGive with a CardConnect merchant account, you complete PCI compliance in the CardPointe portal. SecureGive is a PCI Level 1 service provider, and the portal is where your church completes its part. Your login came from CardPointe when the merchant account opened, and if you need a reset, our support team can help.

Our team keeps step-by-step instructions for each setup: online and mobile, kiosk, or both. You can also read about how we protect donor data on our security page.

If you have a question about which questionnaire fits your church or whether a scan applies, our team is glad to walk through it with you. Just send us an email or give us a call.

Frequently Asked Questions

Yes. PCI DSS applies to every organization that accepts card payments, regardless of size. Smaller churches often have simpler setups, which usually means a shorter questionnaire. The card brands and your merchant account provider decide whether and how often a church completes it.

Most processors ask churches to complete it every year. Your portal shows your due date, and many providers send reminder emails beforehand. Because requirements and instructions can change, read each question against your current setup before you sign.

Processors can charge a monthly non-compliance fee if the questionnaire is not completed on time, and amounts and grace periods vary by provider. Your merchant agreement lists the specifics, and your giving platform's support team can help you find where your account stands.

Responsibility is shared. A PCI compliant giving platform and processor secure the systems that handle card data. SecureGive is a PCI Level 1 service provider. Your church is responsible for what it controls: how donors reach your giving page, who has a login to your accounts, any kiosk connection, and keeping card numbers off paper.

It depends on how donors reach your giving page. A scan is a security check of your website or network address. A plain hyperlink to a hosted giving page does not require one for most SecureGive churches. A redirect or embedded form does, and so does a kiosk connected to your network.

Usually a finance director, administrator, or operations lead, because the questions cover access, policies, and vendors. In smaller churches it may be the pastor. Name a backup contact, and involve whoever manages your website or network if a scan applies.

Insights Delivered to Your Inbox

Start building a more generous church with resources, insights, and practical ministry tips delivered to your inbox every week.

Select a campus

Download Your Resource

Complete the form to receive your free Impact Report Template.

Ready to see ParishGive?

Complete the form and our team will schedule a time to show you ParishGive’s trusted giving and engagement solution.

Request a Meeting with Todd

Complete the form and Todd will be in touch to schedule a time to meet.

Ready to see SecureGive?

Complete the form and our team will schedule a time to show you SecureGive’s trusted giving and engagement solution.