Overview of HelcimPay.js

Embed payments into your website without handling sensitive information, using a single API call. With our prebuilt payment modal, HelcimPay.js enables you to easily accept payments and is the ideal solution for developers looking to implement a seamless payment experience while reducing their security and PCI-DSS compliance scope.

HelcimPay.js has access to Helcim Fee Saver, improved performance, and can be used by your customers to process credit card or ACH payments, or simply verify and tokenize card details to your Helcim Card Vault for later use through the Payment API.

How does HelcimPay.js work?

HelcimPay.js is a JavaScript based payment solution that uses a single API call to initialize a checkout session, then uses JavaScript to render the HelcimPay.js payment modal in an iFrame to allow your customers to make payment.

A successful initialization request to the HelcimPay.js Initialization endpoint will return a checkoutToken and secretToken to you.

🚧

Sending HelcimPay.js initialization requests

All requests to initialize a checkout session should be done from your website or applications secure back-end server, using your API Access token to authenticate your connection. This ensures a secure connection between your server and the Helcim system.

The checkoutToken is the key to the HelcimPay.js modal. This token ensures a secure connection between the cardholder’s web browser and Helcim’s endpoint. Please note, the checkout token is a unique value for each payment instance, and it expires after 60 minutes, or once the transaction is processed. Having unique and recent checkoutToken reduces the likelihood that an unauthorized payment is processed.

The HelcimPay.js modal can be easily implemented and rendered by adding a script tag to your web browser’s HTML code and passing the checkoutToken returned in your initialization request as a parameter to the function that renders HelcimPay.js.

📘

Integrating HelcimPay.js into Mobile Applications

Because HelcimPay.js uses JavaScript in order to render the payment modal on your website or application, it requires a browser to work. When integrating into mobile applications, your application must utilize a WebView wrapped in a native app.

The secretToken returned in your initialization request can be used for validation after a transaction has been processed successfully by your customer. This token, along with transaction data in the response are used to create a hash. You can use this hash to verify that the data in the transaction response is valid and has not been tampered with by comparing it to the hash returned by Helcim in the transaction response.

Testing your HelcimPay.js Integration

You should test your HelcimPay.js integration and card transaction flows without submitting real authorizations to the card networks, as this can have a negative impact on your processing terminal and account.

If you have an existing Helcim account, or you're looking to try potential solutions to see if we're a good fit, then we recommend getting set up with a developer test account.

Review our Developer Test Account documentation to learn more about how to set up a developer test account and what testing functionality is available.