The short answer: the card reader you can use with Altru is decided by Blackbaud, not by what’s on the shelf at an office supply store. Altru takes card payments through Blackbaud’s own payment processing, so only devices Blackbaud has tested and approved for that connection will pass card data into a sale. A reader that works fine with a coffee shop’s point of sale will usually do nothing useful in Altru.
That makes the real question less “which reader should we buy?” and more “what does Blackbaud support right now, and does it cover chip and tap?” Here’s how to get a reliable answer and what to weigh before you spend money on hardware.
Why you can’t just plug in any reader
When a card is swiped, dipped, or tapped, the reader has to hand the card data to software that knows how to send it to a payment processor. In Altru, that path runs through Blackbaud’s payment service. The reader, the Altru client on the workstation, and the processor all have to agree on the format and the encryption.
Generic readers fail in a few predictable ways:
- They don’t encrypt card data the way Blackbaud’s processing expects, so the transaction is rejected or the data never reaches the payment screen.
- They’re built for a specific processor’s terminal ecosystem (many all-in-one countertop terminals are) and can’t talk to Altru at all.
- They work in a test but introduce PCI compliance problems because unencrypted card data passes through the workstation.
Swipe, chip, and tap are different questions
Altru’s in-person card support has historically centered on swipe (magnetic stripe) readers connected to the sales workstation. Chip (EMV) and contactless tap are separate capabilities, and whether Altru supports them, with which devices, and in which countries, is exactly the kind of thing that changes over time. We’re not going to guess at the current state here. Ask Blackbaud directly and get the answer in writing.
Why it matters:
- Fraud liability. With card networks’ EMV rules, if a chip card is swiped instead of dipped and the charge turns out to be fraudulent, the liability for that charge can fall on the merchant rather than the card issuer. For low-dollar admissions this is rarely a big number, but for memberships, group sales, and gift shop purchases it adds up.
- Visitor expectations. People increasingly reach for tap or a phone wallet first. A swipe-only desk works, but it’s slower and some newer cards are awkward to swipe.
- Card availability. Some issuers and international cards lean hard on chip. If you get many international visitors, ask about that specifically.
Questions to put to Blackbaud before buying anything
- What card reader models are currently supported for Altru daily sales, and is there a published compatibility list we can reference?
- Does Altru support EMV chip and contactless payments at the point of sale today? If yes, which devices, and does it require a specific payment processing setup or account change?
- Are the supported readers encrypted at the device (so card data never sits unencrypted on our workstation)?
- Does anything change for our Windows version, browser, or the way the Altru client is installed on sales stations?
- Where should we buy the device, and is there a configuration or encryption key injection step before it’ll work?
- Do the same readers work for membership sales, group sales payments, and the gift shop, or only daily sales?
Buy one device first and test it on a single workstation with a real low-dollar transaction and a refund before you order for every register.
What organizations do when the supported options aren’t enough
If Blackbaud’s answer doesn’t cover chip or tap the way you’d like, the common fallbacks each have a cost:
Stay with supported swipe readers
The simplest path. Transactions post to Altru with no extra reconciliation. You accept the swipe experience and whatever chargeback exposure comes with it. Many organizations with mostly low-ticket admissions find this acceptable.
Run a separate standalone terminal
Some sites keep a chip-and-tap terminal from another processor beside the register for guests who can’t or won’t swipe. The sale still has to be recorded in Altru, usually with a payment method set up for that purpose, and someone has to reconcile two processors’ deposits each day. It works, but it doubles the bookkeeping and makes it easy for a sale to be charged on the terminal and never entered in Altru (or the reverse). If you go this way, have finance agree on the payment method naming and a daily reconciliation step before staff start using it.
Move more sales off the desk
Every ticket or membership sold online in advance is one fewer card at the counter. Pushing timed tickets and renewals to the web, then scanning them at entry, reduces how much your in-person card hardware matters. It doesn’t solve the gift shop or walk-up traffic, but it can shorten the line enough that the reader stops being a pain point.
A few practical tips
- Keep one spare, already-configured reader. A failed device at opening time with no backup means hand-keying cards, which is slower and riskier.
- Label each reader with the workstation it’s paired to if your setup needs that.
- Don’t let staff type card numbers into notes or comments when a reader fails. Write down the fallback procedure.
- Check your PCI self-assessment with whoever owns it after any hardware change.
Quick answers
Can I use a reader from my bank or another processor?
Generally no. Altru processes cards through Blackbaud, so the reader has to be one Blackbaud supports for that connection.
Does Altru take Apple Pay or Google Pay at the desk?
That depends on whether contactless is supported in your current setup. Confirm with Blackbaud support rather than assuming.
Do I need new readers for online sales?
No. Web purchases are entered by the buyer on their own device, so desk hardware doesn’t affect them.
