Castle fraud detection review

Castle centers account protection around risk and filter requests. Its free and Pro allowances are denominated in API usage, and alternative IP lookup quantities use the same dollar credit.

Where it fits

Best fit for teams securing signup and login flows with API-led decisioning. Our rating weights practical decisions, account linkage, signal depth, implementation and commercial fit. A tenth of a point is a close judgment; use the full methodology and your own traffic before choosing.

Signals, output and workflow

In a proof of concept, request a sample response for a clean user and a suspicious user. Record which fields are available to engineering, risk and support, and whether the result directly supports the action your team needs.

Access and pricing

Free access: 1,000 Risk API calls / month, or equivalent IP usage. Public entry price: 200 US dollars / month including 40,000 Risk and Filter requests. Products in this comparison meter different units. Calculate the number of calls your actual flow will make, confirm included products and any overage, and get the latest terms from the vendor.

Strength and trade-off

Strength: Best fit for teams securing signup and login flows with API-led decisioning.

Trade-off: Price comparisons need the actual request mix; a Risk request and an IP lookup are different billing units.

What to verify in a test

1. Run the product on the same signup, login or payment cohort you use for other candidates.
2. Count known abuse caught, legitimate users flagged, missing responses and latency.
3. Compare the output to the operational action your team can take, then normalize the quote to that event volume.

Source

Vendor page ↗

FAQ

Visit Castle ↗