1. Identity and Fraud Developer
  2. Kount 360
  3. Payments Fraud
Quick Links

Command to Payments Fraud SDK Migration

Migrate from Command to Payments Fraud on Kount 360 by implementing the Payments Fraud SDK. The Payments Fraud SDK closely matches the Command SDK, minimizing friction during migration.

Important: When you migrate to Payments Fraud using the Payments Fraud SDK, you are completing a minimum viable integration with Kount 360. To use all of the available features in Kount 360, such as Tags in the API response, you must complete a full API integration after migrating. For more information, go to the Payments Fraud v2.0 Integration Guide.

Note

If the customer currently uses Mode X with the SDK, the migration is handled as a Mode U process (PATCH /orders request in Payments Fraud) with a 302 BAD_MODE warning similar to the following example:

...
   ERROR_COUNT=1 Value: [X] WARNING_0=302 BAD_MODE Field: [MODE] Cause: [mode X is not supported in K360 and will function as mode U with no risk evaluation]
...

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:

  • Kount 360 Client ID (PaymentsFraud.ClientId): Your new ID provided in Kount 360. To learn more or locate your Client ID, review Find your Client ID.

  • Payments Fraud API key (PaymentsFraud.Api.Key): Your API key was provided during your organization creation. Refer to the Payments Fraud v2.0 Integration Guide for more information.

Version Information

Supported .NET Standard versions:

Required Kount .NET SDK version: The latest available version from Nuget.

Required Kount RIS Version: Now backwards compatible with all currently supported versions of the Risk Inquiry Service (RIS)

Note

The supported .NET versions are based on formal specifications from Microsoft.

Configuring the .NET SDK for Migration

To move traffic from Kount Command to Payments Fraud on Kount 360, you must make two changes to your integration.

  1. Update your implementation to use long (64-bit) for merchantId. Payments Fraud uses 15-digit client IDs, which exceed the limits of a 32-bit int. Continuing to use a 32-bit int might cause overflow or data loss.

  2. For your integration environment, add the following properties to your appsettings.json :

    Sandbox

    "Ris.EnableMigrationMode": "true",
"PaymentsFraud.ClientId": "<Your Payments Fraud Client ID>",
"PaymentsFraud.Auth.Url": " https://login-uat.equifax.com/as/token",
"PaymentsFraud.Api.Url": "https://api-sandbox.kount.com/commerce/ris",
"PaymentsFraud.Api.Key": "<Your Payments Fraud API Key>"

    Production

    "Ris.EnableMigrationMode": "true",
"PaymentsFraud.ClientId": "<Your Payments Fraud Client ID>",
"PaymentsFraud.Auth.Url": "https://login.equifax.com/as/token",
"PaymentsFraud.Api.Url": "https://api.kount.com/commerce/ris",
"PaymentsFraud.Api.Key": "<Your Payments Fraud API Key>"

Caution

Setting Ris.EnableMigrationMode to true redirects traffic from Command to Payments Fraud, only.

Migrating to Payments Fraud with the Java SDK

To migrate from Command to Payments Fraud in Kount 360 by using the Java SDK, you must update your implementation to use the new constructors that replaced the process of setting -D system properties. You must also update your code to use a long (64-bit) type for merchantId values to account for the 15-digit merchant IDs used in Payments Fraud.

This SDK allows for configuring Command (legacy) and Payments Fraud on Kount 360 side-by-side. After setup is complete, you can toggle between the two by changing the migration mode boolean. When you set migrationModeEnabled to true, all Risk Inquiry Service (RIS) traffic is routed to Payments Fraud.

Note

If migration mode is enabled but required configuration values are missing or invalid, the SDK might trigger a javax.naming.ConfigurationException.

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

  • Kount 360 Client ID (payments.fraud.client.id): Your new ID provided in Kount 360. To learn more or locate your Client ID, review Find your Client ID.

  • Payments Fraud API key (payments.fraud.api.key): Your API key was provided during your organization creation. Refer to the Payments Fraud v2.0 Integration Guide for more information.

Version Information

Supported Java version: 8+

Required Kount Java SDK JAR version: The latest available version from Maven.

Required Kount RIS Version: Now backwards compatible with all currently supported versions of the Risk Inquiry Service (RIS)

