How to Configure Fraud Prevention Rules in the EPG Portal

Purpose: Block or review transactions originating from known fraudulent IP addresses. 

How it works

• Compares the shopper’s IP address against your High‑Risk IP list.
• Matching transactions can be Declined or Held for review (payment‑method dependent).  

Step‑by‑step

1. In Fraud Prevention Rules, locate Check for high‑risk IP addresses.
2. Tick  the checkbox to enable the rule.
3. Choose the action:
   Decline – transaction is automatically rejected.
   Hold for review – transaction is paused for manual assessment
4. Maintain your IP block list as required.
5. Click SAVE CHANGES.

Best practice: Use Decline for repeated or confirmed fraud sources.

Purpose: Prevent unusually large transactions that fall outside normal purchase behaviour.

How it works

• Flags any transaction that exceeds the maximum value you define.
• You control whether those transactions are declined or reviewed.

Step‑by‑step

1. Enable Set maximum transaction amount.
2. Enter the maximum allowed transaction value.
3. Choose the action:
   Decline – over‑limit transactions are rejected.
   Hold for review – transaction is paused for your decision.
4. Click SAVE CHANGES.

Tip: Set the limit slightly above your highest legitimate basket value.

Purpose: Reduce fraud and shift liability to the card issuer where authentication succeeds.

How it works

• Applies when a transaction does not result in a liability shift after 3D Secure.
• You decide how non‑authenticated transactions are handled.

Step‑by‑step

1. Enable Enforce 3D Secure authentication.
2. Select how to process transactions without liability shift:
   Decline
   Hold for review
3. Click SAVE CHANGES.

Important: This rule is strongly recommended and is mandated in the UK & EU for most eCommerce transactions.

Purpose: Verify that the billing postcode matches issuer records.

How it works

• Compare the postcode provided at checkout with the issuer’s data.

Step‑by‑step

1. Enable Check for AVS postal code mismatch.
2. Choose the action:
   Decline
   Hold for review
3. (Optional) Enable Apply this rule when AVS could not be performed.
4. Click SAVE CHANGES.

Use case: Particularly effective for UK, EU and US card payments.

Purpose: Validate the billing street address against issuer records.

How it works

• Detects inconsistencies in the street line of the billing address.

Step‑by‑step

1. Enable Check for AVS street mismatch.
2. Select Decline or Hold for review.
3. Click SAVE CHANGES.

Tip: Pair with postcode checks for stronger address verification.

Purpose: Ensure the card security code matches issuer data.

How it works

• Flags transactions where the CVV/CVC is incorrect or missing.

Step‑by‑step

1. Enable Check for card security code mismatch.
2. Choose how mismatches are handled:
   Decline
   Hold for review
3. Click SAVE CHANGES.

Best practice: Decline mismatches for one‑off eCommerce payments.

Purpose: Block transactions using billing addresses from high‑risk regions.

How it works

• Compares the billing country against your High‑Risk Country list.

Step‑by‑step

1. Enable Check for high‑risk billing country.
2. Define your list of restricted countries.
   
3. Choose Decline or Hold for review.
4. Click SAVE CHANGES.

Purpose: Identify risk based on where the card was issued.

How it works

• Matches the card’s issuing country against your risk list.

Step‑by‑step

1. Enable Check for high‑risk issuing country.
2. Configure the list of high‑risk issuing countries.
   
3. Select Decline or Hold for review.
4. Click SAVE CHANGES.

Purpose: Block known compromised or fraudulent cards.

How it works

• Compares transactions against a merchant‑maintained block list.

Step‑by‑step

1. Enable Check for high‑risk card numbers.
2. Add card numbers to your block list as required.
   
3. Choose Decline or Hold for review.
4. Click SAVE CHANGES.

Note: Use only for confirmed fraud cases.

Purpose: Prevent rapid repeat attempts using the same card.

How it works

• Caps the number of transactions per card within a defined time window.

Step‑by‑step

1. Enable Limit card use frequency.
2. Set:
   Maximum number of transactions
   Time period (e.g. per hour / per day)
3. Define the action when the limit is exceeded:
   Decline
   Hold for review
4. Click SAVE CHANGES.

Ideal for: Digital goods, subscriptions, and high‑velocity attack protection.