Force-Sale Fraud, and How to Protect Against It (Pt. 2)

A couple of weeks ago, we posted the first part of an overview from Visa on how to spot, and guard, against Force-Sale Transactions.

Sometimes called a “force capture” or “offline transaction,” these transactions let a merchant bypass the usual authorization process by manually entering a code. The transaction is then routed through clearing and settlement, eventually “force-posted” to the issuer.

POS devices and payment gateways have supported this “Force Sale” function almost since the earliest days of credit cards themselves. And while the need for this function has diminished as processing systems have evolved, devices, and merchants, still offer such payment methods as a standard feature, or processing option.
So, in our first part, we showed you some ways to spot signs of fraud during Forced Posting. This week we show you ways to guard against it.
• Add acquirer access controls to the “Force Sale” function.
• Disabling the default use of the “Force Sale” function by using these acquirer access controls.
• Consider having your processor perform force-posted transactions on the merchant’s behalf if only a few such transactions are required in a given cycle
Additionally, other “Force Sale” access can be implemented, especially via gateway updates, which can disable automatic “Force Sale” functions.
And in other news: Changes will be coming to both the AVPS Website, and this blog! We’ve been working behind the scenes to give you a more accessible online experience, in terms of information that you need, is timely, helps you find new services and equipment, etc.
You’ll be seeing the changes here, and in the newsletter, and they’ll be rolled out shortly.
And you can still contact your AVPS Rep throughout, to learn more about Force Sale fraud protection, upgrading gear, and anything else!
See you… in a week!

Tags: , , ,

No comments yet.

Leave a Reply

You must be logged in to post a comment.