Constructors

The sandbox environment is used in the constructor examples. To integrate with the production environment, use the production URLs.

Reference the sandbox and production URLs to align with your current stage of integration.

Sandbox

Auth Server URL:

https://login-uat.equifax.com/as/token

API Service Host:

https://api-sandbox.kount.com

Production

Auth Server URL:

https://login.equifax.com/as/token

API Service Host:

https://api.kount.com/commerce/ris

File-based API key constructor (Sandbox)

new KountRisClient(
    new URL("https://risk.test.kount.net"), // URL endpoint
    new File("/path/to/apiKeyFile.key"), // API key file
    true, // migrationModeEnabled
    "yourPaymentsFraudApiKey", // Payments Fraud API key
    "yourPaymentsFraudClientId", // Payments Fraud Client ID
    "https://api-sandbox.kount.com/commerce/ris", // Payments Fraud API endpoint (RIS)
    "https://login-uat.equifax.com/as/token" // Payments Fraud Auth endpoint
);

String-based API key constructor (Sandbox)

new KountRisClient(
    new URL("https://risk.test.kount.net"), // URL endpoint
    "yourApiKeyString", // API key as a string
    true, // migrationModeEnabled
    "yourPaymentsFraudApiKey", // Payments Fraud API key
    "yourPaymentsFraudClientId", // Payments Fraud Client ID
    "https://api-sandbox.kount.com/commerce/ris", // Payments Fraud API endpoint (RIS)
    "https://login-uat.equifax.com/as/token" // Payments Fraud Auth endpoint
);

Connection pool constructor (Sandbox)

new KountRisClient(
    "sandbox", // environment
    10, // connectionPoolThreads
    5, // connectionPerRoute
    true, // migrationModeEnabled (route to Payments Fraud)
    "yourPaymentsFraudApiKey", // Payments Fraud API key
    "yourPaymentsFraudClientId", // Payments Fraud Client ID
    "https://api-sandbox.kount.com/commerce/ris", // Payments Fraud API endpoint (RIS)
    "https://login-uat.equifax.com/as/token" // Payments Fraud Auth endpoint
);

Example SDK configuration

Replace <ORG_TOKEN_PATH> with the unique token path assigned to your organization. The /v1/token suffix must remain.

// Example configuration for migration to Payments Fraud in Kount 360
String env = "sandbox"; // or "production"
int connectionPoolThreads = 100;
int connectionPerRoute = 20;
boolean migrationModeEnabled = true;

String paymentsFraudClientId = "<YOUR_CLIENT_ID>";
String paymentsFraudApiKey = "<YOUR_API_KEY>";
String paymentsFraudAuthEndpoint = "https://login-uat.equifax.com/as/token";
String paymentsFraudApiEndpoint = "https://api-sandbox.kount.com/commerce/ris"; // or api.kount.com for prod

KountRisClient client = new KountRisClient(
    env,
    connectionPoolThreads,
    connectionPerRoute,
    migrationModeEnabled,
    paymentsFraudApiKey,
    paymentsFraudClientId,
    paymentsFraudApiEndpoint,
    paymentsFraudAuthEndpoint
);

Parameter reference

Parameter

Description

env

Environment: "sandbox" or "production".

connectionPoolThreads

Number of threads available to the HTTP client.

connectionPerRoute

Maximum concurrent connections per route.

migrationModeEnabled

When true, directs RIS traffic to Payments Fraud instead of Command.

paymentsFraudApiKey

Your Payments Fraud API key.

paymentsFraudClientId

Your Kount 360 client ID.

paymentsFraudApiEndpoint

RIS endpoint URL (api-sandbox.kount.com or api.kount.com).

paymentsFraudAuthEndpoint

OAuth2 token endpoint for your organization.

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:

  • Kount 360 Client ID (PF_CLIENT_ID): Your new ID provided in Kount 360. To learn more or locate your Client ID, review Find your Client ID.

  • Payments Fraud API key (PF_API_KEY): Your API key was provided during your organization creation. Refer to the Payments Fraud v2.0 Integration Guide for more information.

Version Information

Supported PHP Version: 8.2.0+

Required Kount PHP SDK Version: The latest available version from Packagist.

