Bank-to-bank (ACH / pre-authorized debit) money movement — withdraw, refund, void, cancel, retrieve ACH transactions, and list and settle ACH batches under the Helcim API v2.
Helcim ACH Payment API is one of 6 APIs that Helcim publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include ACH Payment, ACH, and Bank Payments. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.
This API exposes
48 operations
across 40 paths,
organized into 9 resource areas,
and defines 53 schemas.
It is described by OpenAPI 3.0.0, at version 2.2.0.
Requests are made against 2 base URLs: https://api.helcim.com/v2, https://api.helcim.test/v2.
48 operations40 paths53 schemas2 DELETE23 GET3 PATCH13 POST7 PUT
Metadata
The identity and technical contract details declared by the specification.
Specification
OpenAPI 3.0.0
API Version
2.2.0
Base URL
https://api.helcim.com/v2
Authentication
API Key
Resource Areas
9
Authentication & Security 1
Helcim ACH Payment API declares
1 security scheme
for authenticating requests.
An API key is passed in the header as api-token (ApiAccessAuth).
ApiAccessAuth — API Token with required permissions
Paths & Operations 48
Across 40 paths, the API surfaces 48 operations — 2 DELETE, 23 GET, 3 PATCH, 13 POST, 7 PUT. They span 9 resource areas: General, Payment, Card Batch, Card Transaction, Customer, Invoice, ACH Payment, Card Terminal, Device. Each is listed below with its method, path, parameters, and response codes.
The contract defines 53 schemas that model the data the API accepts and returns. The most detailed are InvoiceResponse (27 properties), TransactionEft (20 properties), SuccessfulPaymentResponse (18 properties), BankAccountResponse (16 properties). Each schema is shown below with its type and property counts.
Card
object
4 properties4 required
Address
object
9 properties3 required
PaymentRequestBase
object
9 properties4 required
InvoiceBase
object
2 properties
InvoiceWithTip
Shipping
object
3 properties3 required
Pickup
object
2 properties1 required
Tax
object
2 properties2 required
Discount
object
2 properties2 required
LineItem
object
6 properties3 required
InvoiceCreateAfterProcessing
object
5 properties
PaymentRequest
CardToken
object
1 property1 required
CardData
object
1 property1 required
FailedPaymentResponse
object
1 property
SuccessfulPaymentResponse
object
18 properties
PreauthRequest
CaptureRequest
object
4 properties3 required
VerifyRequest
object
9 properties5 required
BankAccount
object
15 properties11 required
BankToken
object
1 property1 required
BankData
object
1 property1 required
SuccessfulAchTransactionResponse
object
12 properties
CardBatch
object
15 properties
Customer
object
8 properties
CustomerRequest
object
6 properties
CustomerUpdateRequest
object
6 properties
CardResponse
object
8 properties
Pad
object
13 properties
Res
object
1 property
Message
object
1 property
BankAccountResponse
object
16 properties
Req
object
14 properties8 required
Res-2
object
2 properties
Res-3
object
1 property
Req-2
object
4 properties
OrderField
object
2 properties
InvoiceResponse
object
27 properties
InvoiceUpsertRequest
object
14 properties2 required
Req-3
object
5 properties4 required
TransactionEft
object
20 properties
Res-4
object
1 property
Req-4
object
1 property1 required
Res-5
object
1 property
Res-6
object
1 property
Res-7
object
1 property
AchBatch
object
14 properties
Res-8
object
1 property
CardTerminal
object
5 properties
Device
object
2 properties
FailedResponse
object
1 property
PaymentRequest-2
object
4 properties2 required
RefundRequest
object
2 properties2 required
Specification
The full machine-readable OpenAPI contract behind this narrative.