Kount 360 Integration Configuration Reference
This guide provides detailed instructions for configuring the Kount Fraud Evaluation Integration.
Prerequisites
Before configuring the integration, ensure you have:
EPCC Requirements
- Store Access: Active EPCC store with admin access in Commerce Manager
- API Credentials: Client credentials for OAuth authentication
Kount Requirements
- Kount 360 Account: Active account with API access enabled
- OAuth2 Credentials: API key for authentication
- Merchant Configuration: Configured merchant settings in Kount portal
- Environment Access: Production or sandbox environment credentials
Connection Configuration
Create a new Integration Instance
- In Commerce Manager, click on Composer in the left nav.
- Locate and click on the Kount Fraud Evaluation integration
- Click on Configure
- Details on how to configure each field are provided in the sections below.
- Click on Finish on the final configuration page to create your integration instance.
EPCC Connection
The EPCC connection uses OAuth2 client credentials flow.
Required Fields
| Field | Description | Example |
|---|---|---|
| Client ID | EPCC application client ID | your_epcc_client_id |
| Client Secret | EPCC application client secret | your_epcc_client_secret |
| Token URL | EPCC OAuth token endpoint | https://useast.api.elasticpath.com/oauth/access_token |
| Throttle Limit | API rate limit (requests per interval) | 3 |
| Throttle Interval | Rate limit interval in milliseconds | 125 |
| Keep Alive Flag | Enable connection keep-alive | true |
| Keep Alive Interval | Keep-alive interval in milliseconds | 10000 |
Token URL Options
- US East:
https://useast.api.elasticpath.com/oauth/access_token - EU West:
https://euwest.api.elasticpath.com/oauth/access_token
Configuration Steps
- Configure the Elastic Path Composable Commerce Connection:
- Enter your EPCC Client ID
- Enter your EPCC Client Secret
- Select the appropriate Token URL for your region
- Configure throttling settings
- Enable keep-alive settings for optimal performance
Kount Connection
The Kount connection uses OAuth2 with API key authentication.
Required Fields
| Field | Description | Example |
|---|---|---|
| API Key | Kount API key for authentication | your_kount_api_key |
| Token URL | Kount OAuth2 token endpoint | https://login.kount.com/oauth2/ausdppksgrbyM0abp357/v1/token |
| Base URL | Kount API base URL | https://api.kount.com/commerce |
| OAuth Scope | OAuth scope for API access | k1_integration_api |
| Retry Attempts | Maximum retry attempts for failed calls | 3 |
| Retry Delay | Initial retry delay in milliseconds | 1000 |
| Request Timeout | Request timeout in seconds (max 30) | 15 |
Environment URLs
Production:
- Token URL:
https://login.kount.com/oauth2/ausdppksgrbyM0abp357/v1/token - Base URL:
https://api.kount.com/commerce
Sandbox:
- Token URL:
https://login.kount.com/oauth2/ausdppkujzCPQuIrY357/v1/token - Base URL:
https://api-sandbox.kount.com/commerce
Configuration Steps
- Configure the Kount Connection:
- Enter your Kount API Key (obtained from Kount portal)
- Select the appropriate Token URL for your environment
- Select the corresponding Base URL
- Use default OAuth scope unless instructed otherwise by Kount
- Configure retry and timeout settings based on your performance requirements
Integration Settings
These settings control the behavior and security of the integration.
Webhook Security
| Setting | Description | Default | Notes |
|---|---|---|---|
| Webhook Secret Key | Secret key for EPCC webhook validation | Auto-generated UUID | Automatically generated if not provided |
Configuration: The webhook secret is auto-generated during deployment. You can provide a custom value if required by your security policies.
Logging Configuration
| Setting | Description | Options | Default |
|---|---|---|---|
| Log Level | Verbosity of integration logging | error, warn, info, debug, trace | error |
Usage Guidelines:
- Production: Use
errororwarnfor optimal performance - Development: Use
warnunless detailed troubleshooting is needed, then usedebug - Testing: Use
debugfor comprehensive request/response logging
Risk Evaluation Settings
| Setting | Description | Options | Default |
|---|---|---|---|
| Fallback Decision | Decision when Kount is unavailable | APPROVE, DECLINE, REVIEW | REVIEW |
| Enable Risk Inquiry | Enable immediate risk evaluation | true, false | true |
Fallback Decision Guidelines:
- APPROVE: Use for low-risk environments where service availability is critical
- DECLINE: Use for high-security environments where fraud prevention is paramount
- REVIEW: Recommended default for manual review workflows
Webhook Management
| Setting | Description | Options | Default |
|---|---|---|---|
| Cleanup Webhooks on Delete | Auto-remove EPCC webhooks when instance is deleted | true, false | true |
Business Configuration
These settings define the business rules and channel configuration for fraud evaluation.
Channel Configuration
| Setting | Description | Example | Default |
|---|---|---|---|
| Channel Identifier | Channel identifier sent to Kount when none specified. | WEB_CHECKOUT, MOBILE_APP, CALL_CENTER | WEB_CHECKOUT |
Fulfillment Configuration
| Setting | Description | Options | Default |
|---|---|---|---|
| Default Fulfillment Type | Fulfillment method when none specified | SHIPPED, DIGITAL, STORE_PICK_UP, LOCAL_DELIVERY, STORE_DRIVE_UP, IN_PERSON | SHIPPED |
| Default Shipping Provider | Shipping provider name used when none specified. | UPS, FedEx, USPS, FBM, Other | FedEx |
| Default Shipping Method | Shipping speed/method when none specified. | STANDARD, EXPRESS, SAME_DAY, NEXT_DAY, SECOND_DAY | STANDARD |
Configuration Guidelines:
- Fulfillment Type: Should match your primary fulfillment method
- Shipping Provider: Use the most common carrier for your orders
- Shipping Method: Default to your standard shipping option
Webhook Configuration
The integration automatically configures EPCC webhooks during deployment:
- Event:
order.fulfilled - URL: Dynamically generated by Integrations Hub
- Authentication: Uses configured webhook secret key
- Retry: No automatic retry. Webhooks can be redelivered using the Integrations Hub execution viewer.
Troubleshooting
Connection Problems
EPCC Connection Failures:
- Verify client ID and secret are correct
- Check token URL matches your EPCC region
- Ensure API credentials have required permissions
- Verify network connectivity to EPCC endpoints
Kount Connection Failures:
- Confirm API key is active in Kount portal
- Verify token URL matches your environment (production/sandbox)
- Check OAuth scope is correct
- Ensure Kount account has API access enabled
Webhook Issues
Webhook Not Receiving Events:
- Verify webhook secret matches configuration
- Check EPCC webhook configuration in Commerce Manager
- Review webhook delivery logs in EPCC
Authentication Failures:
- Confirm webhook secret key configuration
- Check
x-moltin-secret-keyheader in webhook requests - Verify webhook secret hasn't been modified
Support Resources
- Integration Logs: Available in the Integration Details section of Composer in Commerce Manager dashboard
- API Documentation: See API Reference
- Kount Documentation: See Kount 360 Integration Guide
- Kount API Reference: See Commerce APIs