Helcim.js requires a secondary Helcim.js Configuration to be created in order to work, in addition to the API Access Configuration for standard Helcim API authentication.
This allows you to control your Helcim.js settings in the back-end (through your Helcim accounts Integrations section), removing the ability for the end-user to alter your desired settings. You can set a transaction size minimum, to deter card-testing on your checkout page, enable amount hashing, and determine whether the configuration is set to test-mode or production.
- Click on
- Click on
Helcim.js Configurationsto get started.
- Click on
New Configurationin the top right-hand corner to get started.
You can now work through the different fields to customize your Helcim.js settings.
- Toggle your Helcim.js configuration to Active.
- If you toggle this off, your Helcim.js configuration will no longer process transactions.
- Toggle Include XML on Response on.
- This setting controls whether the Helcim.js response should include a XML on the response (along with the rest of the POST fields). This is needed for some plugin configurations.
- Give your Helcim.js Configuration a Name for reference.
- Toggle Test Mode on if you would like transactions passed through this Helcim.js config to be in test-mode, or leave this off for live transactions.
Developer Test Accounts:
If you have a Helcim developer test account, then your Helcim.js config does not need to be in Test Mode as your processing terminal controls the test status of transactions processed through your integration.
We recommend a developer test account when integrating with the Helcim API and more information on test accounts can be found here.
- Select the Currency for your configuration. The available currency for your config will be based on the location and currency available for your Helcim merchant account.
- Select the Transaction Type for your configuration. While Helcim.js can be used to process direct Purchase transactions, for additional security we recommend selecting Card Verify (Tokenize Only) and combining Helcim.js with a call to the Card Purchase API endpoint using the
cardTokenreturned in the Card Verify transaction response. This requires you to also create an API Access Configuration.
- Select your processing Terminal that should be used for transactions. Most Helcim merchants will only have one processing terminal, however merchants with multiple Helcim merchant accounts should select processing terminal for the account they would like to process through.
Review our documentation on SSL and Security for Helcim.js.
- Toggle on Enforce Hashing to determine with amount hashing is required for transactions. Please review our Amount Hashing page for more information on hashing with Helcim.js.
- Set a Minimum Amount to determine the minimum transaction amount that can be processed through your Helcim.js configuration. Setting a minimum amount helps to prevent card testing on your website or checkout page.
- Set a Maximum Amount to determine the to maximum transaction amount that can be processed through your Helcim.js configuration. By default your maximum amount will be set to 0.00 which is no limit.
- Toggle Require Captcha on for your Helcim.js configuration. With this option toggled on it will enable ReCaptcha v3. Additional code will need to be added for Captcha to work correctly and instructions to produce the code using the Code Generator can be found here.
- Set the Captcha Score Threshold for your Helcim.js configuration. This is the minimum captcha score a transaction must pass before the transaction is allowed to process., where a score of 1.0 is likely a very good transaction and a score of 0.0 is very likely a bot. The higher the score, the stricter the threshold.
Saveto create the new configuration.
After you click
Save a new configuration token will be generated under the Security Settings section. Scroll down to copy and paste the token as part of your Helcim.js HTML implmentation.
Updated 3 days ago