Fraud Prevention Service
- Former user (Deleted)
What is the PayU's fraud preventation service?
Payu offers an optional online fraud prevention service to its merchant and takes advantage of the ReD Shield® online fraud prevention service from ReD, a leading global provider of fraud prevention and payment services.
How does it PayU's fraud preventation service work?
Once a store is configured for the service subsequent transactions will undergo an optional fraud check behind the scenes. Based on the fraud check, a transaction could have ay of 3 possible outcomes:
- APPROVE
This result indicates that a transaction has passed all of the rules on the fraud platform and the transaction has been sent to the bank for verification. - DENY
This result indicates the transaction did not pass the various rules on the Fraud platform and as such the transaction was denied - CHALLENGE
This result indicates that the transaction requires manual intervention or case managment e.g. bank verification. The transaction was sent to the bank for verification, but pending the outcome of the case management it will either be aproved or denied.
Â
For CHALLENGE, PayU’s fraud team can manually review the transaction and approve or reject the transaction. During onboarding, the merchant is able to configure whether to attempt payment in the following scenarios:
CHALLENGE response from Fraud system (ProcessFraudChallenge) | E-commerce merchants may wish to still take payment and put the order on hold (pending case manager review) before shipping. |
Validation failure on fraud data (ProcessFraudValidationFailure) | When validation fails, a fraud check is not completed. This should usually just be related to a specific user. As a result, taking payment automatically should only expose the merchant to risk on this transaction |
Fraud system is down (ProcessFraudDown) | If the fraud system was to ever go down, then the merchant may wish to halt transactions. All transactions would then not be going through the fraud system |
Â
All payments with an associated fraud check have 3 possible high level outcomes with multiple fraud results for each outcome.
Payment Successful
| ||||||||||||
Payment Failed
| ||||||||||||
Fraud Failed & Payment Not Attempted
|
Â
PayU will return a ResultCode and a Fraud.ResultCode for each transaction. The ResultCode provides the result of the payment transaction and the Fraud.ResultCode provides the result of the fraud check. When a fraud check returns a CHALLENGE, the result of the case review will update the Fraud.ResultCode. The FraudResultCode therefore holds the fraud state of the transaction
What additional fields should you send for the Fraud the preventation service work?
PayU can apply a synchronous fraud check when a RESERVE or PAYMENT transaction type are completed. If a fraud check is to be completed, additional customer and basket information is required to calculate a fraud score.
AN = Alphanumeric, N = numeric, A = Alpha. Numbers represent min and max lengths
Parameter Name | Description | Data type | Mandatory | ||||||||||||||||||||
Customer | |||||||||||||||||||||||
Address1 | Customer address line 1 | AN : 1 – 30 | N | ||||||||||||||||||||
Address2 | Customer address line 2 | AN : 1 – 30 | N | ||||||||||||||||||||
AddressCity | Customer address city | A : 1 – 20 | N | ||||||||||||||||||||
StateCode | Customer address state code | A : 2 – 2 | N | ||||||||||||||||||||
CountryOfResidence | Customer Country Code - ISO-Alpha 3 | A : 3 – 3 | N | ||||||||||||||||||||
PostCode | Customer Post/Zip Code (remove '-' from field) | AN : 1 -9 | N | ||||||||||||||||||||
IP | Source IP of customer - Format: nnn.nnn.nnn.nnn | A : 7 – 45 | Y | ||||||||||||||||||||
Known | Previous Customer Flag - format Y or N | A : 1 – 1 | N | ||||||||||||||||||||
Fraud | |||||||||||||||||||||||
CheckFraudOverride | Used to override the default merchant fraud setting. If set to true, no fraud check will be completed | A : 4 – 4 | N | ||||||||||||||||||||
PcFingerPrint | See separate guide for full integration details | AN : 1 - 4000 | N | ||||||||||||||||||||
MerchantWebSite | Merchant source website domain | AN : 1 – 60 | Y | ||||||||||||||||||||
Basket | |||||||||||||||||||||||
ShippingId | Shipping ID | AN: 1 - 16 | N | ||||||||||||||||||||
ShppingFirstName | Shipping First Name | AN: 1 – 30 | N | ||||||||||||||||||||
ShippingLastName | Shipping Last Name | AN: 1 – 30 | N | ||||||||||||||||||||
ShippingEmail | Shipping Email Address - value must contain @ | AN: 1 – 45 | N | ||||||||||||||||||||
ShippingAddress1 | Shipping address line 1 | AN: 1 – 30 | N | ||||||||||||||||||||
ShippingAddress2 | Shipping address line 2 | AN: 1 – 30 | N | ||||||||||||||||||||
ShippingAddressCity | Shipping address city | A: 1 - 20 | N | ||||||||||||||||||||
ShippingStateCode | Shipping address state code | A : 2 – 2 | N | ||||||||||||||||||||
| ShippingCountryCode | Shipping Country Code - ISO-Alpha 3 (http://en.wikipedia.org/wiki/ISO_3166-1_alpha-3) | A: 3 – 3 | N | ||||||||||||||||||||
| ShippingPostCode | Shipping Post/Zip Code (remove '-' from field) | AN : 1 - 9 | N | ||||||||||||||||||||
ShippingPhone | Shipping Phone | N : 11 – 19 | N | ||||||||||||||||||||
ShippingFax | Shipping Fax | N : 11 – 19 | N | ||||||||||||||||||||
ShippingMethod |
| A : 1 - 1 | N | ||||||||||||||||||||
Basket – Item Array | |||||||||||||||||||||||
RecipientFirstName | Recipient First Name | AN : 1 - 30 | N | ||||||||||||||||||||
RecipientLastName | Recipient Last Name | AN : 1 – 30 | N | ||||||||||||||||||||
RecipientEmail | Recipient email address | AN : 1 – 45 | N | ||||||||||||||||||||
RecipientAddress1 | Recipient Address Line 1 | AN : 1 – 30 | N | ||||||||||||||||||||
RecipientAddress2 | Recipient Address Line 2 | AN : 1 – 30 | N | ||||||||||||||||||||
RecipientCity | Recipient City | A : 1 – 20 | N | ||||||||||||||||||||
RecipientStateCode | Recipient State/Province Code | A : 2 - 2 | N | ||||||||||||||||||||
RecipientCountryCode | Recipient Country Code - ISO 3 Digit Alpha | A : 3 – 3 | N | ||||||||||||||||||||
RecipientPostalCode | Recipient Post/Zip code (remove '-' from field) | AN : 1 – 9 | N | ||||||||||||||||||||
RecipientPhone | Recipient Phone Number | N : 9 – 19 | N | ||||||||||||||||||||
ProductCode | Item Product Code | AN : 1 – 12 | N | ||||||||||||||||||||
Sku | Item SKU | AN : 1 – 12 | N | ||||||||||||||||||||
Description | Item description | AN : 1 – 26 | N | ||||||||||||||||||||
Quantity | Item quantity | N : 1 – 8 | N | ||||||||||||||||||||
CostAmount | Item cost amount - R5.00 should be sent as 500 | N : 2 – 8 | N | ||||||||||||||||||||
Amount | Total Item Amount (item qty x item cost amt), no decimal | N : 2 – 12 | N | ||||||||||||||||||||
ShippingNumber | Item shiping/tracking number | AN : 1 – 19 | N | ||||||||||||||||||||
GiftMessage | Item gift message | AN : 1 - 160 | N | ||||||||||||||||||||
Â
How do I integrate with PayU's fraud preventation service?
The PayU fraud prevention service is offered on both integration methods and documentation is found at the following locations:
- Redirect payment page :-Â please view here
- Enterprise API :-Â please view here