The API Report CardAPI Index
THE API REPORT CARD / Financial Services / Helcim
Helcim

Helcim API

SMB payment processing / merchant services (Canada-headquartered, US + CA) · helcim.com

Helcim publishes a self-serve REST API covering payments, customers, invoicing, recurring billing, ACH, and terminal control under dashboard-issued tokens. Signup is free and instant with no sales contact. There are no first-party SDKs, and webhooks cover only two card-present event types.

Last verified: July 2026Financial Services
API GRADE
A
VERIFIED JUL 2026

SCORECARD

ExistenceGOODSelf-serve REST API at devdocs.helcim.com covering the full payments stack over JSON and HTTPS.
AccessGOODFree instant signup and dashboard-issued API tokens; no sales contact or partner gate anywhere.
CoverageGOODPayments, preauth and capture, customers, invoices, recurring plans, ACH, card batches, and terminal control.
AuthGOODDashboard-issued API tokens, server-side only; HelcimPay.js keeps card data out of your PCI scope.
Docs & DXGOODStrong docs with llms.txt and OpenAPI, but no first-party SDKs and webhooks fire for just two event types.
StabilityGOOD
MORE FROM THE REPORT CARD
StripeASumUpAAirbaseD+AnsaradaC
Supergood: Helcim shipped a real API. Most vendors don't; we ship near-native APIs for the rest.

Frequently asked questions

Helcim scores A on the API Report Card. Helcim publishes a self-serve REST API covering payments, customers, invoicing, recurring billing, ACH, and terminal control under dashboard-issued tokens. Signup is free and instant with no sales contact. There are no first-party SDKs, and webhooks cover only two card-present event types.

Tried to integrate with Helcim?
SOURCES
No first-party SDKs in any major language -- every integrator hand-rolls HTTP clients, which slows adoption vs. Stripe / Square devdocs.helcim.com ↗
Webhooks are scoped to card-present transaction events only (`cardTransaction`, `terminalCancel`) -- no native events for invoices paid, subscription renewed/failed, ACH cleared, refund issued, customer updated, or batch settled, forcing developers to poll for most lifecycle changes devdocs.helcim.com ↗
Webhook payloads contain only a transaction ID and event type -- every notification requires a follow-up GET against the Card Transaction API, doubling the request volume and adding latency devdocs.helcim.com ↗
One webhook endpoint per service and the endpoint URL is not allowed to contain the substring 'Helcim', which is an unusual and undocumented-rationale constraint devdocs.helcim.com ↗
Helcim has historically operated two API generations (legacy Helcim Commerce / XML API and the current REST devdocs.helcim.com surface); older partner integrations and third-party connectors are still on the legacy surface, which complicates migration and creates inconsistent docs in the wild devdocs.helcim.com ↗
Public docs do not specify rate limits, so capacity planning for bulk operations (backfills, mass refunds, end-of-month reconciliation) requires trial and error helcim.com ↗
Reported gaps between documented behavior and shipping behavior -- e.g. 'Other Tender' transaction list endpoint flagged as non-functional despite appearing in the public reference cardpaymentoptions.com ↗
No API versioning header / dated API versions -- breaking changes to the live API land for everyone simultaneously, with changelog discipline lower than Stripe's devdocs.helcim.com ↗
Only one linked bank account per merchant account propagates into the API -- there is no native concept of multiple settlement destinations, which blocks multi-entity / sub-merchant routing use cases cardpaymentoptions.com ↗
Smart Terminal / Payment Hardware API requires the merchant be on Helcim hardware, so any POS-bridge integration is locked to the Helcim hardware footprint devdocs.helcim.com ↗
Sudden holds on deposits and account-level transaction caps imposed without warning after volume spikes, with funds held for weeks while Helcim re-underwrites the merchant trustpilot.com ↗
Initial KYC / 'Know Your Customer' onboarding delays of 1-2+ weeks before first payout, with merchants reporting they only learned of additional documentation requirements after their first transaction trustpilot.com ↗
Effective rate discrepancies vs. signup quote -- multiple merchants report being quoted interchange-plus pricing then seeing effective rates of 3.5%+ once interchange and assessment line items land on the statement trustpilot.com ↗
Account terminations described as abrupt with limited stated rationale, common pattern for high-risk verticals (CBD, supplements, digital goods, subscriptions, certain professional services) cardpaymentoptions.com ↗
Only one bank account can be linked per Helcim account, which is a hard blocker for multi-entity, multi-location, or trust-account merchants (e.g. property managers, law firms) cardpaymentoptions.com ↗
UI error codes are cryptic and customer-support reps reportedly lack standardized SOPs for resolving KYC and risk flags, leading to inconsistent answers across tickets cardpaymentoptions.com ↗
Underwriting and risk decisions feel opaque -- merchants approved at signup get re-reviewed and shut off mid-relationship trustpilot.com ↗
Some sales-cycle feature promises (specific reporting, specific integrations, ACH limits) reportedly turn out buggy or non-functional in production cardpaymentoptions.com ↗
Mixed reviews on G2 reflect the typical processor pattern: love it when it works, severe pain when risk/KYC fires g2.com ↗
Smaller hardware ecosystem than Square / Clover -- limited terminal SKUs and no kitchen printer / KDS / kiosk lineup means food-service merchants outgrow it theretailexec.com ↗
© Supergood Systems, Inc.