## Providing Additional Fraud Data to Radar

Stripe Radar enhances its fraud detection capabilities by leveraging comprehensive data. When you tokenize payment information directly with Stripe, critical device details are automatically captured, leading to more accurate fraud scores. However, if you handle card tokenization yourself, use a third-party tokenizer, or send raw credit card numbers from your servers, this automatic capture of device details is bypassed. This can result in less precise fraud scores, potentially allowing fraudulent charges to go through.

To address this, Stripe offers **Radar Sessions**. By utilizing Radar Sessions, you can capture essential fraud-related information without needing to tokenize payments directly on Stripe. A Radar Session essentially creates a snapshot of browser metadata and device details, which significantly improves Radar's predictive accuracy for your payments. This metadata includes crucial information such as IP address, browser type, screen or device specifications, and other device characteristics.

For a deeper understanding of how Radar utilizes this data, refer to the documentation on [Advanced Fraud Detection](/radar/advanced-fraud-detection).

**Note:** The most secure and recommended method for tokenizing payment information is through a preferred Stripe integration. These integrations manage the secure collection and tokenization of payment details automatically. When you use a preferred Stripe integration, Radar has visibility into your checkout flows and can leverage the additional data for superior fraud protection. If you are using a preferred Stripe integration, you do not need to use Radar Sessions.