Skip to content
Suite 06 · Block fraud, not customers

Fraud & Risk Engine

Every transaction is scored in single-digit milliseconds against device intelligence, velocity rules and sanctions data — so you decline the fraud attempt and approve the good customer.

Capabilities

6 endpoints and counting

  • Risk Scoring
  • Velocity Rules
  • Device Intelligence
  • AML & Sanctions Monitoring
  • Chargeback Defence
  • Case Management
POST/v1/risk/evaluate
curl https://api.rupeeco.in/v1/risk/evaluate \
  -H "Authorization: Bearer $RUPEECO_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "amount": 1899000,
    "device_id": "dvc_7bd1a2",
    "email": "aarav@example.com",
    "ip": "203.0.113.42"
  }'
What makes it different

Designed around how this actually breaks

1

Sub-10ms decisions

Inline scoring on the authorisation path with a full feature vector returned for your own models.

2

Rules you can edit

Velocity, geo, BIN, device and amount rules changed from the dashboard, versioned and testable against replayed traffic.

3

AML built in

Continuous screening against sanctions and PEP watchlists with STR-ready case files.

Where teams use it

Common fraud & risk engine use cases

Every deployment starts with a call about your flows. Bring your edge cases — routing rules, approval chains, reconciliation formats — and we will map them before you write a line of code.

Discuss your use case
01

High-risk checkout protection

02

Onboarding fraud screening

03

Regulatory AML monitoring

Pairs well with

Same key, same dashboard, same webhook signature — add another suite without another integration.

Try first. Subscribe later.

Start with sandbox keys. Talk commercials when you are ready.

Test the full API surface before you sign anything. When you are ready to go live, we price on the volume you actually process.

1

Map your flows

A solutions engineer walks through your money-in, money-out and verification requirements and proposes the shortest path live.

2

Test in sandbox

Pull keys, replay real-world scenarios and validate webhooks against a sandbox that mirrors production behaviour.

3

Go live and scale

Switch to production keys, turn on routing rules, and add new suites from the marketplace whenever you need them.