Terms of Service
Last Updated: July 17, 2024
Welcome to the FDS (Fraud Detection SaaS) Scoring Engine. These Terms of Service ("Terms") govern your access to and use of our fraud detection API and dashboard.
1. Services Provided
The FDS Scoring Engine is a multi-tenant system featuring a Zero-Rule-Configuration architecture. Fraud evaluation and decision-making are entirely managed by our scoring engine. The service is designed to detect:
Each integration declares one of 17 closed fraud vector codes, grouped as:
- Payment & Money: carding fraud, promo/voucher abuse, BNPL fraud, chargeback abuse, seller/escrow fraud, money-mule activity, COD non-payment abuse, return/refund abuse, and loyalty-points fraud.
- Identity & Access: device-farm and emulator clusters, session hijacking, bot/registration farming, account takeover, content spam, referral fraud, password-reset abuse, and OTP brute-force.
2. Pricing & Billing
Usage is prepaid and billed per scored request in Indonesian Rupiah (IDR). Each request is priced by (a) whether its fraud vector is high-value (payment-adjacent) or low-value (identity/session), and (b) your project's trailing 30-day request volume tier:
| Tier | Trailing 30-Day Volume | Low-Value Rate | High-Value Rate |
|---|---|---|---|
| Bronze | 0 – 100,000 requests | Rp 25 | Rp 35 |
| Silver | > 100,000 requests | Rp 20 | Rp 30 |
| Gold | > 500,000 requests | Rp 15 | Rp 25 |
| Platinum | > 2,500,000 requests | Rp 10 | Rp 20 |
A low-value-declared request carrying clearly payment-shaped data (a card hash, voucher code, purchase amount, or disbursement account) is billed at the high-value rate regardless of its declared fraud vector. Every new project receives an automatic Rp 50,000 onboarding bonus credit. There is no subscription fee or fixed-term contract.
Current enforcement status: tier pricing, balance, and billing records are tracked and visible in the console today. Automatic balance deduction and hard cutoff at the scoring endpoint are not yet active; usage is metered and auditable, not yet self-enforcing.
3. System Resilience & Fail-Open Conditions
Our system is designed with high-resiliency (fail-open) principles. In the event of partial infrastructure disruptions (such as cache or graph analysis failures), API services will not be blocked.
Scoring Timeout Policy:
To ensure SLAs are met, the scoring evaluation enforces a strict 950ms timeout deadline. If the evaluation exceeds this time limit, the system will automatically provide a fallback response to prevent transaction blocking:
- Risk Score: 50
- Decision:
REVIEW(Manual review recommended) - Reason: "Scoring evaluation timed out. Manual review recommended."
4. Integration Security & Webhooks
All outgoing webhooks sent from our system to your backend will include an X-FDS-Signature header. This header contains the HMAC-SHA256 hash of the payload using your API Key, which you must validate to ensure data integrity and authenticity.