A refund that won’t go through is rarely random. When Altru refuses one, or appears to process it but the money never reaches the guest’s card, the cause almost always falls into one of a handful of buckets: the state of the original payment, where that payment was actually processed, what has already happened to the money, or what the person clicking has permission to do. Working through those in order usually finds the problem in a few minutes.
Below is how we’d triage it, roughly from most common to least.
1. Look at the original payment before anything else
Open the original transaction on the constituent record or in daily sales and note three things: the payment method, the date, and the amount already refunded (if any). Most refund failures are explained right there.
- It was paid by card today. In card processing generally, a charge that hasn’t settled yet is usually voided, not refunded. If your workflow only offers a refund and it fails on a same-day card sale, the transaction may need to be handled as a void or simply retried after settlement. How Altru presents this depends on your payment setup, so confirm the expected behavior with Blackbaud support rather than assuming.
- It was paid a long time ago. Card networks and processors limit how far back a refund can go back to the original card. An old transaction may need to be refunded by another method, such as a check, with the refund still recorded in Altru so revenue stays accurate.
- Part of it was already refunded. If someone issued a partial refund earlier, the remaining refundable amount is smaller than the original total. Trying to refund the full original amount will fail. Check for an earlier refund before trying again, and don’t let two staff members work the same request at once.
- It was split across tenders. A sale paid partly by card and partly by cash or gift certificate has to be refunded in pieces that match those tenders. Refunding the whole amount to the card typically won’t work.
2. Confirm where the money was actually collected
This one catches a lot of organizations. Altru can only push a refund back to a card when the charge ran through the merchant account Altru is connected to. If a purchase was taken some other way, Altru has a record of the sale but no ability to reverse the card charge:
- A standalone card terminal at the desk that isn’t integrated with Altru.
- A third-party online checkout, event platform, or donation page that charges the card itself and then writes the sale into Altru.
- A merchant account that has since been replaced. Transactions taken under an old account may not be refundable through the new one.
In those cases the refund has to be issued wherever the charge happened (the terminal, the vendor’s dashboard, or the processor’s portal), and then recorded in Altru as a refund by an appropriate non-card method so your revenue and the guest’s record match. Write down which channels fall into this category so desk staff know where to go.
3. Check permissions and the register
If the payment looks normal and was processed through Altru, the next suspect is the user.
- Security role. Refund rights are often limited to supervisors on purpose. A front-desk role that can sell tickets may not be able to refund them. Have an admin compare the user’s role with someone who can refund successfully.
- Drawer or session state. Refunds at the point of sale typically need to happen within an active sales session. If the drawer is closed or the user is in the wrong session, the refund may be blocked or land somewhere unexpected.
4. Consider what’s attached to the sale
Some sales carry more than a payment. A membership purchase created a membership. A ticket may already have been scanned. An order may include items tied to a program or event that has already run. Depending on how your organization is configured, Altru may expect you to deal with those pieces (cancel the membership, return the tickets) as part of the refund, or may treat the order differently once part of it has been used. If you can’t tell whether this is what’s blocking you, reproduce the scenario with a test sale in a non-production environment if you have one, or ask Blackbaud support how your version handles it.
5. Think about finance before you force it through
If revenue for the original sale has already been posted to your general ledger, a refund still creates a reversing entry that finance has to account for. That isn’t usually what blocks the refund, but it’s a good reason to loop in your business office before staff improvise. Workarounds like deleting payments or editing amounts to make the numbers “fit” cause much bigger problems at month-end than a delayed refund.
When to call Blackbaud support
If none of the above explains it, the issue may be in the payment configuration or the processor connection itself, which only Blackbaud can see. To speed things up, have this ready:
- The constituent name and the transaction date and amount.
- The exact error message, word for word, or a screenshot.
- Whether the failure happens for every refund or only this one.
- Which user tried it and from where (desk, back office, online order).
“Every card refund fails since Tuesday” points to a configuration or processor problem. “Only this one fails” almost always traces back to steps 1 through 4.
What to tell the guest in the meantime
Be honest and specific: confirm the amount you’re refunding, how it will come back to them (card or check), and when you’ll follow up. Note the promise on their constituent record so whoever picks it up next doesn’t start over. A refund that takes an extra day is fine; one that gets lost between shifts is what generates the angry follow-up.
Quick answers
Altru said the refund succeeded, but the guest never got the money. Why?
Check whether the refund was recorded to a card or to another payment method. If it was recorded as cash or check, Altru logged it but nothing went back to the card. Also allow time for the card issuer to post it, which commonly takes several business days.
Can I refund to a different card than the one used?
Generally card refunds go back to the original card. For a different destination, refund by another method and record it in Altru. Confirm your organization’s policy and processor rules first.
