Data points
Shield uses data points as objects of measurement. They represent categories of (transaction) data and are used in rules and lists.
Standard data points
Here is an overview of all default available data points
Datapoint | Description | Example(s) |
---|---|---|
Amount | Transaction amount | 10.00 |
Card number | Card number of the debit or credit card | 522078******3273 |
Card number category | Card category of the debit or credit card | prepaid, business, gold. |
Card number country | Issuing country of the debit or credit card | NL |
Card number owner type | Owner type of the debit or credit card | personal, commercial, unknown |
Card number type | Card number type of the debit or credit card | credit, debit, chargecard |
Client IP | IP address of the client | 192.123.456.78 |
Client IP country | Country of the IP address of the client | NL |
Currency | Currency of the transaction | EUR |
IBAN | Used IBAN in an IBAN transaction | NL06ABNA1234567890 |
Is recurring | Is a recurring transaction. | True/False |
Is start-recurring | Is a FIRST transaction of a possible series of recurring transactions | True/False |
Payment method | Used payment method in the transaction | VISA |
PayPal account | Used PayPal email address in a PayPal transaction | paypaluser@email.com |
Website key | The registered websitekey of the transactionn | sd6f8s7df6 |
Custom datapoints
Aside from the default available data points, a merchant can create additional data points by defining custom variables. Custom variables are meant to provide additional data through transaction requests. They can be created here. Once a custom variable is created, Shield will automatically regard it as a data point. Not only will the become available to use in fraud rules, but Shield will generate a related block and trust list as well (as it does for each data point in general).