Payments integration · Updated November 15, 2026

Helcim integration

We connect Helcim to WordPress, Webflow, Astro or Next.js sites and custom software, from a hosted payment page to checkout inside your own forms. You take CAD or USD payments on interchange-plus pricing, and each one is recorded where your team works.

Rated 5.0 out of 5,72 Google reviews

Helcim at a glance

Connects
HelcimPay.js, Payment Pages, the Helcim API and webhooks to your site, CRM or database.
WordPress
Helcim for WooCommerce for one-time orders; Payment Pages or a custom plugin for the rest.
Webflow
A Payment Page link or Pay Now button; HelcimPay.js needs a small server function we host.
Astro or Next.js with Sanity
HelcimPay.js sessions, payment checks and webhooks in server routes; content in Sanity.
Custom software
Helcim's Payment and Recurring APIs, with webhooks for card transactions.
Complexity
Low to medium. HelcimPay.js and recurring billing need server code.
Typical setup
1 to 2 days for payment pages, 4 to 12 days for HelcimPay.js with recurring billing and webhooks.

How we connect Helcim

  • WordPress

    Helcim for WooCommerce is Helcim's own plugin. It runs checkout through HelcimPay.js, works with the block checkout and takes CAD or USD, but as of November 15, 2026 only for one-time payments. Recurring billing needs WP Gateways' third-party Gravity Forms add-on or a small plugin we write against the Recurring API.

  • Webflow

    There's no official Helcim app for Webflow. A Payment Page goes in as a link or Pay Now button, and the visitor pays on Helcim's page. HelcimPay.js can't run on Webflow alone: each checkout session starts from a server with your API token. We host a small function for that and the webhooks.

  • Astro or Next.js with Sanity

    An Astro server endpoint or Next.js route handler starts the HelcimPay.js session and passes the checkout token to the page, which opens the payment form in a modal. A second route checks the response hash with the secret token before marking anything paid. Content stays in Sanity, amounts and plans in Helcim.

  • Custom software

    We use the Payment API for purchases and pre-authorization captures, and the Recurring API for payment plans and subscriptions. Payment API calls need an idempotency key. The limit is 100 calls a minute and 3,000 an hour per account, so bulk jobs need pacing.

What organizations use Helcim for

  • Recurring billing and memberships

    The Recurring API sets up payment plans with trials, setup fees, add-ons and tax settings, and links customers to them. As of November 15, 2026, Helcim adds 0.4% to each recurring transaction. Its docs describe no automatic retry for a declined charge, so we build the reminder and retry step.

  • Invoices and payment pages for service businesses

    Payment Pages take fixed amounts, customer-entered amounts such as donations, or invoice payments, with your logo and colours. The webhook marks the invoice paid in your CRM or accounting system.

  • Bank payments for larger amounts

    Helcim takes Canadian EFT pre-authorized debit and US ACH as well as cards. The $6 fee cap suits tuition, rent and large invoices. A rejected or returned bank payment costs $5, so we hold access until it clears.

What to watch out for

  • Consent and privacy

    HelcimPay.js doesn't collect marketing consent. Under CASL your form needs its own unticked opt-in, stored with a date. Helcim's subprocessors include Helcim USA Inc. in the United States, and we found no public statement on where card data is hosted. Your privacy policy should allow for processing outside Canada, and Quebec's Law 25 calls for a privacy impact assessment before that transfer.

  • Tokens, PCI and webhooks

    The API token stays on the server; an initialize call from the browser fails. HelcimPay.js renders only on domains you whitelist in Helcim. Webhooks are signed with HMAC-SHA256 and checked with your verifier token. The card transaction event carries only an ID, so the handler fetches the full transaction.

  • Sync and timing

    Helcim retries a failed webhook at intervals from 5 seconds to 10 hours, so the handler must ignore repeats. Checkout tokens expire after 60 minutes. The hash check fails on accented characters, common in French names, unless you escape them the way Helcim does.

Sources

Checked against Helcim's docs on November 15, 2026.

  1. Helcim pricing Rates as of November 15, 2026.
  2. Overview of HelcimPay.js
  3. Initialize a HelcimPay.js checkout session Server-side call, 60-minute tokens, English or French.
  4. Validate a HelcimPay.js payment
  5. Recurring API
  6. Webhooks Signatures and retry schedule.
  7. API rate limits
  8. Idempotency
  9. What are Helcim Payment Pages
  10. Add a payment page to your website
  11. Helcim for WooCommerce Helcim's own plugin; one-time payments only.
  12. WP Gateways for Helcim Third-party Gravity Forms add-on.
  13. Helcim subprocessors (Canada)

Questions about Helcim

What does Helcim cost in Canada?

As of November 15, 2026, Helcim's keyed and online card rate is interchange plus 0.50% + 25¢ under $50K a month, stepping down to interchange plus 0.15% + 15¢ between $1M and $5M. There's no monthly fee. EFT and ACH payments cost 0.5% + 25¢, capped at $6.

Does Helcim's WooCommerce plugin handle subscriptions?

No. As of November 15, 2026, it takes one-time payments only, and Helcim lists subscriptions as planned. Recurring orders need a third-party add-on or a custom connection to the Recurring API.

Do we need a server to use Helcim?

Not for Payment Pages, which are a link or a button. HelcimPay.js does: each session starts from a server with your API token, and the server checks the payment response too. On Astro or Next.js that's a server route; on Webflow, a small function we host.

Can Helcim checkout be in French?

Yes. HelcimPay.js shows in English or French, set per session or picked up from the customer's browser. Your confirmation emails and receipts need their own French versions.

Can customers save a card for next time?

Yes. HelcimPay.js in verify mode saves the card or bank account to the customer in Helcim's vault as their default. Subscriptions and later charges use it, so card numbers never touch your site.

Related integrations

Taking payments with Helcim?

Tell us what you sell or collect and where the records should go. We'll say which Helcim setup fits and what it takes.

Book a call