Stopping fraud: putting the foot down

Once you’ve identified the fraud, what you do next to stop those attacks from re-occurring depends on the type of attack itself.

Consider this example: If fraud occurred as a result of people using stolen credit cards to obtain high value goods online, perhaps a review of the policy of the sale of certain goods online or extending identification requirements is required. If neither of these outcomes are suitable, then you could delay postage or not send via express shipping methods, or include a human phone call to the ‘perceived consumer’ to validate or screen the consumer before releasing the goods.

In these types of scenarios there are a number of procedural elements that can implemented to stem the potential fraudulent activity.

And whenever you find one of these issues, there is the concept that you may just start blocking the wrong people and do just as much damage to your brand and reputation.

Once you’ve understood where the fraud is emanating from, then you need to think about the following, before acting:

Does the solution require a change of process, a change of system, a change to the organisation or a mixture?

Does the solution present an impact to funds management and collection?

Does the solution present a change to the way that Customer Service staff deal with customers?

Are you going to be able to protect yourself against future attacks completely in this problem vector or are you reducing the threat and still allowing the attacks, albeit reduced, to occur?

What support will you need from groups within your organisation and how can you best inform them and integrate them to the greater problem solving arena?

The questions above will help guide you through implementing a solution to a fraud problem.