Verifone Central

Overview

Verifone's Blocking Rulesets feature allows merchants to set certain rules, based on which transactions will automatically be blocked by Verifone, without the cardholder being informed about the transaction decline reason. This way, merchants can save fees for transactions that are not forwarded for further processing. If the transaction activates a blocking ruleset, it is declined by Verifone.

Availability

The Blocking Rulesets in Verifone Central can be used by any user, if they have a Merchant Admin role.

Blocking rulesets in Verifone Central

Blocking rulesets can be set for any merchant entity; every child entity will inherit the blocking rulesets of the ancestral entities, but the blocking ruleset(s) can only be viewed for the merchant entity for which they were set up.

Within a blocking ruleset, you can set any of the following rules:

1. Amount − the rule is triggered if the transaction amount fulfils the operator criteria. The value field accepts any number. The following operators are permitted:
   
   • is less than
   • is less than and equal to
   • equals to
   • is not equal to
   • is greater than or equal to
   • is greater than
2. Currency Code − the rule is triggered if the transaction currency code fulfils the operator criteria. The value field is a drop-down of all transaction currency codes that Verifone accepts. The following operators are permitted:
   
   • equals to
   • is not equal to
3. Customer − the rule is triggered if the shopper's name or email address fulfils the operator criteria. The value field accepts any text. The following operators are permitted:
   
   • equals to
   • is not equal to
4. Customer Country Code − the rule is triggered if the shopper's country code fulfils the operator criteria. The value field is a drop-down of all country codes that Verifone accepts. The following operators are permitted:
   
   • equals to
   • is not equal to
5. Customer IP − the rule is triggered if the shopper's IP address fulfils the operator criteria. The value field accepts IP-formatted content. The following operators are permitted:
   
   • equals to
   • is not equal to
6. Customer IP Country − the rule is triggered if the country code of the shopper's IP address fulfils the operator criteria. The value field is a drop-down of all country codes that Verifone accepts. The following operators are permitted:
   
   • equals to
   • is not equal to
7. Issuer Country − the rule is triggered if the country code of the shopper's payment card issuer fulfils the operator criteria. The value field of all country codes that Verifone accepts. The following operators are permitted:
   
   • equals to
   • is not equal to
8. Entity − the rule is triggered if the merchant entity that initiated the transaction fulfils the operator criteria. The value field accepts any number. The following operators are permitted:
   
   • equals to
   • is not equal to 

Workflow

Add a blocking ruleset

To add a blocking ruleset, follow these steps:

1. Log in to your Verifone Central account.
2. Navigate to Administration and click on Blocking Rulesets.

 3. Provide a label for your new ruleset and select the rules you want to add from the drop-down list. Once you select a rule and its values, click on Add rule.

4. After adding the desired rules to your new ruleset, click on Create ruleset.

 5. Your new ruleset is created.

 6. You can add a new ruleset by clicking on Add new ruleset. You can set multiple rulesets for a merchant entity.

Edit a blocking ruleset

To edit/change a ruleset, follow these steps:

1. Log in to your Verifone Central account.
2. Navigate to Administration and click on Blocking Rulesets.
3. Click on the ruleset you want to edit.
4. In the next window, click on Edit ruleset.
5. Update the ruleset and click Save changes.

Verifone Validation Logic

To provide an example of the Verifone validation logic, let us assume that you set up the following two blocking rulesets for a given merchant entity:

1. Blocking Ruleset A
   
   • Rule 1: Issuer Country equals to Country A
   • Rule 2: Amount is greater than 100
   • Rule 3: Currency Code equals to Currency Code B
2. Blocking Ruleset B
   
   • Rule 1: Customer Country Code is not equal to Country Code C

After saving the blocking rulesets, transaction #001 is initiated with the merchant entity with the following properties:

• 99 Currency Code B with Issuer Country A from Shopper Country D

And the following logic is applied by the Verifone Validation Service for Transaction #001:

• Blocking Ruleset A, Rule 1 is triggered
• Blocking Ruleset A, Rule 2 is not triggered
• Blocking Ruleset A, Rule 3 is triggered
• Blocking Ruleset A is not activated
• Blocking Ruleset B, Rule 1 is triggered
• Blocking Ruleset B is activated
• Result: The Transaction is blocked by the Verifone Validation Service

Transaction #002 is initiated with the merchant entity with the following properties:

• 101 Currency Code A with Issuer Country B from Shopper Country C

The following logic is applied by the Verifone Validation Service for transaction #002:

• Blocking Ruleset A, Rule 1 is not triggered
• Blocking Ruleset A, Rule 2 is triggered
• Blocking Ruleset A, Rule 3 is not triggered
• Blocking Ruleset A is not activated
• Blocking Ruleset B, Rule 1 is not triggered
• Blocking Ruleset B is not activated
• Result: The transaction is not blocked by the Verifone Validation Service, and is sent for further processing

Blocking rulesets use cases

Amongst others, Verifone's blocking rulesets feature can be used for use cases such as:

• If there are any IPs or customers that are known to be fraudulent, you can preemptively block them to avoid future fraudulent activities.
• Also, as a merchant, you might be asked by an acquirer or by a local government to comply with regulations or national laws and not be in business with certain countries.