# Use Radar with Connect

Learn how to use Stripe Radar to identify financial risk on connected accounts and connected account charges.

*Stripe Radar* (Stripe Radar helps detect and block fraud for any type of business using machine learning that trains on data across millions of global companies. It’s built into Stripe and requires no additional setup to get started) uses its AI model to identify financially risky payments and accounts in real time. When you use Radar with connected accounts, it checks only external charges. It doesn’t check fund transfers between Stripe accounts.

[Charges in a Connect integration](https://docs.stripe.com/connect/charges.md#types) fall into two categories:

- **Direct charges**: Paid directly to a connected account; Stripe applies only the collecting account’s Radar configuration and rules
- **Transferred charges** (for example, destination charges or separate charges and transfers): Paid to the platform account and transferred to a connected account; Stripe applies only the platform account’s Radar configuration and rules

You can [manage connected account](https://docs.stripe.com/radar/account-fraud-prevention.md) and transaction fraud with Radar. To detect financial risk in real time, apply our default rules or define your own [custom rules](https://docs.stripe.com/radar/rules.md). Your rules can include [attributes](https://docs.stripe.com/radar/rules/supported-attributes.md) for direct and transferred charge types and for connected accounts.

If your platform pays the fees for your connected accounts, you can choose whether your connected accounts use Radar Lite instead of their own [Radar tiers](https://docs.stripe.com/radar/how-radar-works.md#compare-plans). Learn how to [enable Radar Lite for your connected accounts](https://docs.stripe.com/radar/risk-settings.md#apply-radar-rules-to-direct-charges) when using direct charges.

## Radar fees

Stripe charges Radar account fees to the platform always, and Radar transaction fees based on the rate for the account that collected the payment. For payments collected by the platform account and transferred to a connected account, you can pass Radar fees to the connected account by reducing the transferred amount.

## Radar configuration for a connected account

The Dashboard you use to configure Radar transaction risk protection for a connected account depends on the connected account type. The following table shows which Dashboard to use for each account type.

| Dashboard access of the connected account | Connected account Dashboard | Platform account Dashboard Connect page |
| --- | --- | --- |
| Connected accounts with access to the Stripe Dashboard | ✓ Supported | ❌ Unsupported |
| Connected accounts with access to the Express Dashboard | ❌ Unsupported | ✓ Supported |
| Connected accounts with no dashboard access | ❌ Unsupported | ✓ Supported |

## Radar behavior

Radar transaction risk behavior for connected account payments depends on the charge category and connected account type. The following table describes each scenario.

| Charge type | Radar config rules used | Charges visible in connected account Dashboard | Charges visible in platform account Dashboard Connect page |
| --- | --- | --- | --- |
| Direct for connected accounts with access to the Stripe Dashboard | Connected account | ✓ Supported | ❌ Unsupported |
| Direct for connected accounts with access to the Express Dashboard | Connected account | ✓ Supported | ✓ Supported |
| Direct for connected accounts with no dashboard access | Connected account | ❌ Unsupported | ✓ Supported |
| Transferred from platform account | Platform account | ❌ Unsupported | ✓ Supported |

## See also

- [Choose your connected account type](https://docs.stripe.com/connect/accounts.md)
- [Radar documentation](https://docs.stripe.com/radar.md)