Command to Payments Fraud SDK Migration

March 27, 2025 09:05

You can migrate from the Command Risk Inquiry Service SDKs to the Payments Fraud SDK with minimal technical effort. We created a process that requires flipping a flag by adding properties to your configuration settings. The properties vary depending on which SDK you use. By adding these properties, you are updating your current SDK to stop sending data to Command and to start sending data to Payments Fraud.

The Payments Fraud SDK has been built to closely match the Command SDK to reduce friction during migration.

Migrating to Payments Fraud with the .NET SDK

Before migrating from Command to Payments Fraud in Kount 360 using the .NET SDK, you must have the following:

Merchant ID (Ris.MerchantId)

Provided by your Kount representative during integration.
Client ID (PaymentsFraud.ClientId)

In Kount 360, go to Admin > Product Configuration > System Settings to find the Client ID associated with your API key. You must be the organization owner to find this information in Kount 360.
Command API key (Ris.API.Key)

In the Agent Web Console, go to Admin > API Keys to find your API key.
Payments Fraud API key (PaymentsFraud.Api.Key)

Your API key should have been saved to a secure location during your organization creation. Refer to the Payments Fraud v2.0 Integration Guide for more information.
.NET SDK version 9.0.1 or newer

Setting the .NET SDK for Migration

In your app or web configuration settings, in the appsettings.json section, add the following properties:

 "Ris.EnableMigrationMode": "true",
    "PaymentsFraud.ClientId": "CLIENT_ID",
    "PaymentsFraud.Auth.Url": "https://login.kount.com/oauth2/aus12zvb2vueTvA7F0h8/v1/token",
    "PaymentsFraud.Api.Url": "https://api.kount.com/commerce/ris",
    "PaymentsFraud.Api.Key": "API_KEY"

Setting Ris.EnableMigrationMode to true enables data traffic to flow to Payments Fraud. When this is active, data cannot flow to both products, only Payments Fraud.

Migrating to Payments Fraud with the Java SDK

Before migrating from Command to Payments Fraud in Kount 360 using the Java SDK, you must have the following:

Client ID (payments.fraud.client.id)

In Kount 360, go to Admin > Product Configuration > System Settings to find the Client ID associated with your API key. You must be the organization owner to find this information in Kount 360.
Payments Fraud API key (payments.fraud.api.key)

Your API key should have been saved to a secure location during your organization creation. Refer to the Payments Fraud v2.0 Integration Guide for more information.
Payments Fraud API endpoint (payments.fraud.api.endpoint)
Payments Fraud authentication endpoint (payments.fraud.auth.endpoint)
Kount JAR version 8.0.0 or newer
Java SDK 17 or newer

Setting the Java SDK for Migration

In your app or web configuration file, add the following properties:

migration.mode.enabled
payments.fraud.api.key
payments.fraud.api.endpoint
payments.fraud.auth.endpoint
payments.fraud.client.id

The configuration is similar to how the kount.config.key setting is currently used in the existing Command Java SDK.

Setting migration.mode to enabled allows data traffic to flow to Payments Fraud. When this is active, data cannot flow to both products, only Payments Fraud.

Note

KountRisClient might invoke javax.naming.ConfigurationException if migration mode is enabled but the properties are not present. In this instance, set the new values by passing flags or setting environment variables.

Migrating to Payments Fraud with the PHP SDK

Before migrating from Command to Payments Fraud in Kount 360 using the PHP SDK, you must have the following:

Client ID (PF_CLIENT_ID)

In Kount 360, go to Admin > Product Configuration > System Settings to find the Client ID associated with your API key. You must be the organization owner to find this information in Kount 360.
Payments Fraud API key (PF_API_KEY)

Your API key should have been saved to a secure location during your organization creation. Refer to the Payments Fraud v2.0 Integration Guide for more information.
Payments Fraud API endpoint (PF_API_ENDPOINT)
Payments Fraud authentication endpoint (PF_AUTH_ENDPOINT)
PHP language version 8.2.0 or newer
Kount PHP SDK package 8.0.0 or newer

Setting the PHP SDK for Migration

Add following code to the settings.ini package:

[PAYMENTS_FRAUD]
; Whether or not to enable Payments Fraud migration mode
MIGRATION_MODE_ENABLED=FALSE

; Payments Fraud client ID analagous to the Kount RIS merchant ID
PF_CLIENT_ID =

; Payments Fraud API key
PF_API_KEY =

; Payments Fraud API endpoint
PF_API_ENDPOINT = https://api.kount.com/commerce/ris

; Payments Fraud Auth endpoint
PF_AUTH_ENDPOINT = https://login.kount.com/oauth2/ausdppkujzCPQuIrY357/v1/tokenmigration_mode_enabled

Setting MIGRATION_MODE to ENABLED allows data traffic to flow to Payments Fraud. When this is active, data cannot flow to both products, only Payments Fraud.

Migrating to Payments Fraud with the Python SDK

Before migrating from Command to Payments Fraud in Kount 360 using the Python SDK, you must have the following:

Client ID (pf_client_id)

In Kount 360, go to Admin > Product Configuration > System Settings to find the Client ID associated with your API key. You must be the organization owner to find this information in Kount 360.
Payments Fraud API key (pf_api_key)

Your API key should have been saved to a secure location during your organization creation. Refer to the Payments Fraud v2.0 Integration Guide for more information.
Payments Fraud API endpoint (pf_api_endpoint)
Payments Fraud authentication endpoint (pf_auth_endpoint)
kount-ris-sdk 4.0.1 or newer

Note

Python 2 is not supported by this SDK.

Setting the Python SDK for Migration

In the client.py client class, add the following properties:

migration_mode_enabled
pf_client_id
pf_auth_endpoint
pf_api_endpoint
pf_api_key

Setting migration_mode to enabled allows data traffic to flow to Payments Fraud. When this is active, data cannot flow to both products, only Payments Fraud.

Note

Adding the properties to your client.py client class consolidates for all Risk Inquiry Service Modes and overrides merc with pf_client_id if migration_mode_enabled is set to true.

Migrating to Payments Fraud with the Ruby SDK

Before migrating from Command to Payments Fraud in Kount 360 using the Ruby SDK, you must have the following:

Client ID (pf_client_id)

In Kount 360, go to Admin > Product Configuration > System Settings to find the Client ID associated with your API key. You must be the organization owner to find this information in Kount 360.
Payments Fraud API key (pf_api_key)

Your API key should have been saved to a secure location during your organization creation. Refer to the Payments Fraud v2.0 Integration Guide for more information.
Payments Fraud API endpoint (pf_api_endpoint)
Payments Fraud authentication endpoint (pf_auth_endpoint)
Ruby SDK version 3.2.7 or newer
kount_complete 3.0.0 or newer

Setting the Ruby SDK for Migration

In your app or web configuration file, add the following properties:

migration_mode_enabled
pf_client_id
pf_auth_endpoint
pf_api_endpoint
pf_api_key

Setting migration.mode to enabled allows data traffic to flow to Payments Fraud. When this is active, data cannot flow to both products, only Payments Fraud.

Was this article helpful?

0 out of 0 found this helpful