How Companies Should Approach Friction in Fraud Prevention

5 min read

Combining fraud detection with identity proofing lets teams respond to advanced threats without adding unnecessary friction. Once those systems share signals, you can tune controls based on risk and route only the right users into step-up checks.

A client of ours also had a problem with a persistent fraud group attempting to bypass their fraud tool. While their fraud tool detected the majority of accounts, it wasn’t slowing down new attempts. The fraudsters would create entirely new accounts with new residential IPs, devices, emails, cards, etc. to try again with minimal resource costs. Outright bans weren’t working and didn’t teach the fraudsters a lesson. Instead, they leveraged Trust Swiftly to add in friction to these users that they knew regular customers could complete, but the fraudsters would have trouble doing. This directed the fraudsters to a journey with increasing scrutiny to complete the identity verifications. In the end, the fraudsters ultimately gave up and have yet to return exhausting their resources. Building a steep incline for known fraudsters is an easy way to stall them out and make sure they stay away from your business for the long-term.Automate Your Customer Journey

Dynamic friction will also allow the people you usually reject outright to be given a second chance. The next evolution will be dialing back any friction you have in your onboarding process. People like to get to their destination fast. However, a brake check after the initial sign up or transaction is a much better experience than turning off their car. This allows you to put the majority of your users in auto-piloted journeys enabling them to interact with your business faster. If you want to learn how to implement dynamic friction for your business, contact us, we can help optimize your customer’s experience with Trust Swiflty.


About the Trust Swiftly Team

We publish practical guidance on identity assurance, fraud prevention, and FedRAMP-aligned controls for high-risk workflows.

Comments