Analyze synthetic payment transactions, detect card-testing and account-takeover patterns, calculate risk, and simulate an authorization decision.
Transaction Intelligence
Use a CSV/JSON transaction log or the built-in synthetic scenario.
No file selected
For this prototype, use synthetic transaction records only. Never upload card numbers, CVVs, PINs, passwords, or real banking credentials.
FRAUDGUARD USER MANUAL
Accepted Transaction Log Format
FraudGuard analyzes synthetic transaction logs in CSV or JSON format. Use the required fields below so the detection engine can evaluate transaction behavior.
01 · Supported files
.CSV.JSON
CSV is recommended for quick testing. JSON may contain an array directly or an object with a transactions array.
Never upload real payment information. Do not include card numbers, CVVs, PINs, passwords, bank credentials, or other sensitive financial data. Use synthetic/test records only.
06 · What happens after analysis?
0–24 LOW · Allow25–49 MEDIUM · Challenge50–74 HIGH · Hold75–100 CRITICAL · Block
These are simulated decisions for the prototype. A real payment processor would enforce the final authorization decision.
0
TRANSACTIONS
0
DECLINED
0
DEVICES
0
COUNTRIES
Fraud Risk Assessment
0
/ 100
LOW RISK
No significant fraud indicators detected.
ALLOW TRANSACTION
Detection Signals
Investigation Timeline
Transaction Evidence
Identifiers are intentionally non-sensitive synthetic values.
Time
Transaction
User
Amount
Country
Device
Status
Prototype decision only. In a real payment system, the authorized merchant/payment processor would enforce the final authorization decision.