A caller wants four tickets for Saturday’s lantern walk. They read you the card number, the expiration date, the security code, and then pause when you ask for their street address. Maybe they’re calling from a car, maybe they’re buying for a relative, maybe they just don’t want to say it out loud. Your advance sales screen is waiting on that field, and the line behind them is getting longer.
Billing address friction in Advance Sales comes up at almost every Altru site that takes phone orders. The short version: the requirement usually isn’t arbitrary, it isn’t always coming from Altru itself, and the right fix depends on where the requirement actually lives.
Figure out who is asking for the address
Before you change anything, separate three things that tend to get blurred together:
- Altru’s own required fields. The advance sales order is tied to a constituent, and your configuration may require address information on that constituent or on the payment.
- Your payment processor’s fraud rules. Card-not-present transactions (phone orders are the classic example) are commonly checked with address verification, which compares the billing street and ZIP to what the card issuer has on file. Depending on how your merchant account is set up, a missing or mismatched address can cause a decline or a higher processing rate.
- Your own internal policy. Some organizations made address a habit years ago for mailing lists or fraud reasons, and nobody remembers why.
The fastest way to tell them apart is to run a test order in a sandbox or test environment, leave the address blank, and note exactly where it stops you and what message you get. An Altru validation message points to configuration. A decline or warning from the payment step points to your processor settings. If you can’t tell, open a case with Blackbaud support and include the exact message; ask them specifically whether the address is required by Altru, by your merchant account, or both.
If the processor is the one requiring it
Address verification exists to protect you from chargebacks on phone and online orders, so think carefully before trying to loosen it. A few honest points:
- Your merchant account settings decide how strict address verification is. Whether you can relax them, and what that does to your rates or chargeback liability, is a conversation with your processor, not something to work around at the desk.
- In many setups the ZIP code carries most of the verification weight. Ask whether a ZIP-only match is acceptable for your account. Some callers who balk at a full street address will happily give a ZIP.
- If you do loosen the rules, watch your chargebacks for a few months afterward. Large group orders and high-dollar phone sales are where fraud tends to show up.
If Altru configuration is the one requiring it
Look at what your setup treats as mandatory for a new constituent and for a payment. Some sites require a full address on every new record for good reasons (mailings, membership prospecting, data quality), and turning that off affects every sales channel, not just phone orders. Weigh that before changing it.
A middle path many teams use:
- Search for the constituent first. Repeat buyers and members often already have an address on file. Confirm it with the caller (“Is your billing address still the one on Elm Street?”) instead of asking them to recite it.
- Agree on what counts as acceptable minimum data for a brand-new caller, then make sure your configuration actually allows it. Test it before training anyone on it.
- Flag incomplete records with a constituent attribute or note so they can be found later with a query and cleaned up, rather than becoming permanent gaps.
Ways to avoid keying the card at all
Sometimes the cleanest answer is to not take the card over the phone:
- Send the caller to your online sales. Online checkout puts the address entry on the buyer’s own device, and it keeps card numbers out of your staff’s ears entirely. Walk them to the right page while they’re still on the line if needed.
- Hold the order and collect payment on arrival. If your policies allow reservations with payment at pickup, the card can be handled in person at the desk, where it’s a card-present transaction rather than a phone order. Check how your team handles unpaid reservations before relying on this.
- For groups and schools, invoicing or a separate payment step often fits better than reading a card over the phone, and the payer (often a business office) is used to supplying billing details.
Things not to do
A few workarounds show up at a lot of desks and cause problems later:
- Typing your organization’s own address as the billing address. It can fail verification, it muddies your constituent data, and it may put you on the wrong side of your merchant agreement.
- Writing card numbers on paper to process later when the caller “gets back to you” with an address. That creates a card security problem that is far worse than a declined call.
- Entering placeholder text like “N/A” or “Phone order” in address fields. Those records end up in mailing lists and duplicate checks.
Quick answers
Can Altru process an Advance Sales card payment with no billing address at all?
It depends on your configuration and your merchant account settings, and we’d rather not guess for your site. Test it in a sandbox and confirm with Blackbaud support before telling staff it’s allowed.
Is a ZIP code enough?
Sometimes. Ask your processor whether ZIP-only verification is acceptable for your account and what it means for chargeback protection.
What should front desk staff say to a caller who won’t give an address?
Offer the online option or payment at pickup. Give staff that script up front so they aren’t improvising with a card number in hand.
