Historical Data Upload

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.

This page describes the process for uploading historical data.

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>.json

Prerequisites

Before performing S3 operations, ensure you have:

1. Proper authentication as described in the Authentication section

2. AWS SDK or HTTP client configured with your credentials

3. Your client name and S3 bucket name confirmed with EagleSense support

Data Upload Operations

Historical Data for ML Tuning

Upload historical transaction data to improve the ML model accuracy. This data is used for model training and performance optimization.

Target Location: s3://{merchant_name}-merchant-eagle-sense/historical-data/

File Naming Convention: historical_data_<id>.{json|csv}

Supported Formats: JSON and CSV—Please confirm your preferred format with EagleSense support prior to integration.

Upload Process:

1. Ensure you have proper authentication as described in the Authentication section

2. Upload your historical data files directly to the historical-data directory

3. Use unique identifiers in filenames to prevent conflicts

4. Confirm successful upload completion

1. Payment Transaction Data:

ID	Data Type
user_id	String
card_id	String
merchant_transaction_id	String
transaction_timestamp	Timestamp
site_name	String
action_platform	String
subscription_id	String
package_id	String
ref_token	String
payment_method_type	String
transaction_amount	Float
decline_reason	String
acquirer_name	String
order_id	String
transaction_mid	String
transaction_type	String
order_type	String
transaction_descriptor	String
transaction_initiation	String
refund	Boolean
refund_reason	String
transaction_status	String
authorization_type	String
authorization_settle_time	String
merchant_category_code	Int
transaction_currency	String
transaction_currency_displayed	String
transaction_currency_charged	String
exchange_rate	Float
3ds_transaction	Boolean
hashed_ip_address_network	String
hashed_ip_address_host	String
ip_address	String
user_agent	String
device_fingerprint	String
device_language	String

2. Order Data:

ID	Data Type
package_id	String
product_description	String

3. Payment Card Data:

ID	Data Type
card_id	String
card_bin	String
bank_name	String
card_timestamp_added	Timestamp
bin_risk_level	Float
last4	String
card_expiration_timestamp	Timestamp
card_brand	String
card_level	String
card_type	String
cardholder_name	String
card_country	String
card_billing_address	String

4. Risk Events Data:

ID	Data Type
merchant_transaction_id	String
order_id	String
risk_event_timestamp	Timestamp
alert_type	String
alert_reason	String
aler_usd_cost	Float
alert_status	String
chargeback	Boolean
chargeback_timestamp	String
chargeback_reason	String
fraud	Boolean
fraud_prevention	Boolean
fraud_prevention_type	String
fraud_report_source	String

5. Multi profile Data:

ID	Data Type
multi_user_id	String
multi_user_ids	String
multi_card_ids	String
related_data	String
users_count	Int

6. User Profile Data:

ID	Data Type
user_id	String
user_age	Int
user_country	String
login_country	String
user_signup_timestamp	Timestamp
traffic_source	String
signup_method	String
multi_user_id	String
local_timestamp	Timestamp
local_timezone	String
user_status	String
user_last_log_timestamp	Timestamp
local_language	String
email_domain	String
hashed_username_email	String
email	String
phone_number	String
zip_code	String

7. User Activity Data:

ID	Data Type
user_id	String
merchant_transaction_id	String
user_action_time	String
user_engagement_time	Float
user_other_product_usage	String
user_first_session_timestamp	Timestamp
user_last_session_timestamp	Timestamp
user_sessions_count	Int

8. Subscription Data:

ID	Data Type
subscription_id	String
subscription_status	String
subscription_auto_renewal	Boolean
subscription_start_timestamp	Timestamp
subscription_end_timestamp	Timestamp
subscription_initial_price	Float
subscription_initial_period	Int
subscription_recurring_price	Float
subscription_recurring_period	Int
premium_subscription_status	String
premium_subscription_auto_renewal	Boolean
premium_subscription_start_timestamp	Timestamp
premium_subscription_end_timestamp	Timestamp

9. Other Merchant Specific Data:

ID	Data Type
payment_method_id	String
brand_id	String
buyer_timestamp_creation	Timestamp