Fraud Overview

  1. Home
  2. APIs
  3. Fraud Overview

Fraud API enables a financial institution or cardholder to manage, mitigate fraud losses and create travel exemptions while minimizing friction for the consumer.

 

Platform Support: DBE=Debit Enhanced EPOC, CGW=Credit Gateway, CSL=Credit Select

 

Features

  • Cardholder Alerts

    Give cardholders security functionality to confirm potential fraud, unblock their card, and increase retention.

  • Convenient Experience

    Empower cardholders to manage exemptions as well and quickly respond to fraud notifications.

  • Verification

    Retrieves media addresses and methods that can be used for cardholder verification. 

     

    Fraud Case feature provides the functionality to search and update real-time Fraud Case information.

    • Case Search: Search for Fraud cases based on institutions, dates, case status, case number and cardholder details.
    • Case Details: Returns Fraud case detailed information for a given case number.
    • Case History: Returns Fraud case history details for a given case number.
    • Case Transactions: Returns Fraud case Authorization transactions for a given case number.
    • Case Update: Updates Fraud Case details for a given case number.
    • Case Rules: Returns Fraud Case rules for a given case number.

                       

           

     

     

    Fraud Alert API provides integration partners the ability to receive alerts for potential fraudulent transactions, retrieve case data for fraudulent cases, and notify Fiserv of the results of an alert notification.

    • Search Case: Retrieve information for fraud cases from Fiserv.
    • Alert Outcome: Notify Fiserv of updates to a case under review. Fiserv returns a response that identifies if a case outcome request is accepted or if the request is rejected and why the request was rejected.
    • Case Close: Notify Fiserv of a case for potential fraud being closed on the vendor platform.   

                   

    Travel Exemptions API enables collection and application of all travel exemptions for a specific card number. Any cardholder updates are captured and used by other web services in the authorization rules for each card transaction, reducing false declines and giving users more control over how they use their card. 

    • Search Exemptions: Obtain information on all existing travel exemptions for the requested card number.
    • Add Exemptions: Add travel exemptions for the requested primary account number (PAN)\, up to the maximum of two lists. Cardholders can make exemptions by state or country.
    • Update Exemptions: Update existing travel exemptions for the requested primary account number (PAN).
    • Expire Exemptions: Terminate existing travel exemptions at any time to create a new list, expiring the old version to enable the new list.

                    

    FAQs

    Are travel notices available in online banking within the Travel Exemptions functionality?

    The feature is a web-message specification that can be coded to make this possible; however, the online banking tool will need to be modified as well coding to use the service to send and receive the necessary information will need to be done.

    Can different start and stop dates be set for different countries with the Travel Exemptions feature? For instance, if someone is traveling to five different countries, but to one country per week?

    No, exemptions are maintained by group; the group has its own start and end dates.  Each group can contain up to 15 locations (countries and/or states). 

    Does the Travel Exemptions feature allow the cardholder to enter future travel plans?

    Yes, each cardholder can have two exemptions configured each containing up to 15 locations (states and/or countries).  Each exemption has start and end dates and times.   

    Exclusions are set by the financial institution through Client Central and provided as part of the Travel Exemptions feature. Do these states/countries need to be excluded from the consumer user interface?

    Design of the consumer or internal user interface is outside of the scope of Travel Exemptions feature. However, if an excluded state or country is sent as an exemption an error response message will be sent.

    How does the Travel Exemptions feature work?

    Updates will need to be made to the system you want to integrate so that your cardholder or internal staff can enter the necessary data.  That system sends an initial “getTrvlExemptionsList” so that current cardholder record information can be displayed.  Fiserv finds the cardholder’s record and sends all current state and country exemptions along with any location exclusions where you have indicated you don’t want automated exemptions configured.  The cardholder or internal staff make the changes and a follow up message (add, update or expire) is sent to Fiserv.  Fiserv reviews the information and sends back the response (success or error message).   

    If a cardholder calls and says they are driving to a certain state. Is it best to list all of the states under the travel exemptions that they are driving through and the dates?

    Yes.

    Is there a unique error code the Travel Exemption feature detects a request to add a country in the financial institution’s exclusion list?

    Yes. The unique code for this scenario WS205.This is different than when a state or country validation can’t occur (e.g. CA for CAN) whose code is WS204.  

    What are the benefits of the Travel Exemptions feature to the financial institution and the cardholder?

    This feature offers the ability to integrate from your own applications into to the Fiserv risk systems in real-time.  It gives you flexibility to have your cardholders to self-service through existing tools they know. 

    What are the prerequisites for implementing the Fraud Alert feature?

    All clients who participate in a Risk Solution Set (Risk Essentials, Risk Advisor or Risk Advantage) can implement the Fraud Alert feature.

    What is the Fraud Alert feature?

    This feature allows an entity outside of CWSi Card Management to be able to retrieve case data regarding fraudulent cases, notifies Fiserv of case results or a case closed. The data contains the case information including card details and up to three (3) transactions that may be considered fraud. This allows the client to determine the locations of where notifications are sent internally and to consumers.

    What is the Travel Exemptions feature?

    This is a RESTful message that allows an entity outside of the CWSi card management system to be able to update the cardholder record regarding state and country exemptions.  This will require coding to specification and completing a certifications process as well as interfacing the API to the user interface (for example:  digital app or online banking service).  

    What list of countries should be displayed in the internal system that feeds the Travel Exemptions feature??

    A standard ISO country list can be used, the API requires 3-character country values and 2-character state values.  You will need to decide how you want to work with your exclusion list.  Some people don’t display these options and others choose to simply let the error message return and address it then. 

    What other risk services does my financial institution require prior to consuming the Travel Exemptions feature?

    You need to utilize at least one of the following risk rule tools – TranBlockerSM, Card Risk Mitigation: EnFact® or Card Risk OfficeSM Advantage: RuleManager.  If you are currently on Card Risk Office Essentials, Card Risk Office Advisor or Card Risk Office Advantage) you are able to utilize the Travel Exemptions feature.

    Will the Fraud Alert feature replace my existing notifications?

    No. Alerts sent through the Fraud Alert feature are in addition to the existing notifications you are currently sending. When a case is created, the Fraud Alert feature is initiated in conjunction with the first notification type you have in your existing notifications. If a case is closed as “NO FRAUD,” “FRAUD” or the card status is changed to a “Closed” status, the contact attempts stop through both the API and the existing channels, similar to the existing process.

    With the Travel Exemptions feature, how are exclusion groups created?

    This is done within the card management system of Debit Processing: Client CentralSM.  A maximum of two exclusion groups can be created.  A maximum of 51 State/Country codes can be part of an individual exclusion group.  The exclusion groups are kept at the client (LOGO) level and contain up to 50 BINs.