Skip to main content
All CollectionsGiving FormAdvanced settings
What to do when suspected stolen card testing happens on your giving form
What to do when suspected stolen card testing happens on your giving form

How to respond and clean up records after a suspected card testing fraud attempt.

Alex Molina avatar
Written by Alex Molina
Updated over a month ago

If you notice suspicious activity where your Funraise forms are being used to test stolen or unauthorized credit cards, it's essential to take immediate steps to protect your account, prevent fraud, and maintain the integrity of your platform. This article will guide you through handling and mitigating this issue.


1. Refund any fraudulent completed transactions

  • Why: Refunding completed fraudulent transactions helps your payment gateway (e.g., Stripe) learn to better detect and prevent similar transactions in the future.

  • How: Log in to your payment gateway account (typically through Stripe or your chosen provider) and locate the fraudulent transactions.

    • Mark each fraudulent transaction as such and initiate the refund.

    • If your gateway provider requests any additional information regarding these transactions, provide any relevant details to support your case.

  • Note: Refunded transactions will sync the updated status back to Funraise, updating transaction records appropriately in Funraise.

2. Delete any failed transactions using the import tool

  • Why: Deleting failed transactions helps clean up your records and minimizes clutter in your transaction history. This is especially helpful when failed transactions result from multiple attempts with invalid cards.

  • How:

    • Manually: You can delete failed transactions individually from the Transactions section by selecting Delete Transactions in the Transaction's action menu (3 dots).

    • In Bulk: You can delete many failed transactions at once using the import tool (Settings > Imports). If you're using the import tool, you'll need to provide the failed Funraise Transaction IDs and then batch delete the transactions. Be sure to verify that only failed, fraudulent transactions are selected for deletion to ensure legitimate data remains intact.

Did this answer your question?