Product Overview
What is EagleSense?
EagleSense offers a suite of tools, including first-party fraud prevention, acceptance rate optimization, and smart retries, all accessible via a simple API.
Key Benefits
Evaluate each transaction
Reduce fraud and minimize revenue loss
Take full control of the effects EagleSense has on your transaction flow, depending on your immediate business needs
Enhance Approval Rates for transactions and ensure compliance with the new VAMP regulations
Adhere to industry standards and benchmarks
How EagleSense Works
Our model is tailored to each client, continuously learning from their unique inputs while also drawing on industry trends, supplementary sources, and broader subscription insights.
Phase 1: Model Selection and Tuning
During this phase, we use historical data on transactions, user behaviour and profile descriptors. This data can be either provided to us in a batch format, or we can collect it over a period of time through a real-time integration with our API. [More on this in the Data Sharing section].
Please share any existing filters or anti-fraud logic you have in place. This is important for us to account for potential biases in the dataset and ensure the best possible model performance.
We will analyze your raw data, transform it into features, do test runs and then tune our models, taking into account your business characteristics and data structure.
We will then estimate the future effects on risk event ratios, revenue and costs, based on the past data.
Phase 2: Live Scoring Operation
Once the model is trained, it will be used for live transaction scoring. You can send your transaction data via S3 or integrate with our API, submitting transaction-specific requests to our system before they are executed. In response, we will return an assessment of the likelihood of risk or fraud for each transaction.
This process is similar to how you might integrate with a payment gateway.
You will be able to make adjustments to the tool’s reference metrics, transaction targeting and monitor performance through the comprehensive dashboard.
Things to note:
In live EagleSense operation, it is crucial that we receive the status of all previous charge attempts (CITs, MITs, initial transactions and rebills) for a given user and order through Batch Transaction Scoring method before a new retry is submitted for scoring. This ensures we can recalculate aggregate features with full context prior to the next evaluation.
We also require that completed CIT Initials (with all statuses) are provided via Batch Transaction Scoring method — even if they are not sent for scoring — before submitting a rebill for the same order or user. This helps maintain feature accuracy and supports proper model retraining across all transaction types, consistent with the structure of your historical dataset.
Last updated