Reso 2021-3185 - Laserfiche WebLink

Home Browse Search

15.8 Contractor or system must provide a way for Purchasing Entities to track reported fraud transactions to completion (closure). WEX offers a comprehensive fraud prevention and management program. Most recently, we have been beta testing an enhanced customer facing claims management interface with a large government customer. This tool allows customers to view each claim, the claim number, type of claim, card number, date reported, age of claim, total dollars, claim status and date of resolution. Upon resolution, an email is sent to the fleet for notification. The information in the interface can be exported into a report (on demand or scheduled) so it can be easily shared with others in your organization. Once beta testing is complete, we expect to deploy this solution to other large customers. We expect this to be in place before the contract effective date of January 1, 2021. 15.9 Contractor or system must be able to resolve mass attacks (i.e. fraudulent low value charges on multiple cards at once) without requiring action from the Purchasing Entities. This type of attack is not a risk to WEX Fleet card holders, as our transaction processing occurs on a closed -loop network, not over the Internet. Regarding other Web -based applications, OWASP standards are built into development processes, and manual testing is performed in addition to peer review as required by our SDLC. WEX uses an automated dynamic application security testing (DAST) solution that scans web applications to find vulnerabilities and provide guidance on remediation. WEX receives vulnerability announcements for relevant systems from vendors, third parties, NIST, FDIC, FBI, and other threat feeds, and has a dedicated security operations team managing and maintaining the vulnerability management program. The vulnerability management procedure requires a ticket to be generated and assigned to Information Technology operations teams for patching. 16. DISPUTED TRANSACTIONS Purchasing Entities will pay according to the contract payment terms; however, in instances of dispute, the charges must be placed in suspense until there is resolution. The Contractor must propose a timely dispute procedure to ensure that the payment network charge back rights do not expire. If upon resolution of a dispute it is found that the transaction was actually an authorized charge, the Participating Entity will be liable for the payment within the payment terms as described herein. 16.1 Contractor must provide a resolution procedure for dealing with disputed transactions resulting from unauthorized charges, errors in cardholder billings, or problems with charges for merchandise or services that are not resolved between the Cardholder and Merchant. Disputed Transaction Detail • How users will notify the Contractor • Ability to dispute transactions electronically as well as track through final resolutions of the charge • Instructions for cardholders • Instructions (including invoice adjustments) for billing offices • Provisions for prompt investigation of disputed items MASTER AGREEMENT No. 00819 - FLEET CARD SERVICES PAGE 135 OF 138