Initiate ACH transfer from own account

Initiate ACH Transfer From Own Account

This endpoint initiates an ACH (Automated Clearing House) transfer from a customer's Netevia financial account to a linked external account. The operation requires two-factor verification via a one-time code to authorize the movement of funds. This endpoint is deprecated — use the latest funds movement endpoints for new integrations.

Deprecated: This endpoint has been marked deprecated. Review the related endpoints section for the current ACH transfer workflow.

Endpoint

POST /api/fundsMovement/v2/ACHTransfer

Authentication

Bearer token required. Obtain via:

POST https://api.banking.netevia.dev/api/auth/v2

Include in header: Authorization: Bearer {token}
Token lifetime: 10 minutes. Refresh via POST /api/auth/refresh.

When to use

Use this endpoint when a customer needs to push funds from their Netevia financial account to an external bank account that has been linked via Finicity or Plaid. The transfer requires a one-time verification code to confirm the customer's identity before funds are moved, providing an additional layer of security for outbound ACH transactions.

Request Body

{
  "fromFinancialAccountId": "fa_9a8b7c6d5e4f3210",
  "toFinancialAccountId": "fa_ext_1a2b3c4d5e6f7890",
  "amount": 25000,
  "currencyCode": 840,
  "oneTimeCode": "847291",
  "secureOperationType": "ShortMessageCode",
  "memo": "Monthly savings transfer"
}

Response

200 OK

A 200 status indicates the ACH transfer was accepted and queued for processing. The response body is not detailed in the schema; confirm transfer status using the funds movement status endpoints.

{}

Error Codes

Common Mistakes

• Providing an amount of 0 — the minimum accepted value is 1 (representing 1 cent if currency is USD).
• Sending a oneTimeCode that is not exactly 6 digits — the field pattern requires ^\d{6}$ and any deviation (letters, fewer/more digits) will cause a 400 error.
• Using a toFinancialAccountId that refers to an account not linked or not yet verified via Finicity or Plaid — external accounts must complete underwriting verification before they can receive ACH transfers.
• Mismatching secureOperationType with the actual method used to generate the oneTimeCode — ensure the type matches how the code was delivered or generated.
• Omitting the currencyCode when an explicit currency is required by your integration — defaulting behavior may vary; always specify 840 for USD transfers.

Related Endpoints

• POST /api/auth/v2 — Obtain a Bearer token for authentication
• POST /api/auth/refresh — Refresh an expiring Bearer token
• GET /api/fundsMovement/v2/ACHTransfer/{transferId} — Check the status of a submitted ACH transfer
• POST /api/fundsMovement/v2/internalTransfer — Transfer funds between a customer's own Netevia accounts without ACH
• GET /api/financialAccounts — List financial accounts available for the customer

Example

curl -X POST https://api.banking.netevia.dev/api/fundsMovement/v2/ACHTransfer \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "fromFinancialAccountId": "fa_9a8b7c6d5e4f3210",
    "toFinancialAccountId": "fa_ext_1a2b3c4d5e6f7890",
    "amount": 25000,
    "currencyCode": 840,
    "oneTimeCode": "847291",
    "secureOperationType": "ShortMessageCode",
    "memo": "Monthly savings transfer"
  }'