Say you’re running a free family day, a members-only preview with no charge, or a zero-dollar volunteer orientation. You build the registration on an Altru web form, test it, and there it is: a billing address block asking people for a street, city, and ZIP to “pay” nothing. Some visitors fill it in, some type nonsense, and some leave.
Below is what’s going on, what you can realistically change, and how to keep the data clean in the meantime.
Why billing fields show up when nobody is paying
Altru’s public web forms are built around a purchase flow. Tickets, memberships, donations, and event registrations all pass through the same checkout logic, and that logic assumes there will be a payment to authorize. Billing details travel with the payment, so they tend to come along even when the total is zero.
How much control you have over that section is the part to verify for yourself. Administrators can adjust a lot of form content, but billing information isn’t always configurable the way other fields are, and the behavior can depend on the form type and how it’s set up. We’d rather not guess which combination applies to your site. The reliable way to find out:
- Clone the form in a sandbox or test environment and set every item to $0.
- Look through the form’s field and section settings for anything that controls billing information or marks address fields as required.
- Submit a test registration with the address left blank and see whether it goes through.
- If it won’t, open a case with Blackbaud support and ask directly whether billing fields can be hidden or made optional on no-payment forms in your version. Ask them to describe the current behavior, not just say “it’s on the roadmap.”
Do you actually need the address?
Before you look for workarounds, decide what you want. An address isn’t useless on a free registration. It helps with matching against existing constituent records, and some teams use it for future mailings. But there’s a real cost too:
- Drop-off. A free form that looks like a checkout makes people hesitate. They wonder whether they’ll be charged.
- Bad data. People who don’t want to share an address will type “none,” “123 Main St,” or your own street address. Those values end up on constituent records.
- Duplicate risk. A fake or partial address can keep Altru from matching a returning visitor to their existing record, so you end up with a second record for the same person.
- Privacy. Collecting personal data you don’t need is harder to defend than not collecting it.
If you only need name and email for a free event, that’s a good reason to stop asking for more.
Workarounds while the form stays as it is
Explain why the address is there
If the fields can’t be removed, add a short line near the top of the form, such as: “This event is free. You won’t be charged. We ask for your address so we can match your visit to your existing record.” Being honest about it brings back some of the people who would otherwise leave, and it cuts down on made-up addresses.
Don’t tell visitors to type a placeholder
It’s tempting to write “enter N/A if you prefer.” Don’t. Placeholder text in address fields is hard to clean up later and can trip address validation or matching. If you take one thing from this article, take this one.
Build a cleanup query
Set up a constituent query that finds records created or updated through your web forms where the address is obviously junk: very short street lines, common filler words, or your organization’s own address. Run it after each free event. It’s much easier to fix twenty records the week of the event than two thousand at year end.
Watch for duplicates after big free events
Free days bring a lot of first-time and returning visitors through at once. Plan a duplicate review afterward, especially if many registrants entered incomplete addresses that wouldn’t match their existing records.
Consider a different registration path for free events
For truly free events with no capacity concerns, some teams take free RSVPs outside the Altru payment flow and import or sync the attendees afterward. That trades one problem for another: now you have to get the data into Altru correctly. Whether it’s worth it depends on how many free events you run and who handles the import.
Where Social Good fits
We build Checkouts, a branded, mobile-friendly checkout that organizations use in place of Altru web forms for tickets, memberships, and donations, with the data writing back to Altru. If the form experience is the problem, including what it asks of visitors, that’s the kind of thing it’s built to address. If you’re seeing this on just one or two free events a year, though, the steps above may be all you need.
Quick answers
Is the billing address required by Altru or by the payment processor?
It comes from the payment flow the form uses. Whether you can switch it off for zero-dollar transactions depends on your form type and configuration, so test it in a sandbox and confirm with Blackbaud support.
Will a blank or fake address break anything?
It won’t stop the registration from recording, but it can weaken record matching and add duplicates or junk addresses to constituent records. A cleanup query after each free event keeps that manageable.
