Fraud Free

NOTE: This service is still in evaluation - contact your account manager for further information.

Requirements

  • The corresponding Saferpay licence and thus the existence of a valid identification with a username and password for the Saferpay system.
  • Availability of at least one active Saferpay terminal via which payment can be carried out and availability of the associated Saferpay TerminalId.
  • A Fraud Free contract. Please contact your account manager for further information!
  • JSON-API Spec Version 1.9

API Response

The Fraud Free Service only accepts liability for the transaction if the API response (PaymentPage/Assert response, Transaction/authorize response) contains all of the following attributes with values as specified:

  • In the Liability Container, LiabilityShift is set to true!
  • The LiableEntity equals FraudFree!
  • Within the FraudFree Container, LiabilityShift is set to true!

Info: Should the Fraud Free service not accept liability, 3D Secure is used instead!

Important: The FraudFree-Response will not be visible inside the Saferpay Backoffice. Always save the API-response for further use, e.g. in case of fraud!

Below, you'll find JSON-examples of success and major fail cases, that are returned with the authorization response:

Fraud Free accepts liability


"Liability":{ 
   "LiabilityShift":true,
   "LiableEntity":"FraudFree",
   "FraudFree":{ 
      "Id":"fb126ca6853f4217853df26213da4de8",
      "LiabilityShift":true,
      "Score":x.xx,
      "Investigationpoints":[ 
         "susp_xxx_xx",
         "susp_xxxxx"
      ]
   }
}

Fraud Free rejects liability and fallback to 3D Secure

Example of Rejection due to suspicious client data:

"Liability":{ 
   "LiabilityShift":true,
   "LiableEntity":"ThreeDs",
   "ThreeDs":{ 
      "Authenticated":true,
      "LiabilityShift":true,
      "Xid":"X2lYXwpROW5IBC5tVCQLUlwrRQs=",
      "VerificationValue":"AAABBIIFmAAAAAAAAAAAAAAAAAA="
   },
   "FraudFree":{ 
      "Id":"c6057dcc280448ea8ee51307aadbb276",
      "LiabilityShift":false,
      "Score":0.80,
      "Investigationpoints":[ 
         "susp_bill_ad",
         "susp_machine"
      ]
   }
}

Rejection due to too high authorization-amount:

"Liability":{ 
   "LiabilityShift":true,
   "LiableEntity":"ThreeDs",
   "ThreeDs":{ 
      "Authenticated":true,
      "LiabilityShift":true,
      "Xid":"Gy0mNAETemwEBAhLNhQAVmJcSAc=",
      "VerificationValue":"AAABBIIFmAAAAAAAAAAAAAAAAAA="
   },
   "FraudFree":{ 
      "Id":"faaf76cff7de4b0f9997f941f99a626e",
      "LiabilityShift":false,
      "Score":0.00,
      "Investigationpoints":[ 
         "not_liable_high_amount"
      ]
   }
}

Info: You can simulate rejections, by submitting reject@example.com as the payer e-mail (also see Mandatory Data Points).

Status Change

Liability shift is excluded if the transaction changes to a status as within this list:

Status Description
cancelled Transaction was cancelled by the client prior to shipment
Refund Transaction was refunded
Chbk Client received a chargeback for an unspecified reason
cancelled_claim Chargeback was cancelled

Mandatory Data Points

When using our Fraud Free solution (requires a concerned contract amendment) the transmission of specific parameters is mandatory.

The following data points are mandatory and must contain valid values when using the Fraud Free Service and calling PaymentPage Initialize Request or Transaction Initialize Request:

Data Point Example Validation
DeliveryAddress.Email payer@gmail.com Valid email address
DeliveryAddress.CountryCode DE ISO 3166-1 alpha-2 country code
Payer.IpAddress* 212.243.178.130 Valid IP address

(*) The Payer IpAddress is only mandatory when calling Transaction Initialize Request. With PaymentPage Initialize Request the Payer IpAdress ist detected automatically.

Back to Top