Security is part of the donor experience

Trust is what makes giving feel easy

Peak giving is ahead of us as Giving Tuesday and year-end approach. For many nonprofits, the weeks between now and the end of December bring in more online revenue than any other stretch of the year. They also bring more phishing emails, more fraudulent transactions, and more pressure on every system that touches a gift.

Every gift in that window depends on something donors rarely think about: confidence that their money and their information are safe. Nonprofits work hard to earn that confidence through their mission and their stories.

Security is an important part of the donor experience. A donor deciding whether to give makes a quick judgment about whether an organization can be trusted. When that judgment comes easily, more people complete their gift. Good security is what makes that possible.

Donors don’t see security, but they feel it

Most donors will never read a security page. What they experience is the result: a checkout that recognizes their digital wallet, a form that asks only for what it needs, and a gift that goes through without a second thought. When security works well, it’s invisible. When something looks off, donors hesitate, and that creates friction in the moment of highest intent before completing a gift.

The safest giving experience can also be the easiest one, and it should be. Digital wallets confirm a donor’s identity with a fingerprint or a face scan. Fraud screening runs in the background, where legitimate donors never notice it. Extra checks like 3D Secure appear only when a bank asks for them.

Trust also carries forward. A first gift is the start of a relationship, and every later decision depends on how that first experience felt: whether to give again, whether to become a monthly donor, whether to share personal details for a tribute gift. Security protects the transaction in front of you and every gift that might follow it.

Donor data deserves the same care. When someone gives, they share their name, address, and payment details, trusting your organization to look after them. Stewarding that information well is part of stewarding the donor.

Security is something you practice every day

Many security problems don’t begin with a sophisticated attack. They begin with a former volunteer who still has a login, a password reused across three tools, or an email that looked like it came from a trusted vendor. That’s good news, because it means most of the protections that matter are within every nonprofit’s reach.

It also means trust has to be earned through evidence. Nonprofits should know how their donations are processed, how donor information is handled, and who controls the donor relationship. Their technology partners should be able to explain those safeguards in plain language and show independent proof that they work. If a vendor can only tell you that security is a priority, ask more questions.

What security really means, in plain language

The best security design assumes something will eventually go wrong somewhere, and limits how far it can spread. The safest card number is one that was never stored, which is why tokenization matters. The safest integration shares only what it needs to, in the direction it needs to. And the safest account requires more than a password. When you evaluate any technology partner, ask how their design contains a problem, not only how they prevent one.

Security pages are full of acronyms. Each one describes a specific protection, and it helps to know what you’re getting.

TermWhat it meansWhy it matters to your nonprofit
PCI DSS Level 1The highest level of the card industry’s security standard, assessed independently every year.Card data is handled to the standard banks require, so your team has reduced burden.
TokenizationCard numbers are replaced with a random token that’s useless if stolen.Full card numbers never sit in your systems or your platform’s database.
Encryption at rest and in transitData is scrambled while stored and while moving between systems.Copied or intercepted data can’t be read without the keys.
SOC 2 Type IIAn independent audit of how a company runs its security controls over several months.It shows the controls work in practice, beyond a written policy.
ISO 27001An international standard for managing information security across an entire company.Security is run as an ongoing program with clear ownership and regular review.
Penetration testingSecurity specialists try to break in the way an attacker would.Weaknesses get found and fixed before someone else finds them.
Two-factor authentication and SSOA second proof of identity at login, or sign-in through your organization’s own identity system.A stolen password alone can’t open your account.
Least-privilege accessPeople and connected systems get only the access their role requires.One compromised login can do far less damage.
Data controller and processorThe controller (your nonprofit) decides how donor data is used. The processor handles it on your behalf.Your donor data and relationships stay yours.

Nine steps to take before Giving Tuesday

Most of these take less than an hour, and together they can help close the gaps attackers rely on most during giving season.

  1. Turn on two-factor authentication for everyone. That includes every user of your fundraising platform, CRM, and email. A stolen password alone shouldn’t be enough to get in. Where your platform allows it, require 2FA for every user, or require single sign-on (SSO) through your organization’s identity provider.
  2. Review who has access. Remove former staff, volunteers, and agencies. Give everyone else only the access their role requires.
  3. Be skeptical of unexpected security emails. Attackers send fake “security incident” or “reset your password” messages around big giving moments. Don’t click the link. Go to the vendor’s site directly.
  4. Rotate your integration keys. If you connect a CRM or other tool through an API key, generate a new one, at least once a year and whenever someone with access leaves.
  5. Know what card testing looks like. A run of small, failed, or repeated donations is the classic sign that someone is testing stolen cards on your form. Report it to your platform right away.
  6. Reconcile after any outage. When a connected system comes back online, confirm that every gift made while it was down has synced.
  7. Watch for copycat pages. Fraudsters build fake donation pages around high-profile moments. Search for your organization’s name, and report impersonation to your platform and to the site hosting it.
  8. Audit your connected apps. Review which apps and integration users can access your CRM, and remove any you no longer use. Check login history for activity you don’t recognize.
  9. Ask your vendors for evidence. Request current audit reports, such as SOC 2 Type II and a PCI attestation. Ask which direction data flows in each integration, and what keeps working if a connected system goes down. Ask how much traffic they test for, and whether they’ve ever turned away a donation because of load.

