Greip - Fraud PreventionAbout this trigger
Triggers, queries, and actions are the building blocks of Applets. Triggers tell an Applet to start, queries ask a question, and actions are its end result.
Developer info
- Description
- This trigger fires when a new Fraudulent payment detected by Greip.
- API endpoint slug
- greip.fraud_payment
Trigger fields
No fields for this trigger
Ingredients
Created atDate and time event was created.
- Slug
- created_at
- Filter code
- Greip.fraudPayment.CreatedAt
- Type
- Date with time (ISO8601)
- Example
- 2020-07-08T04:17:06.000+05:00
Customer IDThe customer ID associated with the order.
- Slug
- customer_id
- Filter code
- Greip.fraudPayment.CustomerId
- Type
- String
- Example
- 10120
Rules detectedTotal rules detected in the order.
- Slug
- rules_detected
- Filter code
- Greip.fraudPayment.RulesDetected
- Type
- String
- Example
- 5
Customer emailThe customer email address associated with the fraudulent payment.
- Slug
- customer_email
- Filter code
- Greip.fraudPayment.CustomerEmail
- Type
- String
- Example
- name@domain.com
ScoreOrder risk score (0-100)
- Slug
- score
- Filter code
- Greip.fraudPayment.Score
- Type
- String
- Example
- 33.12
Rules checkedTotal rules checked against the order.
- Slug
- rules_checked
- Filter code
- Greip.fraudPayment.RulesChecked
- Type
- String
- Example
- 23