Supported attributes
Review a complete list of attributes supported in Radar rules.
Use the following attributes within Radar to write rules. Learn how to write effective rules.
Payment method specific attributes
Rules that evaluate payment method specific attributes (for example, :card_ or :sepa_) always treat non-Boolean attributes as missing for transactions that don’t use that payment method. Therefore, rules that depend on such attributes can’t act on transactions that don’t use the relevant payment method. Read more on missing attributes.
Bank account information
Attribute | Type | Example Value |
sepa_debit_bank_code | Case insensitive string | 08307 |
The bank code associated with the account used to make the payment. | ||
sepa_debit_country | Case insensitive Country | IE |
The two-letter code corresponding to the country of the customer’s bank account. | ||
sepa_debit_fingerprint | Case sensitive string | example_fingerprint |
The unique identifier of the bank account used to make the payment. | ||
Transaction rule attributes
Write rules using these attributes to evaluate transactions from any payment method screened by Radar.
Risk scores and levels
Attribute | Type | Example Value |
risk_level | Case Insensitive String | normal |
The risk level of a given payment, as determined by Stripe. The supported values are: normal, elevated, highest, not_assessed. | ||
risk_score | Numeric | 50 |
The risk score of a given payment, as determined by Stripe. The values range between 0 (least risky) and 100 (riskiest). By default, a risk score of 65 or above corresponds to a risk level of elevated, while a risk score of 75 or above corresponds to a risk level of highest. You can adjust the thresholds at Risk Settings. | ||
Address
Attribute | Type | Example Value |
billing_address | Case Insensitive String | 1234 Main St #2A Brooklyn, NY 10022 US |
The full provided billing address. | ||
billing_address_line1 | Case Insensitive String | 1234 Main St |
The first line of the provided billing address (typically a street name and number). | ||
billing_address_line2 | Case Insensitive String | #2A |
The second line of the provided billing address (typically an apartment or unit number). | ||
billing_address_postal_code | Case Insensitive String | 10022 |
The postal code (ZIP) of the provided billing address. | ||
billing_address_city | Case Insensitive String | Brooklyn |
The city of the provided billing address. | ||
billing_address_state | Case Insensitive String | NY |
The state of the provided billing address. | ||
billing_address_country | Case Insensitive Country | US |
The two-letter code corresponding to the country of the provided billing address. | ||
shipping_address | Case Insensitive String | 1234 Main St #2A Brooklyn, NY 10022 US |
The full provided shipping address. | ||
shipping_address_line1 | Case Insensitive String | 1234 Main St |
The first line of the provided shipping address (typically a street name and number). | ||
shipping_address_line2 | Case Insensitive String | #2A |
The second line of the provided shipping address (typically an apartment or unit number). | ||
shipping_address_postal_code | Case Insensitive String | 10022 |
The postal code (ZIP) of the provided shipping address. | ||
shipping_address_city | Case Insensitive String | Brooklyn |
The city of the provided shipping address. | ||
shipping_address_state | Case Insensitive String | NY |
The state of the provided shipping address. | ||
shipping_address_country | Case Insensitive Country | US |
The two-letter code corresponding to the country of the provided shipping address. | ||
Amount
Attribute | Type | Example Value |
amount_in_xyz | Numeric | 50 |
The amount of the payment, converted to the currency specified by xyz (for example, amount_in_usd). Specify one of the following supported currencies and Stripe automatically calculates a converted amount to use: aed, ars, aud, brl, cad, chf, clp, cop, czk, dkk, eur, gbp, hkd, huf, idr, ils, inr, jpy, khr, krw, mxn, myr, nok, nzd, php, pln, ron, rub, sek, sgd, thb, try, twd, or usd. For decimal currencies (for example, usd), rules use the base currency unit rather than sub units (for example, dollars, not cents). | ||
average_usd_amount_attempted_on_customer_all_time | Numeric | 50 |
The average amount (in USD) of attempted transactions (charges) for the Customer object on your account within the past 5 years. This value includes payments from 2020 onward. | ||
average_usd_amount_successful_on_customer_all_time | Numeric | 50 |
The average amount (in USD) of charges that resulted in an authorization for the Customer object on your account. This value includes payments from 2020 onward. | ||
total_usd_amount_charged_on_customer_all_time | Numeric | 50 |
The total amount (in USD) of charges from the Customer object that were attempted on your account. This value includes payments from 2020 onward. | ||
total_usd_amount_failed_on_customer_all_time | Numeric | 50 |
The total amount (in USD) of charges from the Customer object that failed (blocked or declined) on your account. This value includes payments from 2020 onward. | ||
total_usd_amount_successful_on_customer_all_time | Numeric | 50 |
The total amount (in USD) of charges that resulted in an authorization for the Customer object on your account. This value includes payments from 2020 onward. | ||
Client information
Attribute | Type | Example Value |
browser | Case Insensitive String | Chrome 103.0.0 |
The customer’s browser name and version. | ||
isp | Case Insensitive String | Cactus Practice ISP |
The customer’s Internet Service Provider (ISP) name. | ||
operating_system | Case Insensitive String | Mac OS X 10.15.7 |
The customer’s operating system name and version. | ||
user_agent | Case Insensitive String | mozilla/5.0 (macintosh; intel mac os x 10_15_7) applewebkit/537.36 (khtml, like gecko) chrome/103.0.0.0 safari/537.36 |
The customer’s user agent. | ||
Customers
Attribute | Type | Example Value |
customer | Case Sensitive String | cus_AeFLnRaI51AbRi |
The Customer object ID supplied with the payment. | ||
total_customers_for_email_yearly | Bounded numeric (≤25) | 10 |
The total number of Customer objects associated with this email on your account. This attribute only includes live mode Customer objects that interacted with your account in the past year. This data updates at most every 72 hours. | ||
total_customers_for_email_weekly | Bounded numeric (≤25) | 10 |
The total number of Customer objects associated with this email on your account. This attribute only includes live mode Customer objects that interacted with your account in the past week. This data updates at most every 72 hours. | ||
total_customers_with_prior_fraud_activity_for_email_yearly | Bounded numeric (≤25) | 10 |
The total number of Customer objects associated with this email that have fraud activity on your account. Fraud activity includes fraud disputes, early fraud warnings, and high risk Radar blocks. This attribute only includes live mode Customer objects that interacted with your account in the past year. This data updates at most every 72 hours. | ||
total_customers_with_prior_fraud_activity_for_email_weekly | Bounded numeric (≤25) | 10 |
The total number of Customer objects associated with this email that have fraud activity on your account. Fraud activity includes fraud disputes, early fraud warnings, and high risk Radar blocks. This attribute only includes live mode Customer objects that interacted with your account in the past week. This data updates at most every 72 hours. | ||
Distance
Attribute | Type | Example Value |
distance_between_billing_and_shipping_address | Numeric | 50 |
The distance (in km) between the provided billing address and the provided shipping address. | ||
distance_between_ip_and_billing_address | Numeric | 50 |
The distance (in km) between the IP address from which the payment originates and the provided billing address. | ||
distance_between_ip_and_shipping_address | Numeric | 50 |
The distance (in km) between the IP address from which the payment originates and the provided shipping address. | ||
Disputes
Attribute | Type | Example Value |
dispute_count_on_ip_all_time | Bounded numeric (≤25) | 10 |
The count of fraudulent disputes associated with charges from this IP address on your account within the past 5 years. This value includes payments from 2020 onward. | ||
dispute_count_on_ip_weekly | Bounded numeric (≤25) | 10 |
The count of fraudulent disputes associated with charges from this IP address on your account in the past week. | ||
dispute_count_on_ip_daily | Bounded numeric (≤25) | 10 |
The count of fraudulent disputes associated with charges from this IP address on your account in the past day. | ||
dispute_count_on_ip_hourly | Bounded numeric (≤25) | 10 |
The count of fraudulent disputes associated with charges from this IP address on your account in the past hour. | ||
Email
Attribute | Type | Example Value |
email | Case Insensitive String | user@example.com |
The email address supplied with the payment. | ||
email_domain | Case Insensitive String | example.com |
The domain of the email address supplied with the payment. | ||
is_disposable_email | Boolean | true |
Identifies if the email address supplied with the payment uses a known throwaway email address provider. Stripe maintains a list of domains corresponding to throwaway email addresses. | ||
The email_domain and is_disposable_email attributes use the email address found in any of the following fields:
- The
receipt_of the paymentemail - The
descriptionof the payment - The
nameof the payment method (for example, if an email address has been provided as the cardholder name) - The
emailof the customer that the payment was created on - The
descriptionof the customer
Email usage
Attribute | Type | Example Value |
email_count_for_billing_address_all_time | Bounded numeric (≤25) | 10 |
The number of emails associated with this billing address from charges on your account within the past 5 years. This value includes payments from 2020 onward. | ||
email_count_for_billing_address_weekly | Bounded numeric (≤25) | 10 |
The number of emails associated with this billing address from charges on your account in the past week. | ||
email_count_for_billing_address_daily | Bounded numeric (≤25) | 10 |
The number of emails associated with this billing address from charges on your account in the past day. | ||
email_count_for_billing_address_hourly | Bounded numeric (≤25) | 10 |
The number of emails associated with this billing address from charges on your account in the past hour. | ||
email_count_for_ip_all_time | Bounded numeric (≤25) | 10 |
The number of emails associated with this IP address from charges on your account within the past 5 years. This value includes payments from 2020 onward. | ||
email_count_for_ip_weekly | Bounded numeric (≤25) | 10 |
The number of emails associated with this IP address from charges on your account in the past week. | ||
email_count_for_ip_daily | Bounded numeric (≤25) | 10 |
The number of emails associated with this IP address from charges on your account in the past day. | ||
email_count_for_ip_hourly | Bounded numeric (≤25) | 10 |
The number of emails associated with this IP address from charges on your account in the past hour. | ||
email_count_for_shipping_address_all_time | Bounded numeric (≤25) | 10 |
The number of emails associated with this shipping address from charges on your account within the past 5 years. This value includes payments from 2020 onward. | ||
email_count_for_shipping_address_weekly | Bounded numeric (≤25) | 10 |
The number of emails associated with this shipping address from charges on your account in the past week. | ||
email_count_for_shipping_address_daily | Bounded numeric (≤25) | 10 |
The number of emails associated with this shipping address from charges on your account in the past day. | ||
email_count_for_shipping_address_hourly | Bounded numeric (≤25) | 10 |
The number of emails associated with this shipping address from charges on your account in the past hour. | ||
IP address
Attribute | Type | Example Value |
ip_address | Case Insensitive String | 192.168.1.1 |
The IP address from which the payment originates. If payment is made with digital_wallet, the IP address might be missing due to obfuscation of the payment’s originating IP address. | ||
ip_address_connection_type | Case Insensitive String | cellular |
The connection type of the IP address from which the payment originates. We identify the following types of connections: cable/dsl, cellular, corporate, dialup. | ||
ip_country | Case Insensitive Country | US |
The two-letter code corresponding to the country-level geolocation of the IP address that the payment originates from. | ||
ip_state | Case Insensitive State | CA |
The ISO code corresponding to the state-level geolocation of the IP address that the payment originates from. If the country doesn’t have a state, this attribute populates with the country’s closest version of a state. | ||
is_anonymous_ip | Boolean | true |
Identifies if the IP address from which the payment originates is a known proxy or Tor exit node. This information updates daily. | ||
is_my_login_ip | Boolean | true |
Identifies if the IP address from which the payment originates has been used to log into your Stripe account. You can use this attribute as a proxy for “is my IP address.” | ||
Other payment details
Attribute | Type | Example Value |
payment_method_type | Case insensitive string | us_bank_account |
The payment method used on the payment. The supported values are: card, sepa_debit, and us_bank_account (ACH direct debit) | ||
charge_description | Case Insensitive String | payment for order #12 |
The description supplied with the payment. | ||
currency | Case Insensitive String | usd |
The 3-digit currency code representing the currency in which the customer paid for the transaction. | ||
destination | Case Sensitive String | acct_19KCB9AlaaEw6AgR |
For Connect users creating destination charges, the destination account on whose behalf the charge is made. | ||
is_checkout | Boolean | true |
is_off_session | Boolean | true |
Indicates when a Stripe Billing payment isn’t triggered by direct user action, or when the off_session flag is set at PaymentIntent confirmation. | ||
is_recurring | Boolean | true |
Identifies if the payment is recurring, for example, from subscriptions. | ||
transaction_type | String | charge |
The type of the transaction. The supported values are: charge, payment_intent, setup_intent. The payment_intent value is only supported for Request Credentials rules. In that case, any Allow, Block, or Review rules run against the charge attempts created when confirming the payment. | ||
Time
Attribute | Type | Example Value |
hours_since_customer_was_created | Numeric | 50 |
The number of hours since the Customer object making the payment was created on your account. | ||
hours_since_email_first_seen | Numeric | 50 |
The number of hours (up to five years) since the email address supplied with the payment first appeared on your account. This value includes payments from 2020 onward. | ||
hours_since_email_first_seen_on_stripe | Numeric | 50 |
The number of hours (up to five years) since the email address supplied with the payment first appeared on Stripe overall. This value includes payments from 2020 onward. | ||
minutes_since_customer_was_created | Numeric | 50 |
The number of minutes since the Customer object making the payment was created on your account. | ||
minutes_since_email_first_seen | Numeric | 50 |
The number of minutes (up to five years) since the email address supplied with the payment first appeared on your account. This value includes payments from 2020 onward. | ||
minutes_since_email_first_seen_on_stripe | Numeric | 50 |
The number of minutes (up to five years) since the email address supplied with the payment first appeared on Stripe overall. This value includes payments from 2020 onward. | ||
seconds_since_customer_was_created | Numeric | 50 |
The number of seconds since the Customer object making the payment was created on your account. | ||
seconds_since_email_first_seen | Numeric | 50 |
The number of seconds (up to five years) since the email address supplied with the payment first appeared on your account. This value includes payments from 2020 onward. | ||
seconds_since_email_first_seen_on_stripe | Numeric | 50 |
The number of seconds (up to five years) since the email address supplied with the payment first appeared on Stripe overall. This value includes payments from 2020 onward. | ||
Payment outcome counters
Attributes that track payment outcomes (authorized, blocked, declined, total) reflect two different data scopes:
- Charges-only: Attributes with
_include only card charge data.charges_ - Transactions: Attributes with
_include data for charges, ACH and SEPA direct debit payment attempts, and setup attempts.transactions_
Account rule attributes (Radar for Platforms only)
These attributes correspond to Connected accounts and allow you to take actions, such as submitting accounts for review.
Account risk levels
Attribute | Type | Example Value |
account_risk_level | Case Insensitive String | normal |
The risk level of a given account, as determined by Stripe. The supported values are: normal, elevated, and highest. An elevated account risk score means the account causes financial loss 50% of the time. A highest account risk score means the account causes financial loss 90% of the time. | ||
Disputes
Attribute | Type | Example Value |
dispute_count_for_account_monthly | Numeric | 10 |
The number of disputes that occurred within the past month on a connected account. Includes all dispute types (not just fraudulent) and statuses (won, lost, and so on). Disputes are determined by the date the dispute occurred, not the date of the underlying transaction. There can sometimes be more than one dispute on a single charge. | ||
dispute_count_for_account_weekly | Numeric | 10 |
The number of disputes that occurred within the past week on a connected account. Includes all dispute types (not just fraudulent) and statuses (won, lost, and so on). Disputes are determined by the date the dispute occurred, not the date of the underlying transaction. There can sometimes be more than one dispute on a single charge. | ||
dispute_count_for_account_daily | Numeric | 10 |
The number of disputes that occurred within the past day on a connected account. Includes all dispute types (not just fraudulent) and statuses (won, lost, and so on). Disputes are determined by the date the dispute occurred, not the date of the underlying transaction. There can sometimes be more than one dispute on a single charge. | ||
usd_amount_disputed_for_account_monthly | Numeric | 50 |
The charge volume (in USD) of disputes that occurred within the past month on a connected account. Includes all dispute types (not just fraudulent) and statuses (won, lost, and so on). Disputes are determined by the date the dispute occurred, not the date of the underlying transaction. There can sometimes be more than one dispute on a single charge. | ||
usd_amount_disputed_for_account_weekly | Numeric | 50 |
The charge volume (in USD) of disputes that occurred within the past week on a connected account. Includes all dispute types (not just fraudulent) and statuses (won, lost, and so on). Disputes are determined by the date the dispute occurred, not the date of the underlying transaction. There can sometimes be more than one dispute on a single charge. | ||
usd_amount_disputed_for_account_daily | Numeric | 50 |
The charge volume (in USD) of disputes that occurred within the past week on a connected account. Includes all dispute types (not just fraudulent) and statuses (won, lost, and so on). Disputes are determined by the date the dispute occurred, not the date of the underlying transaction. There can sometimes be more than one dispute on a single charge. | ||
dispute_rate_for_account_monthly | Percentage | 0.10 |
The percent of charges in the past month that resulted in a dispute. In this case, Stripe calculates the dispute on the date of the charge, not the date the dispute arrived. | ||
dispute_rate_for_account_weekly | Percentage | 0.10 |
The percent of charges in the past week that resulted in a dispute. In this case, Stripe calculates the dispute on the date of the charge, not the date the dispute arrived. | ||
dispute_rate_for_account_daily | Percentage | 0.10 |
The percent of charges in the past day that resulted in a dispute. In this case, Stripe calculates the dispute on the date of the charge, not the date the dispute arrived. | ||
Failures
Attribute | Type | Example Value |
failure_count_for_account_monthly | Numeric | 10 |
The number of failures which occurred within the past month on a connected account, including issuer blocked charges and Radar blocked charges, but excluding failed API calls. Failed API calls are included under the Failed category in the Transactions section of the Dashboard but aren’t considered indicative of fraud risk. | ||
failure_count_for_account_weekly | Numeric | 10 |
The number of failures which occurred within the past week on a connected account, including issuer blocked charges and Radar blocked charges, but excluding failed API calls. Failed API calls are included under the Failed category in the Transactions section of the Dashboard but aren’t considered indicative of fraud risk. | ||
failure_count_for_account_daily | Numeric | 10 |
The number of failures which occurred within the past day on a connected account, including issuer blocked charges and Radar blocked charges, but excluding failed API calls. Failed API calls are included under the Failed category in the Transactions section of the Dashboard but aren’t considered indicative of fraud risk. | ||
usd_amount_failed_for_account_monthly | Numeric | 50 |
The charge volume (in USD) of failures which occurred within the past month on a connected account, including issuer blocked charges and Radar blocked charges, but excluding failed API calls. Failed API calls are included under the Failed category in the Transactions section of the Dashboard but aren’t considered indicative of fraud risk. | ||
usd_amount_failed_for_account_weekly | Numeric | 50 |
The charge volume (in USD) of failures which occurred within the past week on a connected account, including issuer blocked charges and Radar blocked charges, but excluding failed API calls. Failed API calls are included under the Failed category in the Transactions section of the Dashboard, but aren’t considered indicative of fraud risk. | ||
usd_amount_failed_for_account_daily | Numeric | 50 |
The charge volume (in USD) of failures which occurred within the past day on a connected account, including issuer blocked charges and Radar blocked charges, but excluding failed API calls. Failed API calls are included under the Failed category in the Transactions section of the Dashboard but aren’t considered indicative of fraud risk. | ||
failure_rate_for_account_monthly | Percentage | 0.10 |
The percent of charges in the past month that resulted in a failure, including issuer blocked charges and Radar blocked charges, but excluding failed API calls. Failed API calls are included under the Failed category in the Transactions section of the Dashboard but aren’t considered indicative of fraud risk. | ||
failure_rate_for_account_weekly | Percentage | 0.10 |
The percent of charges in the past week that resulted in a failure, including issuer blocked charges and Radar blocked charges, but excluding failed API calls. Failed API calls are included under the Failed category in the Transactions section of the Dashboard but aren’t considered indicative of fraud risk. | ||
failure_rate_for_account_daily | Percentage | 0.10 |
The percent of charges in the past day that resulted in a failure, including issuer blocked charges and Radar blocked charges, but excluding failed API calls. Failed API calls are included under the Failed category in the Transactions section of the Dashboard but aren’t considered indicative of fraud risk. | ||
Refunds
Attribute | Type | Example Value |
refund_count_for_account_monthly | Numeric | 10 |
The number of refunds that occurred within the past month on a connected account. Refunds are calculated based on the date on which the refund occurred, not the date of the underlying transaction. A single charge can sometimes have more than one refund. | ||
refund_count_for_account_weekly | Numeric | 10 |
The number of refunds that occurred within the past week on a connected account. Refunds are calculated based on the date on which the refund occurred, not the date of the underlying transaction. A single charge can sometimes have more than one refund. | ||
refund_count_for_account_daily | Numeric | 10 |
The number of refunds that occurred within the past day on a connected account. Refunds are calculated based on the date on which the refund occurred, not the date of the underlying transaction. A single charge can sometimes have more than one refund. | ||
usd_amount_refunded_for_account_monthly | Numeric | 50 |
The charge volume (in USD) of refunds that occurred within the past day on a connected account. Refunds are calculated based on the date on which the refund occurred, not the date of the underlying transaction. A single charge can sometimes have more than one refund. | ||
usd_amount_refunded_for_account_weekly | Numeric | 50 |
The charge volume (in USD) of refunds that occurred within the past day on a connected account. Refunds are calculated based on the date on which the refund occurred, not the date of the underlying transaction. A single charge can sometimes have more than one refund. | ||
usd_amount_refunded_for_account_daily | Numeric | 50 |
The charge volume (in USD) of refunds that occurred within the past day on a connected account. Refunds are calculated based on the date on which the refund occurred, not the date of the underlying transaction. A single charge can sometimes have more than one refund. | ||
refund_rate_for_account_monthly | Percentage | 0.10 |
The percent of charges in the past month that resulted in a refund. In this case, the refund is calculated on the date of the charge, not the date the refund arrived. | ||
refund_rate_for_account_weekly | Percentage | 0.10 |
The percent of charges in the past week that resulted in a refund. In this case, the refund is calculated on the date of the charge, not the date the refund arrived. | ||
refund_rate_for_account_daily | Percentage | 0.10 |
The percent of charges in the past day that resulted in a refund. In this case, the refund is calculated on the date of the charge, not the date the refund arrived. | ||
Charges
Attribute | Type | Example Value |
charge_count_for_account_monthly | Numeric | 10 |
The count of successful charges that occurred within the past month on a connected account. | ||
charge_count_for_account_weekly | Numeric | 10 |
The count of successful charges that occurred within the past week on a connected account. | ||
charge_count_for_account_daily | Numeric | 10 |
The count of successful charges that occurred within the past day on a connected account. | ||
usd_amount_charged_for_account_monthly | Numeric | 50 |
The successfully processed charge volume (in USD) that occurred within the past month on a connected account. | ||
usd_amount_charged_for_account_weekly | Numeric | 50 |
The successfully processed charge volume (in USD) that occurred within the past week on a connected account. | ||
usd_amount_charged_for_account_daily | Numeric | 50 |
The successfully processed charge volume (in USD) that occurred within the past day on a connected account. | ||