Data Sharing
Overview of Historical Data Sharing
EagleSense requires data to function effectively. Including but not limited to transaction and alert data, product data, user profile and activity data.
This is how you can share your data with EagleSense for model refinement and transaction analysis purposes (Phase 1):
Connect to our S3 bucket and upload historical datapoints in batch format.
Historical Data Upload For authentication instructions, please refer to Authentication
Overview of Live integration for Batch Transaction Scoring
Once the solution is live, the Batch Transaction Scoring method enables you to send transaction data for immediate risk assessment. Each submitted transaction receives a risk score, allowing you to make informed decisions before processing. This integration is optimized for handling large transaction volumes efficiently. You will also use this method to send all processed transactions with their statuses (CITs, MITs, initials, and rebills), ensuring we receive complete transaction history and details regardless of whether a transaction requires scoring.
Overview of Transaction Updates and Delayed Attributes (Declined, Authorised, Refunds, Chargebacks, Post-Transaction Events)
This method allows you to submit post-transaction updates—such as status changes, refunds, chargebacks, or status changes—linked to the original transactions. These delayed attributes are used to score future transactions, enhance model accuracy, enrich historical context, and support ongoing performance monitoring.
Batch Transaction Status Updates and Delayed Attributes
Overview of Near Real-Time Transaction Scoring API
This method enables low-latency scoring of individual transactions and the submission of individual transaction updates.
Required Data Fields
We kindly ask you to include all applicable optional and required fields to ensure comprehensive data coverage. Providing as much detailed information as possible will enhance the accuracy and effectiveness of our analysis. If certain fields are not relevant, feel free to exclude them, but we encourage their inclusion whenever applicable.
Last updated