---
title: Configuring an adapter instance
description: Configure the iovation IdP Adapter to determine how PingFederate communicates with the iovation API.
component: iovation
page_id: iovation:setup:pf_iovation_ik_configuring_an_adapter_instance
canonical_url: https://docs.pingidentity.com/integrations/iovation/setup/pf_iovation_ik_configuring_an_adapter_instance.html
revdate: May 30, 2025
section_ids:
  steps: Steps
---

# Configuring an adapter instance

Configure the iovation IdP Adapter to determine how PingFederate communicates with the iovation API.

## Steps

1. Sign on to the PingFederate administrative console.

2. Go to **Authentication > IdP Adapters** and click **Create New Instance**.

3. On the **Type** tab, set the basic adapter instance attributes:

   1. In the **Instance Name** field, enter a name for the adapter instance.

   2. In the **Instance ID** field, enter a unique identifier for the adapter instance.

   3. In the **Type** list, select **iovation IdP Adapter**. Click **Next**.

4. (Optional) On the **IdP Adapter** tab, in the **Optional Transaction Insight Parameters** section, configure additional transaction data to send to iovation with the device profile.

   You can find an overview in [Transaction insight parameters](pf_iovation_ik_transaction_insight_parameters.html).

   1. Click **Add a new row to 'Transaction Insight Parameters'**.

   2. In the **Incoming Attribute Name** field, enter the name of an attribute from any authentication source that appears earlier in your PingFederate authentication policy than the iovation IdP Adapter.

   3. In the **iovation API Attribute Parameter** field, enter the transaction insight parameter, such as `billingCountry` or `eventId`.

   4. In the **Action** column, click **Update**.

   5. To map another transaction insight parameter, repeat steps a - d.

5. (Optional) On the **IdP Adapter** tab, in the **Optional iovation Attributes** section, configure additional attributes to include in the attribute contract from the iovation payload.

   |   |                                                                                            |
   | - | ------------------------------------------------------------------------------------------ |
   |   | The `transactionRiskResult`(`/result`) attribute is already included in the core contract. |

   1. Click **Add a new row to 'Optional iovation Attributes'**.

   2. In the **Local Attribute** field, enter a name of your choosing for an attribute.

   3. In the **iovation API Attribute Mapping** field, enter the JSON Pointer syntax for the value of the matching iovation attributes as shown in [JSON Pointer syntax reference](pf_iovation_ik_json_pointer_syntax_reference.html).

   4. In the **Action** column, click **Update**.

   5. To add more attributes, repeat steps a - d.

6. On the **IdP Adapter** tab, configure the adapter instance by referring to [iovation IdP Adapter settings reference](pf_iovation_ik_iovation_idp_adapter_settings_reference.html). Click **Next**.

7. On the **Actions** tab, test your connection to the iovation API. Resolve any issues that are reported, and then click **Next**.

8. On the **Extended Contract** tab, add any attributes that you included in the **Optional iovation Attributes** section of the **IdP Adapter** tab.

9. Complete the adapter configuration.

10. On the **Summary** tab, check that the configuration is correct. Click **Done**.