Get ACH transfer details

Get ACH Transfer Details

The GET /api/fundsMovement/ACHTransferDetails/{transferId} endpoint allows users to retrieve detailed information about a specific ACH transfer. By providing the unique transferId, callers receive comprehensive data about the transaction, including amounts, statuses, sender and receiver details, and timestamps. This endpoint is essential for tracking, verifying, and auditing individual ACH transfers within banking applications.

Endpoint

GET /api/fundsMovement/ACHTransferDetails/{transferId}

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 you need to look up the full details of a previously initiated ACH transfer. It is suitable for displaying transfer status to end users, reconciling transactions in partner back-office systems, and confirming that a transfer completed successfully before triggering downstream business logic.

Path Parameters

Response

200 OK

Returns a structured object containing detailed information about the specified ACH transfer, including transaction amounts, current status, sender and receiver details, and relevant timestamps.

{
  "transferId": "txn_abc123xyz456",
  "status": "COMPLETED",
  "amount": 250.00,
  "currency": "USD",
  "direction": "CREDIT",
  "sender": {
    "accountNumber": "XXXXXXXXXX",
    "routingNumber": "XXXXXXXXX",
    "name": "Jane Smith"
  },
  "receiver": {
    "accountNumber": "XXXXXXXXXX",
    "routingNumber": "XXXXXXXXX",
    "name": "Acme Corp"
  },
  "initiatedAt": "2026-06-01T10:15:00Z",
  "settledAt": "2026-06-03T08:00:00Z",
  "description": "Invoice payment #1042"
}

Error Codes

Common Mistakes

• Passing an incorrect or stale transferId — make sure to use the ID returned at the time of transfer creation, not an internal reference number.
• Omitting the Authorization header or using an expired token will result in a 401 response; tokens expire after 10 minutes and must be refreshed via POST /api/auth/refresh.
• Attempting to retrieve a transfer that belongs to a different partner will return 403 — ensure the Bearer token corresponds to the partner that initiated or owns the transfer.

Related Endpoints

• POST /api/fundsMovement/ACHTransfer — Initiate a new ACH transfer
• GET /api/fundsMovement/ACHTransferList — List ACH transfers for an account
• POST /api/auth/refresh — Refresh an expiring Bearer token

Example

curl -X GET https://api.banking.netevia.dev/api/fundsMovement/ACHTransferDetails/txn_abc123xyz456 \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json"