Can I vibe code Accertify?

1. System Architecture & Overview:
Build a Node.js/TypeScript microservice for real-time ecommerce order risk scoring and manual review workflows. The system receives checkout order payloads via API, evaluates them against configurable risk rules, generates a composite risk score (0-100), and outputs a decision: APPROVE, REVIEW, or REJECT.

2. Data Model:
Create PostgreSQL schemas for:
- Orders: id, total_amount, currency, customer_id, ip_address, billing_address, shipping_address, payment_method, status (approved, held_for_review, rejected), risk_score, created_at.
- RiskRules: id, rule_name, condition_json, weight, action, active_status.
- RiskEvaluations: id, order_id, matched_rules (JSON array), aggregate_score, evaluation_timestamp.
- ReviewQueue: id, order_id, analyst_id, status (pending, approved, rejected), notes, resolved_at.

3. Core Rule Engine Functionality:
Implement a dynamic rule evaluation module supporting conditions like:
- Billing and shipping country mismatch (add +25 to score).
- High-velocity order placement (>3 orders from same IP within 10 minutes) (add +40 to score).
- Anonymous proxy / VPN IP detection using external lookup IP APIs (add +30 to score).
- Disposable email domain detection (add +20 to score).
- High order value (>3x store average order value) (add +15 to score).
Compute total risk score. If aggregate score > 75, reject order and trigger payment hold. If aggregate score is 45-75, place in ReviewQueue. If < 45, automatically approve.

4. Admin Review Dashboard API:
Build REST endpoints for internal risk analysts to:
- List pending orders in ReviewQueue sorted by risk score.
- Manually approve or reject held orders, transmitting status update webhooks to Shopify or custom store frontends.
- Add and update risk rules dynamically without restarting the application.

5. Failure Modes & Latency Limits:
- Synchronous risk score processing must complete in under 150ms.
- If third-party IP enrichment APIs timeout (200ms threshold), fallback to internal basic rules without failing the order.
- Log all evaluation failures for audit purposes.

6. Out of Scope:
Device fingerprinting browser SDKs, credit card tokenization, and card network chargeback representment filing.

$ each button prefixes agent-specific run instructions · build your own product, never copy proprietary code, trademarks or designs