How Fundraise Up manages security

We monitor security continuously, and independent auditors verify our standards every year. Here’s what that looks like in practice.

AreaWhat we do
PaymentsPCI DSS Level 1 certified (v4.0.1). Card payments are tokenized through Stripe, and we store only the card’s last four digits, expiry date, and brand.
Independent auditsSOC 2 Type II and ISO 27001, with annual penetration testing. Our Trust Center holds the SOC 2 Type II report (covering security, availability, and confidentiality), our PCI DSS attestation, our ISO 27001 certificate, a HECVAT, our latest penetration test, and a data processing agreement.
Encryption256‑bit AES encryption at rest and TLS 1.2+ in transit.
Fraud and card testingLayered screening that combines behavior analysis, proxy detection, background bot checks, Stripe Radar, and human review. Supports 3D Secure where banks require it. Our fraud protection blocks 98.8% of fraudulent donation attempts.
Account accessTwo-factor authentication that admins can require for every user, SAML single sign-on, role-based permissions, and an audit log of user actions.
IntegrationsDonations keep processing even if a connected CRM is unavailable. On repeated errors the sync pauses, and every donation stays stored in Fundraise Up, ready to resync. A sync log shows which donations synced or failed and why, and admins can resync failed donations, all donations, or a date range. Admins get alerts for critical errors or a revoked connection, plus optional daily or weekly sync reports. A unique ID on every record means a resync never creates duplicates.
Resilience99% uptime, up to 600 transactions per second in real time with overflow queued rather than rejected, monthly load testing, hourly and daily backups kept for up to a year, and a public status page.
Data controlYour organization is the data controller and Fundraise Up is the processor. Your donor relationships stay yours.

Security work is never finished. We keep testing, monitoring, and improving the platform so nonprofits can spend their time on supporters instead of safeguards.

A gift that goes through on Fundraise Up

Security protects a donor’s information. Reliability protects the gift itself. A page that won’t load or a checkout that stalls shakes a donor’s confidence as much as anything that looks suspicious, and on the busiest giving days a few minutes of downtime can cost gifts a nonprofit never gets back.

Giving-day traffic doesn’t rise gently. A matching-gift deadline, an email send, or a moment on live TV can bring thousands of donors to a page within minutes. The question that matters is what happens at a platform’s busiest minute. Here’s how we build for it.

  • Capacity to handle the donor volume. The platform processes up to 600 transactions per second in real time. If traffic ever goes beyond that, extra transactions are queued and completed moments later. In our history, we have never rejected a donation because of server overload.
  • Testing before it counts. Every month we run load tests that simulate complete donor checkouts. We add quarterly stress tests that push past normal capacity, and extra testing ahead of Giving Tuesday and year-end.
  • No single point of failure. Our infrastructure runs across data centers in the US, Canada, the UK, and the EU, and a global content delivery network serves checkout from the location closest to each donor. If a supporting service such as address validation slows down, we switch to a backup provider or finish that step after the gift is complete.
  • Live gifts come first. During spikes, real-time donations take priority over background work like scheduled recurring charges and CRM syncs, which catch up shortly after.
  • Uptime you can check. Fundraise Up maintains 99% uptime commitment, and current platform status is always visible on our public status page.

That preparation shows up when the stakes are highest.

Make security part of your giving season plan

The nonprofits that have the strongest giving seasons plan for them months in advance. Security deserves a place in that plan, alongside your campaign calendar and your matching gifts. Security is never one and done. Nonprofits and sector vendors should remain diligent, and especially during the highest volume donation moments of the year.

Donors bring their generosity to the moments that matter most. When they can give without second-guessing the experience, more of that generosity reaches your mission.

Fundraise Up customers can contact their Customer Success Manager with any questions. To learn more about how we protect nonprofits and their donors, visit our security and compliance documentation.

Copied

Stay connected

Get updates and insights delivered to your inbox