How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

ECI MFG Payment API

Credit card and ACH processing for ECI manufacturing products through the Paya payment gateway: payments, accounts, account vaults and contacts. Bearer tokens from the Integration Engine client-credentials flow. Not surfaced on the public documentation index (public: false in the portal manifest) but the contract is served anonymously.

ECI MFG Payment API is one of 15 APIs that ECI Solutions publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Payments, ACH, and Credit Cards. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 21 operations across 17 paths, organized into 4 resource areas, and defines 42 schemas. It is described by OpenAPI 3.0.1, at version 2.9.29+ff43d60aad.

Requests are made against the base URL https://payments-api.integrations.ecimanufacturing.com.

21 operations 17 paths 42 schemas 1 DELETE7 GET1 PATCH8 POST4 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
2.9.29+ff43d60aad
Base URL
https://payments-api.integrations.ecimanufacturing.com
Authentication
OAuth 2.0
Resource Areas
4

Authentication & Security 1

ECI MFG Payment API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (Bearer) using the clientCredentials flow, exposing 1 scope. By default, every request must be authenticated.

  • Bearer — OAuth 2.0 Client Credentials Flow with API Users issued from Integration Engine Management Console

Paths & Operations 21

Across 17 paths, the API surfaces 21 operations — 1 DELETE, 7 GET, 1 PATCH, 8 POST, 4 PUT. They span 4 resource areas: Account, AccountVault, Contact, Payment. Each is listed below with its method, path, parameters, and response codes.

Account 6
POST
/api/account/authenticatedeprecated
Authenticate user credentials.
body → 200
POST
/api/account/register
Creates a new Payment API user account and possibly company.
body → 200
POST
/api/account/verifypayamerchantaccount
Verify paya merchant account
body → 200
POST
/api/account/resendconfirmationemail
Resend confirmation mail
body → 200
POST
/api/account/verifymerchantaccountandauthenticateuser
Verify paya merchant account with user credentials
body → 200
GET
/api/account/me
Get details about the current user
→ 200
AccountVault 3
GET
/api/accountvault
Gets account vault details.
2 params → 200
PUT
/api/accountvault
Updates account vault details.
body → 200
DELETE
/api/accountvault
Deletes an account vault.
body → 200
Contact 5
POST
/api/contact
Creates a Paya contact.
body → 200
GET
/api/contact
Gets contact details.
2 params → 200
PATCH
/api/contact/{id}
Updates a contact.
1 param body → 200
GET
/api/contact/getaccountvaultsforcontact
Gets contact account vaults.
2 params → 200
GET
/api/contact/GetAccountNumberContacts
Gets contacts by account number.
3 params → 200
Payment 7
POST
/api/payment/accountVaultTransaction
Charges an account vault.
body → 200
PUT
/api/payment/accountVaultTransaction
Updates a transaction description.
body → 200
PUT
/api/payment/updateauthonlytransaction
Completes auth-only transactions.
body → 200
PUT
/api/payment/updateauthonlytransactionbyid
Completes a single transaction.
body → 200
GET
/api/payment/getalltransactions
Retrieves all transactions.
4 params → 200
GET
/api/payment/gettransactionsbystatus
Retrieves transactions by status.
4 params → 200
POST
/api/payment/updatetransaction
Updates a transaction.
body → 200

Schemas 42

The contract defines 42 schemas that model the data the API accepts and returns. The most detailed are AccountVaultDetail (32 properties), Contact (15 properties), AccountVaultTransaction (13 properties), UpdateContact (12 properties). Each schema is shown below with its type and property counts.

AccountNumberContacts
object
2 properties
AccountNumberContactsAPIResponse
object
5 properties
AccountVaultDetail
object
32 properties
AccountVaultDetailRequest
object
2 properties 2 required
AccountVaultDetailResponse
object
1 property
AccountVaultDetailResponseAPIResponse
object
5 properties
AccountVaultListResponse
object
3 properties
AccountVaultListResponseAPIResponse
object
5 properties
AccountVaultTransaction
object
13 properties 6 required
AccountVaultUpdate
object
4 properties 4 required
AccountVaultUpdateModel
object
1 property
ApiError
object
6 properties
ApiUserSettings
object
8 properties
ApiUserSettingsAPIResponse
object
5 properties
AuthOnlyTransactionDetail
object
5 properties 3 required
AuthOnlyTransactionDetailNoBase
object
3 properties 1 required
AuthOnlyTransactionDetails
object
3 properties 3 required
AuthenticateUser
object
2 properties 2 required
AuthenticateUserResponse
object
4 properties 2 required
AuthenticateUserResponseAPIResponse
object
5 properties
Contact
object
15 properties 3 required
ContactAPIResponse
object
5 properties
Links
object
1 property
MerchantAccountModel
object
2 properties 2 required
MerchantUserModel
object
2 properties
PaymentTransaction
object
4 properties 3 required
RegistrationModel
object
12 properties 5 required
ResendConfirmEmailModel
object
1 property 1 required
Self
object
1 property
StringAPIResponse
object
5 properties
TransactionResponse
object
10 properties
TransactionResponseAPIResponse
object
5 properties
TransactionStatusDetail
object
11 properties
TransactionStatusResponseRoot
object
2 properties
TransactionStatusResponseRootAPIResponse
object
5 properties
TransactionUIDetail
object
10 properties
TransactionUIResponseRoot
object
1 property
TransactionUIResponseRootAPIResponse
object
5 properties
TransactionUpdateModel
object
5 properties 4 required
TransactionUpdateRequestModel
object
For updating an existing transaction by id
1 property 1 required
UpdateContact
object
12 properties 1 required
ValidationError
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

eci-solutions-payment-openapi.json Raw ↑

Other APIs ECI Solutions publishes across the network.

ECI Manufacturing ERP API
JobBOSS² Public API
M1 Public API
ECI MFG Integration Management API
ECI Authentication API
ECI Financial Integration API
ECI EvolutionX Ecommerce API
ECI Einvoice API
ECI Shipping API
ECI Currency Data API
ECI AP/AR Commerce Automation API
ECI Office Integration API
Where this information came from

This is an independent, third-party profile of ECI MFG Payment API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.