
The dashboard groups transactions by their creation date, but every time it loads it shows their current status. It doesn't show how they looked on the day of the donation or on the day you downloaded the report.
A transaction can keep updating days or even months later, for legitimate reasons: a refund, a chargeback, a late confirmation from the bank, or a security review.
Example: the September report, checked on two dates
Between the two checks, 3 September donations were identified as fraud. They weren't recorded incorrectly: their status changed afterward, and September's amount raised drops by the same proportion.
Open each reason to see what changes and when it can happen.
afrus continuously analyzes donation activity to protect your organization: unusual volumes, repeated cards, or attempts made too close together. When a transaction looks suspicious, our risk team refunds it through the payment gateway and marks it as fraud.
A donor can dispute a charge with their bank and ask for the money back. Card networks (Visa, Mastercard, etc.) allow this up to 120 days after payment, although most arrive within the first 90 days.
A donor can ask afrus, the payment gateway, or the organization to return their donation. Unlike a chargeback, which the bank starts, a refund is a voluntary request handled by support.
Some payment methods don't confirm the result right away. afrus records the donation with a provisional status (pending or processing) and waits for the gateway's final confirmation. That timing depends on the bank or gateway, not on afrus.
Methods most likely to be affected
On the dashboard: a pending donation becomes successful or failed, so it appears in or disappears from the total. It still counts on its original date.
As an extra safeguard, afrus can hold a donation for review when it detects risk signals. It doesn't count as successful until someone on our team reviews and confirms it.
Some payment methods are processed in batches: the bank charges on its own schedule, and afrus only learns the result when it receives the response file. The clearest case is Recurring Bank Debit (DRB), used for monthly donations charged directly to a bank account.
| # | Reason | What changes in the donation | Effect on amount raised | Typical window |
|---|---|---|---|---|
| 1 | Fraud detection | Moves from successful to fraud | Lowers | Days to weeks |
| 2 | Chargeback | Moves to chargeback (back to successful if the dispute is won) | Lowers (or raises if reversed) | Up to 3–4 months |
| 3 | Full or partial refund | Moves to refunded, or its amount is reduced | Lowers the amount (and sometimes the count) | No fixed window |
| 4 | Late confirmation | Moves from pending to successful or failed | Raises or lowers | Minutes to several days |
| 5 | Security review | Moves from under review to successful | Raises | Minutes to several days |
| 6 | Recurring bank debit | Confirmed when the bank's response arrives | Raises | Several days |
