Creating a Helcim.js Configuration

All implementations of Helcim.js require a specific configuration to function properly. This setup lets you control your front-end payment security directly from your back-end dashboard. As a payments company, Helcim provides these settings so you can prevent fraud and protect your checkout experience.

Processing different transaction types

Helcim.js supports card processing types for card purchase, card preauth, and card verify. If your integration processes different payment types under different circumstances, you must build a unique Helcim.js configuration for each type. For example, you will need to create one configuration for a card purchase and a separate configuration for a card verification.

Create your configuration

Follow these steps to create your Helcim.js configuration and generate your Helcim.js token.

Log in to your Helcim account or developer test account
Click All Tools in the left menu
Select Integrations under the Merchant Tools section
Click Helcim.js Configurations from the inner menu
Click New Configuration in the top right-hand corner
Complete your custom settings using the fields described below
Click Save in the top right corner to create your configuration

📘 Token generation note

Once you click Save, the system automatically generates a new Helcim.js token and secret key under your security settings. Your integration uses these values to authenticate and validate your web transactions.

Configuration settings breakdown

Customize your integration by adjusting the fields within the three main dashboard sections.

General settings

These basic settings identify your configuration, where your checkout will be hosted, and control its active status.

Setting	Description
Active	Toggle this on to activate your Helcim.js configuration and allow processing.
Include XML on Response	This setting controls whether the Helcim.js response should include XML, along with the rest of the POST fields.
Name	Give your Helcim.js Configuration a Name for reference.
Website URLs	Enter the valid website URLs where you will be implementing Helcim.js for processing.

Transaction settings

These settings dictate how and where money flows through your checkout form.

Setting	Description
Currency	Select your processing currency. Your options depend directly on your physical location and the original setup of your merchant account.
Transaction type	Choose the specific transaction type for this checkout instance, such as card purchase or card verify.
Terminal	Choose your processing terminal. Most merchants utilize a single terminal. If you operate multiple accounts across different payments providers, choose the exact merchant terminal you want to use.
Test mode [Deprecated]	For older Helcim.js implementations you could toggle this switch on to test your front-end checkout safely. In newer Helcim.js implementations we recommend leaving test mode disabled and to reach out to our Support team to create a developer test account.

Security settings

Use these fields to deter bad actors from card-testing on your website.

Setting	Description
Enforce Hashing	Toggle this on for purchase transactions to require amount hashing. This ensures nobody can alter pricing in the browser layout.
Minimum Amount	Set a minimum transaction size to stop automated card-testing bots. This restriction is only valid for purchase and pre-authorization transaction types.
Maximum Amount	Establish a maximum payment threshold. Entering 0.00 removes all limits entirely.
Require Captcha	Toggle this switch to enable automated Google reCaptcha V3 protection on your payment forms.
Captcha Score Threshold	Set your minimum allowed security score. A score of 1.0 indicates a verified human visitor, while a score of 0.0 likely flags an automated bot. Stricter thresholds require a higher score.

⚠️ Security best practices

Combining Helcim.js with the Helcim API: To enhance the security of your Helcim.js implementation, we recommend combining Helcim.js to complete a card verify, with the Payment API to process purchase transactions. This allows you to secure your processing with a secondary API Access Configuration and token.