Skip to end of banner
Go to start of banner

Fraud Liability Shift - Lost/Stolen/Non-Received (4799)

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Timeframes

120 days from the Network Processing Date of the Presentment

Conditions

The Issuer must meet all the following conditions:

  1. The Transaction information must be submitted to the GNS Fraud Repository as fraud either by manually entering into the WFIS or electronically transmitting it to the GNS Fraud Repository prior to the Chargeback submission date.
  2. The Cardmember Account must be added to the Exception File no later than the Network Processing Date of the Chargeback.
  3. The Issuer was certified by AEGNS to process AEIPS Chip/PIN Card Transactions on or before the Transaction date.
  4. The Issuer for the Transaction is located in an AEGNS-designated country for AEIPS Lost/Stolen/ Non-received FLS.
  5. The Transaction occurred at an S/E located in an AEGNS-designated country for AEIPS Lost/Stolen/Non-received FLS.
  6. The Transaction occurred on or after the AEGNS-designated AEIPS Lost/Stolen/Non-received FLS effective date for both the Issuer and Acquirer countries.
  7. The Card is identified as chip and PIN and one (1) of the following conditions are met:
    1. The ICC chip/PIN indicator in the POS First Presentment (1240) message indicates that a chip Transaction was not performed, or
    2. The ICC chip/PIN indicator in the POS First Presentment (1240) message indicates that a chip Transaction was performed but the PIN was not used 
      due to the Terminal not being capable or the PIN pad was not working.
  8. For Final Chargeback - This Chargeback is only applicable if the First Chargeback was either a fraud type or one of the following:
    1. 4512 - Multiple Processing
    2. 4516 - Request for Support Not Fulfilled
    3. 4517 - Request for Support Illegible/Incomplete
    4. 4754 - Local Regulations/Legal Dispute

Dependencies

The Issuer must provide all of the following:

  1. Issuer Declaration indicating the date the Account was listed on the Exception File.
  2. Date that the Transaction information was submitted, and that confirmation was received from the GNS Fraud Repository with a fraud type code of lost, stolen, or non-received.

Validations

ValidationValueLogicAssociated Rule(s)
Not Chip Liability Shift EligibleTrue
  • IsCardSecure AND
  • IsChipOnCard
IsChipLiabilityShiftEligible
Consumer-Presented QR transaction that was properly identified in the Authorization Request/0100 message or Financial Transaction Request/0200 message.False
  • posEntryModePan = 3 AND
  • DE 48, Subelement 21 = 11 
IsMCQRTransaction_MC
Authorization Approval after the FNS Date. The issuer approved the transaction after submitting two or more chargebacks involving the same Mastercard card account (for this purpose, “account” means primary account number [PAN] and expiration date) for any of the following message reason codes: 4837, 4840, 4870, or 4871. Message reason code 4863 first chargebacks will be included in the FNS count once the FNS fraud chargeback count is two or greater.False

2 or more previous disputes with reason code 4837, 4840, 4870, or 4871 on the same card number

 IsApprovedAfterFNS_MC
FNS Counter Exceeds 15 Fraud-Related Chargebacks. The issuer submitted more than 15 chargebacks in aggregate involving the same account for message reason codes 4837, 4840, 4870, or 4871.False15 or more previous disputes with reason code 4837, 4840, 4870, or 4871 on the same card numberIsFNSCountReached_MC
A Digital Secure Remote Payment (DSRP) transaction or any subsequent transaction for a related partial shipment or recurring payment.False
  • cardholderActivatedTerminalLevel = 6 
  • terminalOperatingEnvironment in (2,4) 
  • cardDataInputMode = R
  • IsFaceToFaceTransaction != True
IsDSRPTransaction_MC
A valid EMV chip transaction occurred and DE 55 and related data was provided in the Authorization Request/0100 message or Financial Transaction Request/0200 message (when online-authorized) and the First Presentment/1240 message.False

integratedCircuitCardRelatedData is not null

IsChipTransaction_MC
A magnetic stripe-read or key-entered transaction occurred and was properly identified as the result of technical fallback in the Authorization Request/0100 message and in the First Presentment/1240 message.False
  • posEntryModePan in (79,80) OR
  • posEntryModePan = 01 AND
  • IsHybridPOSTerminal (posCardDataTerminalInputCapability in (3,5,8,9) AND cardDataInputCapability in (5,C,D,E,M))
IsFallBackTransaction_MC
The Authorization Request/0100 message contained a service code value other than 2xx or 6xx in DE 35 (Track 2 Data) or DE 45 (Track 1 Data)False@String.startsWith(serviceCode), "2" OR  @String.startsWith(serviceCode), "6"IsChipServiceCode_MC
The transaction was a mail order, phone order, e-commerce, or recurring payment transaction.False
  • cardholderPresentData in (2, 3, 4, 5) OR
  • cardDataInputMode = "S" 
IsMOTOTransaction_MC
Mastercard Commercial Payments Account. The transaction was a Mastercard Commercial Payments Account transaction. A Mastercard Commercial Payments Account transaction occurs when PDS 0002 (GCMS Product Identifier) was MAP (Mastercard Commercial Payments Account) in the First Presentment/1240 message.False

gcmsProductIndentifier = "MAP"

IsMCCommercialPayment_MC

Related Questionnaires

Fraud Questionnaire



  • No labels