Batch Transaction Status Updates and Delayed Attributes
Overview
EagleSense provides S3 bucket access for uploading historical transaction data and batch processing operations. All S3 operations require proper authentication as described in the Authentication section. Access can be achieved through programmatic methods using AWS SDKs or, for certain operations like historical data uploads, through manual uploads if preferred.
Please note, in live EagleSense operation, it is crucial that we receive the status (e.g., declined, authorised) of all previous charge attempts — including CITs (even if they are not sent for scoring), MITs, Initials, and Rebills — for a given user and order before a new retry is submitted for scoring. This ensures we can recalculate aggregate features with full context prior to the next evaluation. You will use Batch Transaction Scoring method to send all processed transactions (CITs, MITs, initials, and rebills) with their statuses (e.g., declined, authorised), ensuring we receive complete transaction history and details regardless of whether a transaction requires scoring.
This guide explains how to send transaction status updates (e.g., declined, authorised) and delayed attributes such as refunds, chargebacks, and other post-transaction events.
If you prefer sending Batch Transaction Status Updates and Delayed Attributes in the same batch and through the same method as Batch Transaction Scoring, please confirm this with the EagleSense team and ensure that we receive the status (e.g., declined, authorised) of all previous charge attempts for a given user and order before a new retry is submitted for scoring.
S3 Bucket Structure
Your client-specific S3 bucket follows this naming convention: {merchant_name}-merchant-eagle-sense
{merchant_name}-merchant-eagle-sense/
├── historical-data/ # Upload historical transaction data for ML model training
│ └── historical_data_<id>.json
├── batch-request-data/ # Upload batch transaction data for evaluation
│ └── batch_<external_batch_id>.json
├── batch-result-data/ # Download batch evaluation results
│ └── batch_<external_batch_id>_<internal_subbatch_id>_result_<subbatch_index>_<total_number_of_subbatches>.json
└── update-data/ # Upload batch transaction attributes that became available later
└── update_<external_update_batch_id>.jsonPrerequisites
Before performing S3 operations, ensure you have:
Proper authentication as described in the Authentication section
AWS SDK or HTTP client configured with your credentials
Your client name and S3 bucket name confirmed with EagleSense support
Data Upload Operations
Transaction Status Updates and Delayed Attributes
Upload additional transaction attributes that became available later.
Target Location: s3://{merchant_name}-merchant-eagle-sense/update-data/update_<external_update_batch_id>.{json|csv}
Where external_update_batch_id can be set to any unique value.
Last updated