Find Answers

Find Answers

Specified Languages
British English

What enhancements are coming for Decision Manager Velocity? (currently in Beta)

Doc ID:    C1777
Version:    3.0
Status:    Published
Published date:    08/29/2017
Updated:    08/29/2017


How has Decision Manager Velocity been enhanced?

The Order and Product Velocity Editor has been updated and includes several enhancements listed below.
The following figure shows the new Order Velocity Editor.


Tracking Element

You can now choose up to four tracking elements instead of one. All of the elements that you choose must
be in the transaction and match in order to trigger the rule. You can choose custom merchant-defined data
fields or from all of the following:
  • Account number
  • Billing phone number
  • Billing first name
  • Billing last name
  • Card BIN
  • Customer account ID
  • Customer IP address
  • Customer username
  • Customer password
  • Device fingerprint
  • Email address
  • Merchant reference number
  • Order value
  • Proxy IP address
  • Shipping address
  • Shipping phone number
  • Smart ID
  • True IP address
If you are the administrator of a group of merchants, you can also choose Merchant ID as a tracking

Apply To

Enhanced Velocity includes the ability to choose the type of orders that the velocity rule should count:
orders under review, accepted orders, rejected orders, and/or failed authorizations. When an order under
review is accepted or rejected, the counts are updated to reflect it.

If you choose Failed Authorizations, Decision Manager will count velocity only if Authorization ran and
received a decline. If Authorization doesn't run or is approved on a transaction, it won't be counted against
velocity rules.

Time Interval

The time interval has been enhanced to include a custom period as well as a calendar period. With the
calendar period, you can still choose a fixed period of time such as a week or month. With the custom
period, you can exclude days.

For example, you may wish to create a rule going back 90 days to 180 days.
  • In the Track back in the past dialog box, enter 180.
  • In the Exclude most recent dialog box, enter 90.


Enhanced Velocity includes the ability to choose a morphing element from the drop-down list. Decision
Manager returns a morphing count when the values of the tracking elements are the same for multiple
transactions, but the morphing element value changes. You can use this value when building custom rules.

Sample Velocity Rule with Multiple Tracking Elements and Morphing Element

In this sample rule, you want to track more than two orders from the same email address and IP address
for 30 days, and note the number of different shipping addresses the orders contain.

Rule Name
Morphing element - shipping address
Tracking Elements
  • Email address
  • IP address
Time Interval
Calendar period - Month to Date
Threshold Order
quantity = 2
Morphing Element Shipping address

This rule is triggered when you receive two or more orders with the same email and IP address in 30 days.
Once these orders have different shipping addresses, you also receive the morphing count. Decision
Manager returns the morphing count when it counts two orders with different values. Even if the rule does not trigger,
Decision Manager returns the morphing count once it is greater than one.

For example, Decision Manager receives three transactions that match the selected elements. The second
transaction has a different shipping address than the first transaction, and the third transaction has yet
another shipping address. Decision Manager returns the morphing count as 3.

To use the morphing count, create a rule with a condition that uses the morphing element. The Velocity
Morphing Count is available in the Rule Editor drop-down menu as shown in the following figure.

Rate This Item