Build a Cross-Border Payment Fraud Agent with Mastra AI and Arize Phoenix
Inspired by the 2026 MAS and Bank of Thailand MOU on cybersecurity and digital fraud protection, this challenge tasks you with building a high-trust payment monitoring agent. You will leverage the Mastra AI framework to orchestrate a sophisticated workflow that intercepts simulated cross-border transaction data, evaluates it against dynamic risk patterns (derived from MAS/ABS cyber resilience guidelines), and generates explainable risk evidence. To ensure regulatory compliance and transparency, you will integrate Arize Phoenix for real-time observability and trace-based evaluation of the agent's decision-making process. The system must handle asynchronous payment flows, manage persistent state for merchant risk profiles, and output structured reports suitable for human-in-the-loop (HITL) review by MAS compliance officers.
What you are building
The core problem, expected build, and operating context for this challenge.
Implement a Mastra AI-powered agentic workflow that utilizes Arize Phoenix to trace and evaluate fraud detection logic for cross-border transactions.
How work is evaluated
The challenge is evaluated on the agent's ability to correctly flag fraudulent transactions while maintaining a low false-positive rate and providing detailed traces in Arize Phoenix.
Shared data for this challenge
Review public datasets and any private uploads tied to your build.
How submissions are scored
These dimensions define what the evaluator checks and which criteria separate a passable run from a strong one.
Schema Validation
Ensures the output matches the required regulatory JSON schema.
This dimension contributes its full weight only when the submission satisfies the requirement. Partial credit is not awarded.
Trace Persistence
Verifies that traces were successfully exported to Arize Phoenix.
This dimension contributes its full weight only when the submission satisfies the requirement. Partial credit is not awarded.
F1 Score
Balance of precision and recall for fraud identification. • target: 0.85 • range: 0-1
This dimension contributes its full weight only when the submission satisfies the requirement. Partial credit is not awarded.
What you should walk away with
Master the Mastra AI workflow engine for stateful agent orchestration
Implement deep observability and tracing using Arize Phoenix
Design regulatory-compliant audit trails for AI-driven financial decisions
Integrate cross-border fraud detection heuristics into an LLM-based agent
Reference links and supporting material
Synthetic cross-border payment stream between Singapore and Thailand, containing 500 records with mixed labels (Normal, Fraud, Suspicious).
How this agent runs
The challenge is evaluated on the agent's ability to correctly flag fraudulent transactions while maintaining a low false-positive rate and providing detailed traces in Arize Phoenix.
Challenge input
JSON array of transaction objects containing amount, currency, sender_country, receiver_country, and merchant_id.
Mastra AI
Required for building the agentic workflow in TypeScript.
Arize Phoenix
Required for tracing and evaluating the agent logic.
Evaluated output
JSON object with boolean flags and evidence strings.
- Ensures the output matches the required regulatory JSON schema.
- Verifies that traces were successfully exported to Arize Phoenix.
- Balance of precision and recall for fraud identification. • target: 0.85 • range: 0-1
- Benchmark: FinReg-Eval-2026
- F1 Score target: 0.85
- 1 public reference case
- JavaScript execution harness
- Javascript sandbox
View technical recipe
Configured tools
- Mastra AI · Required
- SHAP (Explainability) · Optional
- Arize Phoenix · Optional
- Arize Phoenix · Optional
- Mastra AI · Required
Evaluation contract
- Schema Validation · Weight 1
- Trace Persistence · Weight 1
- F1 Score · Weight 1
Recipe state
This is a preview. The configuration can change before the evaluation recipe is locked.