Required Kount RIS Version: Now backwards compatible with all currently supported versions of the Risk Inquiry Service (RIS)

Configure the PHP SDK for Migration

To move traffic from Kount Command to Payments Fraud on Kount 360, for your integration environment add the following to your app settings.ini :

Sandbox

[PAYMENTS_FRAUD]

MIGRATION_MODE_ENABLED = TRUE
PF_CLIENT_ID = <Your Payments Fraud client ID>
PF_AUTH_ENDPOINT = https://login-uat.equifax.com/as/token
PF_API_ENDPOINT = https://api-sandbox.kount.com/commerce/ris
PF_API_KEY = <Your Payments Fraud API key>

Production

[PAYMENTS_FRAUD]

MIGRATION_MODE_ENABLED = TRUE
PF_CLIENT_ID = <Your Payments Fraud client ID>
PF_AUTH_ENDPOINT = https://login.equifax.com/as/token
PF_API_ENDPOINT = https://api.kount.com/commerce/ris
PF_API_KEY = <Your Payments Fraud API key>

Caution

Setting MIGRATION_MODE_ENABLED to TRUE redirects data traffic from Command to Payments Fraud, only.

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:

  • Kount 360 Client ID (pf_client_id): Your new ID provided in Kount 360. To learn more or locate your Client ID, review Find your Client ID.

  • Payments Fraud API key (pf_api_key): Your API key was provided during your organization creation. Refer to the Payments Fraud v2.0 Integration Guide for more information.

Version Information

Supported Python version: Python 3+

Required Kount Python SDK version: The latest available version from PyPi.

Required Kount RIS Version: Now backwards compatible with all currently supported versions of the Risk Inquiry Service (RIS)

Configure the Python SDK for Migration

To move traffic from Kount Command to Payments Fraud on Kount 360, for your integration environment add the following properties in the client.py Client class:

Sandbox

migration_mode_enabled = true
pf_client_id = <Your Payments Fraud client ID>
pf_auth_endpoint = https://login-uat.equifax.com/as/token
pf_api_endpoint = https://api-sandbox.kount.com/commerce/ris
pf_api_key = <Your Payments Fraud API key>

Production

migration_mode_enabled = true
pf_client_id = <Your Payments Fraud client ID>
pf_auth_endpoint = https://login.equifax.com/as/token
pf_api_endpoint = https://api.kount.com/commerce/ris
pf_api_key = <Your Payments Fraud API key>

Caution

Setting migration_mode_enabled to true overrides MERC with PF_CLIENT_ID and redirects data traffic from Command to Payments Fraud, only.

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:

  • Kount 360 Client ID (pf_client_id): Your new ID provided in Kount 360. To learn more or locate your Client ID, refer to Find your Client ID .

  • Payments Fraud API key (pf_api_key): Your API key was provided during your organization creation. Refer to the Payments Fraud v2.0 Integration Guide for more information.

Version Information

Supported Ruby version: 3.2.7+

Required Kount Ruby SDK version: The latest available version from RubyGems.

Required Kount RIS version: Now backwards compatible with all currently supported versions of the Risk Inquiry Service (RIS)

Configure the Ruby SDK for Migration

To move traffic from Kount Command to Payments Fraud on Kount 360, for your integration environment add the following properties in your app or web configuration file:

Sandbox

migration_mode_enabled=true
pf_client_id=<Your Payments Fraud Client ID>
pf_auth_endpoint=https://login-uat.equifax.com/as/token
pf_api_endpoint=https://api-sandbox.kount.com/commerce/ris
pf_api_key=<Your Payments Fraud Client ID>

Production

migration_mode_enabled=true
pf_client_id=<Your Payments Fraud Client ID>
pf_auth_endpoint=https://login.equifax.com/as/token
pf_api_endpoint=https://api.kount.com/commerce/ris
pf_api_key=<Your Payments Fraud Client ID>

Caution

Setting migration_mode_enabled to true redirects data traffic from Command to Payments Fraud, only.

Was this article helpful?
1 out of 5 found this helpful
Payments Fraud
Payments Fraud v2.0 Integration Guide
Command to Payments Fraud SDK Migration
Payments Fraud v1.0 Integration Guide
Risk Inquiry Service to Orders API Comparison
Assign or Update the Reason Code for an Order via API