Adding a Kount connection to your BR-DGE retail channel requires you to collect some information for us to add to your BR-DGE retail channels. This article details the information BR-DGE requires, and how you can locate it.
Kount Account
If you don't already have a Kount Account, you must contact their Support Team.
BR-DGE requires the following information to allow you to route payments to Kount through our platform:
- Site Id
- Merchant Id
- API Key
Please note that some of these details are sensitive. We ask you to handle these with care.
- How to locate your Site Id?
- Log in to the Kount Test Portal.
- Under the Fraud Control list, click the Website option.
- In the Add Website pop-up window, enter a Website ID, which is any unique identifier for the website. The Website ID is used while configuring the plugin.
- If desired, add a description for the website.
- With the Kount Plugin installed successfully, Event Notification Service information displays. Under ENS Enabled, select No and leave the Merchant ENS URL empty.
- Click Add Website.
- How to locate your Merchant Id?
- A Sandbox Boarding Information document is sent following the initial kick-off call. It contains the Merchant ID and URLs associated with the Data Collector (DC) and Risk Inquiry Service (RIS) processes.
- A separate document for Production will be sent with the production service URLs once the test transactions are certified.
- How to create your API key?
- Log into the Agent Web Console.
- Click Admin, and then select API Keys.
- Click Create API Key.
- Enter a Key Name, select your desired Key Permissions (typically RIS and API), and then click Create API Key.
- If the key is successfully created, a confirmation appears.
- The new key displays on the API Key Management screen.
Proceed on Failure
If we are unable to contact Kount, you can choose whether the payment should proceed (true) or be rejected (false). Please confirm your preference.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article