Skip to main content
A card in the payment methods table may show an Expired status even though recurring gifts charged to that card continue to process without any issues. This is expected behavior, not a bug.

​
Why this happens

The Expired label in the dashboard is based on the expiration date that was stored when the card was first added. WeGive compares that stored date to today’s date — if the stored date has passed, the card shows as Expired. However, when a charge is submitted, WeGive sends the card’s secure token to your payment processor (Stripe, Braintree, Finix, or another supported processor). The processor uses its own records to determine whether the card is still valid. If the card issuer (the donor’s bank) has renewed the card — which is common for active accounts — the processor already knows about the updated card details and processes the charge successfully. The dashboard’s Expired label reflects only what WeGive has stored locally. It does not check with the processor for the card’s current real-world status.

​
Do I need to do anything?

No action is required. As long as charges are processing successfully, the Expired badge is purely cosmetic. The processor handles the actual card validity independently.

​
If you want the displayed expiration to match reality

If the Expired label is confusing for your team and you would like the dashboard to reflect the card’s current expiration date:
  • Ask the donor to update their card through the Donor Portal. When a donor removes and re-adds their card (or updates it through the portal’s payment method management), the current expiration date is captured from the processor, and the dashboard will show the correct date going forward.
  • For organizations using Braintree, enabling Card Account Updater (CAU) in your payment settings will automatically refresh stored card details when the issuer reports changes. Once enabled, cards that are renewed by the issuing bank will update in the dashboard without any action from the donor. Contact support if you need help enabling this feature.
Last modified on October 21, 2026