By Grant Holloway, merchant banking operations analyst with 8 years of experience supporting ACH authorization, payment returns, and deposit reconciliation
Last reviewed: July 24, 2026
Helcim is a merchant payment platform for eligible businesses accepting cards, invoices, online payments, and customer bank transfers. U.S. merchants can use Helcim ACH to pull authorized payments from customer checking or savings accounts, while deposits are sent to the bank account connected to the merchant profile.
This independent guide is not operated by or affiliated with Helcim. Login recovery, bank-account updates, ACH collection, refunds, and funding questions should be handled through Helcim’s authenticated services.
What Helcim ACH is used for
Helcim ACH lets an eligible U.S. business collect money directly from a customer’s bank account. It can be used through tools such as Invoicing, Payment Requests, Recurring Payments, and the browser-based Virtual Terminal.
ACH is often considered for larger invoices, scheduled billing, and customers who prefer not to pay by card. Helcim currently publishes ACH pricing of 0.5% plus $0.25 per approved transaction, capped at $6 for qualifying transactions below $25,000. A rejected or returned transfer carries a published $5 charge.
That fee structure does not make ACH identical to a card transaction.
A card may produce an immediate authorization result. ACH moves through the banking network and can remain unsettled for several business days. A submitted bank payment can also be returned later.
Treat the status carefully.
Where to log in to Helcim
The official Helcim login screen contains fields for the user’s email and password, a Forgot password? link, a Login button, and a signup route for new merchant applicants.
Helcim documents the browser access process as:
- Open Helcim’s main website.
- Select Log in in the upper-right corner on a computer.
- On mobile, open the three-line menu and select Log in.
- Enter the email and password assigned to the user profile.
- Complete any additional verification shown.
Use the account email assigned to the individual employee. A business owner, billing administrator, and cashier may all work inside one merchant account while using separate profiles.
Check the user first. Skip an owner-level password reset when only one employee cannot sign in.
How Helcim ACH gets enabled
Helcim says ACH is available to eligible merchants and can be configured for supported payment tools from inside the account. The ACH settings determine where bank payments appear across tools such as Invoicing, Recurring Payments, Payment Requests, and Virtual Terminal.
Before collecting the first bank payment, confirm:
- ACH is available for the merchant account.
- The intended Helcim tool allows ACH.
- The customer-facing payment page presents the correct business.
- Staff understand the difference between submitted and settled.
- The receiving merchant bank account is correct.
Do this before sending a large invoice. Skip assumptions based on seeing an ACH option elsewhere in the dashboard.
Regional limits matter. Helcim’s developer documentation states that cross-border ACH is not supported and that the customer for the originating payment should reside in the same country as the merchant.
How customers authorize a bank payment
An ACH debit pulls funds from the customer’s account after the customer provides authorization. The merchant therefore needs a supported Helcim workflow that records or obtains that permission.
A customer can complete an ACH payment through a Helcim-hosted invoice or payment request. A merchant may also process an authorized ACH transaction through Virtual Terminal. Helcim describes Virtual Terminal as a browser-based tool that works from an internet-connected computer, tablet, or smartphone without separate POS hardware.
The customer-facing path is normally preferable when the customer should enter and authorize the bank information directly.
Use an invoice or Payment Request for customer entry. Use Virtual Terminal when the merchant has an appropriate authorization and is responsible for processing the transaction.
Do not treat a stored customer bank account as permission for every future charge. The business’s agreement and applicable authorization requirements still matter.
ACH verification is not the payment itself
A customer bank account may require setup or verification before it can be used in a supported ACH workflow. Verification establishes or confirms the payment method; it does not prove that a particular invoice has been paid.
That distinction creates three separate events:
- The bank account is added or verified.
- The customer authorizes a payment.
- The ACH transaction settles or is returned.
A merchant can therefore have a valid customer bank profile with no completed payment attached to it.
Keep the invoice status separate from the bank-account status. Skip marking an invoice paid because the customer completed only the account-setup step.
Helcim’s ACH materials describe initial setup and the first payment as potentially taking about three business days, with later payments commonly requiring additional banking time before the merchant sees the funds.
How long Helcim ACH deposits take
Helcim’s current ACH product page provides two timing descriptions. It says ACH transfers typically take about three business days during initial setup and first payment, and that payments may take three to four business days to be withdrawn from the customer’s bank. It also states that merchant funds may appear four to six business days after the batch is processed.
These are business-day estimates, not calendar-day promises.
Weekends and bank holidays do not count as ordinary ACH processing days. A transaction started on Friday may therefore remain in progress through the weekend.
The customer’s account being debited and the merchant’s bank receiving the deposit may also occur on different dates.
Use the status inside Helcim first. Skip delivery promises based only on the customer saying that money has left the bank.
Submitted, settled, returned: read the correct status
ACH transactions can move through several stages. The exact labels shown may depend on the Helcim tool or integration, but merchants should distinguish at least these conditions:
| Condition | Practical meaning |
|---|---|
| Created or requested | Payment flow has been started |
| Submitted or processing | Transaction has entered the bank-payment process |
| Settled | Processing has progressed through settlement |
| Returned or rejected | The bank network did not complete the payment |
| Refunded or voided | The merchant reversed the transaction through an available action |
The developer ACH API supports processing, retrieving, refunding, voiding, cancelling, and working with ACH batches. This reinforces that an ACH transaction can have several distinct states rather than one simple paid label.
Do not ship expensive goods at the request stage. Confirm the business’s acceptable risk point and the status Helcim actually displays.
Why an ACH payment can be returned
An ACH transfer may be rejected during submission or returned after it initially appears to be progressing. Causes can involve the customer’s bank account, authorization, account status, banking restrictions, or information provided during the payment flow.
Helcim currently publishes a $5 fee for returned or rejected ACH transfers.
A return can also reverse money that the merchant expected to retain. This is why ACH sales should not be reconciled solely from the first bank deposit.
When a return appears:
- Open the original Helcim transaction.
- Review the displayed return or rejection status.
- Match any related bank withdrawal.
- Reopen or adjust the customer invoice as appropriate.
- Contact the customer through the business’s normal billing process.
Do not immediately create a second debit without confirming what happened to the first attempt.
ACH refunds differ from card refunds
ACH reversals should not be handled as though they were card credits.
The Helcim ACH API includes separate refund, void, and cancellation capabilities, which indicates that the available action depends on transaction status and timing.
A void or cancellation may be available before settlement reaches a later stage. A refund applies after the payment has moved further through processing.
ACH refunds can also require more time than a customer expects because money must travel back through the banking system. The merchant should review the original transaction and use the action displayed by Helcim rather than creating an unrelated outgoing payment.
Use the original record. Skip improvised repayment methods that disconnect the return from the customer’s invoice.
How merchant deposits should be traced
A completed customer payment does not necessarily create one bank entry with the same amount.
Helcim may group several transactions into a batch. Processing fees, refunds, ACH returns, card disputes, or other adjustments can affect the final deposit or create a later withdrawal.
Follow this path:
Customer authorization → ACH transaction → ACH batch → merchant deposit → bank posting
The batch is the bridge between the individual customer payment and the merchant’s bank account.
One experienced-user detail matters: compare business dates, not just amounts. A payment initiated late in the week may appear in a batch and bank statement several days apart.
Check the batch first. Skip searching only for a deposit equal to the invoice total.
Changing the bank account receiving deposits
A merchant-bank change affects where processed funds are delivered, so it should be handled only from inside the authenticated Helcim account or through Helcim’s documented support process.
Before making the change, review:
- The legal owner of the receiving account
- The business name connected with the merchant profile
- The account selected as the deposit destination
- Pending batches that may already be in progress
- Any displayed confirmation or verification requirement
Do not assume a bank change redirects every deposit immediately. A batch already moving through settlement may continue toward the previously configured destination, depending on its processing stage.
The exact timing is account-specific. When the change affects urgent funding, use Helcim support rather than relying on an unofficial estimate.
Account ownership and employee access
Banking and payment controls should not be available to every employee.
An employee who sends invoices may need customer and transaction tools but not permission to replace the deposit account. A bookkeeper may need reports without the authority to issue refunds or manage other users.
Use separate profiles and the narrowest workable permissions. Skip shared administrator credentials.
Ownership changes deserve even more care. Changing a login email is not necessarily the same as changing the legal owner or business entity connected with a merchant account. A true ownership change can affect underwriting, tax records, banking, and merchant agreements.
Contact Helcim through an authenticated route when the legal business or ownership has changed. Do not simply edit a user’s name and assume the merchant account has been transferred.
Common Helcim ACH mistakes
The first mistake is treating bank-account verification as a completed payment. Verification prepares the method; the transaction still needs authorization and processing.
The second is counting calendar days instead of business days. ACH activity started before a weekend can appear delayed even when it remains within the published range.
A third error is delivering goods when the transaction is only requested or processing. ACH can still be returned.
The final mistake is searching for one deposit equal to one ACH invoice. Several payments can be grouped, while returns and fees can appear separately.
Status first. Bank balance second.
Frequently asked questions
Does Helcim support ACH payments?
Yes, for eligible U.S. merchants.
Can customers pay Helcim invoices by bank account?
Eligible merchants can offer ACH through supported tools, including Invoicing and Payment Requests.
How much does Helcim ACH cost?
Helcim currently publishes 0.5% plus $0.25 per approved transaction, capped at $6 for qualifying payments below $25,000.
How long does a Helcim ACH payment take?
Helcim says customer withdrawals commonly take three to four business days, while merchant funding may appear four to six business days after batch processing.
Can Helcim ACH be used across countries?
No. Helcim’s developer documentation says cross-border ACH payments are not supported.
Does Helcim charge for returned ACH payments?
Yes. The current published fee is $5 for a rejected or returned transfer.
Can I take ACH through Virtual Terminal?
Yes. Helcim’s browser-based Virtual Terminal supports ACH for eligible merchants.
Is a verified bank account the same as a settled payment?
No. Verification establishes the payment method; the individual transaction must still be authorized and processed.
Before relying on an ACH payment, confirm the customer authorization, current transaction status, batch record, and receiving bank deposit in that order.