Funraise's April release includes a big upgrade for organizations on our free plan, an update to the Donors Cover Fees public description, and a new tool to mitigate carding fraud which is showing impressive results already.

We've made Funraise's core functionality available to all organizations as a part of our free plan. We're excited to see organizations of all sizes grow with Funraise—for free! New features added to our core platform include:

We've updated the fee description for Donors Cover Fees on the Giving Form. The new description:

When you increase your contribution to cover fees, you're helping [Organization Name] provide a safe and secure giving experience while keeping processing and software costs low.

We've also removed the opt-out message and broken heart emoji. Thanks to everyone who submitted feedback and responded to our recent survey on Donors Cover Fees. This change is a direct result of your feedback.

Next, we're also looking into an improvement that would give donors more flexibility to choose multiple fee coverage points, either with a multi-select or a slider. Based on our recent survey, this was a preferred option for many organizations. This improvement might also include enhanced fee default amounts based on the payment method or donation amount.

We've recently released a new fraud mitigation tool that has had great initial success. This new layer of protection is called a Web Application Firewall (WAF). You can think of WAF as a shield that sits between Funraise’s platform and a world full of fraudsters (or bots). The WAF has sophisticated listening capabilities that detect constantly shifting signals from HTTP traffic sources, determining the trustworthiness of the source as well as the validity of the request, and blocking them appropriately.

We've written more about why nonprofits face carding fraud, how we're protecting organizations, and the success of this most recent innovation.

Read more about this enhancement→

For a quick peek, the chart below shows an early indication of the success of the new Web Application Firewall (WAF). This chart shows a timeline of failed transactions. Failed transactions should occur at a consistent rate, but when carding fraud happens, they don't—the spikes and surges in the chart represent carding attacks where many cards were being tested against a payment form. In carding attacks, the majority of cards fail, which is why a failed transaction chart is a proxy for carding attacks. As you can see, after the introduction of the Web Application Firewall, failed transactions returned to a lower and expected rate.

Projects we're working on now include an updated giving experience, Register to Fundraise, Machine Learning, and Text-to-Give.

Take a peek at our feature preview

See what else we're working on and add your feedback to our Product Roadmap.
​