4) Gateway Rules for Fraud Prevention using Account Financial Transactions.

This Blog entry is from the Getting Started in Jube section in Learn Jube.

In anticipation for this Blog entry, the all elements in the Account Financial Transactions XML document has been represented as a Request XPath:

1.PNG

All Request XPath has been configured as Response Payload hence will be returned in the HTTP response:

2.PNG

Gateway Rules are pre filtering and sampling to reduce the transaction traffic volume for the processing of intensive model functions. Transactions will only proceed to subsequent steps in model processing in the event that Gateway Rule matches. Upon a Gateway Rule matching, it will be tested against a random sample as another means to reduce the volume. The random sample at the Gateway Rule level is used quite often in Advertising Technology where there may be an abundance of advertising impressions available yet it is not practical to acquire all, hence processing need only take place upon a smaller yet representative sample.

The page is available by navigating through the menu as Entity Models > References > Gateway Rules. The page is presented as a tree objects for the purposes of administering a model child objects:

3.PNG

The Page exists to create Gateway Rules which are code fragments will will be compiled into the Jube Engine. Gateway Rules accept data objects and tests the code fragment for equality, returning a boolean flag to that effect. The Rule and Code Constructor Comprises the following data Objects:

Name

Description

Data

The fields created in the Request XPath page and Inline Scripts (if allocated).

To add a new Gateway rule, click on the Entity Model in the tree towards the left hand side:

4.PNG

The parameters for the Gateway Rule are described as follows:

Name

Description

This Example

Gateway Sample

A percentage value, between 0 and 1, detailing the sample that should be allowed through to subsequent processing. The sample will only be taken in the event that the Rule returns as true. For example, if the Gateway Sample is set to .2, it would imply that only 20% of the matching transactions will be passed through for subsequent processing. It is extremely useful in Advertising Technology where there is an extremely large volume of impressions yet it is not practical for each impression to be acquired, hence a representative sample of the large universe is adequate.

1 (for 100%)

Max Response Elevation

Upon a Gateway Rule Matching, the Maximum Response Elevation is set such to provide some risk management to the magnitude of the response elevation. For example, if the Response Elevation is used to instruct a bid, the open end of this could be cause for alarm. This value is the largest response elevation that may be responded, with any values exceeding this value being truncated to this value. Keep in mind that there are similar limits at the model level also.

11.0000

Complete the parameters for the Gateway Rule as the aforementioned parameters and as below:

5.PNG

Only in the event that a Gateway rule matches will processing continue. If no Gateway rules match, the response message will simply be sent back upon termination of processing:

6.PNG

The the event that no subsequent processing has taken place, yet there is configuration in place, it is most likely that an event has failed to match upon a Gateway Rule.