Somewhere in the back of your mind there’s probably a meeting playing on a loop. A board member asks who is responsible if a donor’s card number gets stolen, and nobody at the table has a good answer. That single imagined question is the reason plenty of small nonprofits keep a cash box and a stack of envelopes while telling themselves online giving can wait until next year. The worry makes sense, but it’s aimed at the wrong target, and once you see where card data actually travels, the fear shrinks to something you can manage with a free afternoon and a decent password manager.

Where the Fear Actually Comes From

Most of us absorbed our sense of online risk from news stories about breaches at huge retailers, hospitals, and banks. Those stories leave a specific picture behind: a database full of card numbers sitting on a server somewhere, waiting for the wrong person to find it. When you run a volunteer-led food pantry or a youth sports league, it’s natural to imagine that you’d be the one holding that database, probably as a spreadsheet on the treasurer’s personal laptop.

Here’s the good news, delivered with a little irritation at how rarely anyone says it plainly. A properly built donation flow never asks your organization to hold card numbers at all. The security side of online giving is largely handled by the payment processor and the platform sitting between your donor and your bank account, which is exactly why online giving security looks so different for a small team than it does for a retailer running its own checkout. Your job shifts from guarding card data to guarding your logins, which is a much smaller and friendlier problem.

What Happens to a Card Number After Someone Clicks Donate

Walk through it from the donor’s side. Someone lands on your page, picks an amount, and types a card number into a secure payment form. That form is served by the payment processor, and the number travels over an encrypted connection straight to them. Your website, your email, and your volunteers never see the full number at any point in the trip. What comes back to you is a confirmation, the donor’s name and email, the amount, and usually just the last four digits of the card for your records. If you’re curious about the full sequence, the breakdown of what actually happens when someone clicks donate goes step by step through the handoff.

SolaFund runs payments through Stripe Connect, and Stripe states publicly that it is certified as a PCI Service Provider Level 1, which is the most demanding tier in the payment card industry’s compliance program. You don’t need to memorize any of that. What matters is the division of labor: the company whose entire business is moving money securely carries the heavy security work, and SolaFund handles the technical infrastructure around it so you never have to build or maintain any of it yourself.

Why Your Organization Never Touches the Card

The card industry has a security standard called PCI DSS, and the practical rule behind it is simple enough to repeat at a board meeting. The compliance burden follows the data. If your website never stores, processes, or transmits card numbers, you have far less to protect, and that is the entire reason to use a hosted payment flow instead of cobbling together your own form.

It also tells you where the genuinely unsafe version of online giving lives. Collecting card details over email, reading numbers aloud into a voicemail, typing them into a Google Form, or texting a photo of a card to the volunteer who handles deposits all put real card data in places never designed to protect it. If a donor offers to send their card number that way, the kindest and safest response is to send them a link to your payment page instead, and thank them for being willing to give.

The Risks That Are Real and Surprisingly Boring

Nobody is going to tunnel into your finances through a cinematic hacking montage. The risks worth your attention are almost embarrassingly ordinary: a weak password reused across five accounts, a login shared by four volunteers, a former board member who still has access to the dashboard two years after leaving, or an email that looks like it came from your payment processor and asks you to sign in through a link. Another real one is card testing, where a scammer runs tiny charges through any donation page they can find to see which stolen cards still work. A reputable processor monitors for this kind of pattern, but it’s a good reason to glance at your transactions now and then.

Notice what every item on that list has in common. None of them involve the platform being cracked open, and all of them are fixable with habits instead of budget. Working through a simple donor safeguard checklist once a quarter covers most of the ground, and it takes less time than the average board meeting spends debating the font on the annual appeal.

A Short Security Routine for Small Teams

Start with two-factor authentication on every account that touches money, including your donation platform, your bank, and the email address those accounts send password resets to. Give each person who needs access their own login so you can tell who did what, and remove people promptly when they step back from the organization. Use a password manager instead of a notes file, because a notes file is just a breach waiting for a laptop to get left in a coffee shop. When an email asks you to log in, close it and type the address into your browser yourself, which defeats the most common phishing trick in about four seconds.

Questions Boards Ask Before Saying Yes

Disputed charges come up first in almost every conversation, and they deserve a straight answer. A donor can always contact their card issuer and dispute a charge, the same way they could with any online purchase, and it occasionally happens even when the donor simply forgot what the charge was for. The practical defense is dull and effective: send a clear receipt right away, make sure your organization’s name shows up recognizably on the card statement, and reply quickly if a dispute notice arrives.

Boards also wonder whether donors will trust a page they’ve never seen before. Donors read small signals constantly, such as the padlock in the browser bar, your organization’s name and logo on the payment page, a real contact address, and a confirmation message that sounds like a person wrote it. None of those cost anything, and together they do more to calm a nervous first-time donor than any badge crammed into the footer.

Finally, some boards ask whether they should talk to their insurance agent about online giving. It’s a perfectly sensible question to bring to someone who knows your policy, since coverage varies and nobody outside your own paperwork can answer it for you.

Making the Decision With Clear Eyes

Saying no to online giving feels like the safe choice, but it quietly carries its own risks. Checks get lost in the mail, cash sits in a desk drawer over a long weekend, and donors who would happily give on their phone at eleven at night simply don’t give at all. Compared with all that, a hosted payment flow run through an established processor is a calmer place to keep your fundraising than a shoebox.

If the fear is still louder than the facts, run a small experiment before you commit to anything. Choose a platform built on a recognized processor, turn on two-factor authentication, and make a five dollar donation to your own organization from your personal card. Watch where the money lands, read the receipt as a donor would, and notice how little of the process ever touched anything you own. Most boards that try this come away with the same reaction, which is mild surprise that the scary part was never really theirs to carry.