Garage Door OS Docs
Invoices & Payments

Helcim Payments

Alternative card processor with hosted checkout.
5 min read

Helcim Payments

Overview

Helcim is an alternative card processor for ServiceFlow businesses that prefer Helcim’s rates, HelcimPay.js hosted checkout, or existing Helcim merchant accounts. When Helcim is configured and saved, it becomes the active card processor for new customer checkouts—invoices, payment links, and the customer portal use HelcimPay.js instead of Stripe Checkout.
Stripe keys are retained when you switch to Helcim. ServiceFlow SaaS billing and Stripe Connect employee payouts (when enabled) still use Stripe independently of the customer-facing processor.

How to access

SurfacePath
Helcim configurationSettings → Payments → Helcim Configuration (/settings/payments?tab=helcim)
Payment settings (processor status)Settings → Payments (/settings/payments)
Payment linksSettings → Payments → Payment Links or Payments → Payment Links — uses active processor
Staff Helcim checkoutAvailable on invoice/payment flows when Helcim is active

What you can do today

  • Connect Helcim with API token and webhook verifier token
  • Run in test or live environment
  • Set currency and optional terminal ID for in-person Helcim terminals
  • Accept online card payments via HelcimPay.js in the customer portal
  • Generate payment links that route to Helcim checkout
  • Use staff-initiated Helcim checkout from the office app for in-office card entry
  • View webhook URL for Helcim Dashboard configuration

Prerequisites

Setup path: Settings → Payments → Helcim Configuration (/settings/payments?tab=helcim)
Before Helcim checkout works:
  1. An active Helcim merchant account with API access
  2. API Token from Helcim Dashboard → Integrations → API Access
  3. Webhook Verifier Token from Helcim webhook settings (recommended for reliable payment status updates)
  4. Webhook endpoint registered in Helcim pointing at the URL shown in ServiceFlow (your API /api/payments/webhook path)
  5. If you need employee payouts, configure Stripe Connect separately — Helcim does not replace Connect

Step-by-step

1. Gather Helcim credentials

  1. Sign in to the Helcim Dashboard.
  2. Go to Integrations → API Access and copy your API Token.
  3. Under Webhooks, create or open a webhook and copy the Verifier Token.

2. Configure Helcim in ServiceFlow

  1. Go to Settings → Payments → Helcim Configuration.
  2. Paste the API Token (required on first setup; leave blank on later saves to keep the existing token).
  3. Paste the Webhook Verifier Token (recommended).
  4. Select Currency (default USD), Environment (Test or Live), and optional Terminal ID.
  5. Click Save. A success message confirms Helcim is now your active card processor.

3. Register the webhook in Helcim

  1. Copy the Webhook URL displayed in the Helcim configuration panel.
  2. In Helcim Dashboard → Webhooks, add that URL and the verifier token.
  3. Send a test event if Helcim supports it, then run a small test payment in ServiceFlow.

4. Verify customer checkout

  1. Open a test invoice with a balance due.
  2. Send a payment link or open pay flow in the customer portal.
  3. Confirm HelcimPay.js loads and payment completes; invoice balance should update after webhook processing.

5. Switch back to Stripe (if needed)

  1. Go to Settings → Payments → Stripe Configuration.
  2. Save valid Stripe keys. Connecting Stripe as the active processor switches new checkouts back to Stripe; Helcim credentials remain stored.

Current limitations

  • Affirm financing is not available with Helcim — Affirm requires Stripe as the active processor
  • ACH via Stripe Financial Connections is not used when Helcim is active; Helcim checkout is card-focused
  • Stripe Terminal settings apply only when Stripe is the active processor
  • One active card processor at a time for customer-facing flows
  • Refund and dispute workflows follow Helcim’s portal and timelines

Roadmap

  • Expanded Helcim payment method support as HelcimPay.js capabilities grow
  • Deeper reconciliation reporting between Helcim settlements and ServiceFlow invoices
  • Optional hybrid flows (not planned for v1 — processor remains either/or for checkout)

Related features