> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.mangopay.com/sdks/profiler/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.mangopay.com/_mcp/server.

# Profiler SDK

## Docs

- [Profiler - Web](https://docs.mangopay.com/sdks/profiler/web.md): How to integrate the fraud prevention profiler on web.
- [Profiler - iOS](https://docs.mangopay.com/sdks/profiler/ios.md): How to integrate the fraud prevention profiler on iOS.
- [Profiler - Android](https://docs.mangopay.com/sdks/profiler/android.md): How to integrate the fraud prevention profiler on Android.


> **Note:** This page contains both a page directory (above) and the landing page content (below). The page directory is generated for agent use and does not appear on the landing page.

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.mangopay.com/sdks/profiler/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.mangopay.com/_mcp/server.

# Profiler overview

The fraud prevention profiler is code implemented into the platform’s app or website which monitors browser and behavioral data during a user’s profiling session. The profiling session runs on your payment page, and the profiler enables you to monitor a vast array of data

signals

which can be used when defining rules.

Each profiling session has a unique identifier called the `attempt_reference`. The data from the profiling session is used to generate a fraud prevention recommendation for the user's action. The attempt reference is linked to the transaction request by being sent in the relevant API call in the `ProfilingAttemptReference` parameter.

### Benefits

Integrating the profiler – whether directly in your website or app, or via the [Checkout SDK](/sdks/checkout) – enables:

<table>
  <tbody>
    <tr>
      <th class="header">
        Profiler-based rules
      </th>

      <td class="table-content">
        Create rules based on the user’s interactions and traits of their browsing session, allowing you to detect bots, VPN usage, and other potentially suspicious behavior.
      </td>
    </tr>

    <tr>
      <th class="header">
        Enhanced data
      </th>

      <td class="table-content">
        Integrate data from the profiler into velocity rules to increase accuracy and precision – such as number of distinct users with the same IP address, or various system fingerprints.
      </td>
    </tr>
  </tbody>
</table>

For more information on Mangopay's fraud prevention solution:

#### [Guide](/guides/fraud-prevention)

Learn about Mangopay's fraud prevention capabilities

## Integration

Integration of the profiling solution comprises two parts:

1. Integrate the profiler on your website or app
2. Send the attempt reference in your pay-in requests to the Mangopay API

> **Note**
>
> **Note – Checkout SDK has the profiler built in**
>
> As well as powering your payment page, Mangopay’s [Checkout SDK](/sdks/checkout) has the profiler built in to simplify your integration.
>
> It generates and returns the attempt reference automatically before triggering the pay-in call.

### 1. Integrate the profiler

Follow our step-by-step guides to integrate the profiler on your website and app:

#### [How to](/sdks/profiler/web)

Profiler SDK - Web

#### [How to](/sdks/profiler/ios)

Profiler SDK - iOS

#### [How to](/sdks/profiler/android)

Profiler SDK - Android

### 2. Send the attempt reference to the API

You need to send the profiling attempt reference in the request to the Mangopay API from your backend.

The `ProfilingAttemptReference` parameter can be sent on the following endpoints:

* [Create a Direct Card PayIn](/api-reference/direct-card-payins/create-direct-card-payin)
* [Create a Web Card PayIn](/api-reference/web-card-payins/create-web-card-payin)
* [Create a Recurring PayIn Registration](/api-reference/recurring-payin-registrations/create-recurring-payin-registration)
* [Create a Preauthorization](/api-reference/preauthorizations/create-preauthorization)
* [Create an Extended Preauthorization](/api-reference/extended-preauthorizations/create-card-extended-preauthorization)
* [Create a Direct Bank Wire PayIn](/api-reference/bank-wire-payins/create-bank-wire-payin)
* [Create a Web Direct-Debit PayIn](/api-reference/web-direct-debit-payins/create-web-direct-debit-payin)
* [Create a Direct Debit PayIn](/api-reference/direct-debit-payins/create-direct-debit-payin)
* [Create an Apple Pay PayIn](/api-reference/apple-pay/create-apple-pay-payin)
* [Create a BLIK PayIn](/api-reference/blik/create-blik-payin-with-code)
* [Create a Giropay PayIn](/api-reference/giropay/create-giropay-payin)
* [Create a Google Pay PayIn](/api-reference/google-pay/create-google-pay-payin)
* [Create an iDEAL PayIn](/api-reference/ideal/create-ideal-payin)
* [Create a Klarna PayIn](/api-reference/klarna/create-klarna-payin)
* [Create an MB WAY PayIn](/api-reference/mb-way/create-mb-way-payin)
* [Create a Multibanco PayIn](/api-reference/multibanco/create-multibanco-payin)
* [Create a PayPal PayIn](/api-reference/paypal/create-paypal-payin)
* [Create a Satispay PayIn](/api-reference/satispay/create-satispay-payin)

## Related resources

#### [Guide](/sdks/checkout)

Learn how the Checkout SDK works