ACH details, SEC codes & addenda

Read ACH details on a transfer

You can obtain details about a transfer involving the ACH payment rail through the transfers GET endpoint. If the source or destination uses an ACH payment method, the transfers details response will contain an achDetails object that contains useful information such as:

• traceNumber: tracking number (assigned by Moov) that can used by payment recipient to trace the payment with their external financial institution
• return: ACH return information per Nacha specification
  • code
  • reason
  • description
• correction: ACH notification of change information per Nacha specification
  • code
  • reason
  • description
• A transfer timestamp: Date-time information about transfer status changes
  • initiatedOn
  • originatedOn
  • correctedOn
  • returnedOn
  • completedOn

ACH statuses

The achDetails also contains rail-specific status information:

Customize ACH statement descriptors

You have the option to override the default Nacha file entries that appear on bank statements. To do this, set custom ACH statement descriptors when creating a transfer. Use the following fields on the source, destination, or both, to provide more clarity or context for an individual transfer:

• achDetails.companyEntryDescription: Describe the purpose of the transaction
• achDetails.originatingCompanyName: Set the name how you'd like it to appear on the statement

Customizing these fields on the source will update the information on the bank statement where the debit occurs. Customizing these fields on the destination will update the information on the bank statement where the credit occurs.

For example, in a transfer where the source and destination are the same Moov account, your account's ACH company name would be used as the default originating company name unless a customization was set. The example below sets custom descriptors for both the source and destination.

curl -X POST "https://api.moov.io/accounts/{accountID}/transfers" \
  -H "Authorization: Bearer {token}" \
  -H "x-idempotency-key: UUID" \
  -H "X-Wait-For: rail-response" \
  -H "x-moov-version: v2026.07.00" \
  --data-raw '{
    "amount": {
      "value": 100,
      "currency": "USD"
    },
    "destination": {
      "paymentMethodID": "string",
      "achDetails": {
        "companyEntryDescription" : "Gym dues",
        "originatingCompanyName" : "Whole Body Fit"
      }
    },
    "source": {
      "paymentMethodID": "string",
      "achDetails": {
        "companyEntryDescription" : "Gym dues",
        "originatingCompanyName" : "Whole Body Fit"
      }
    }
  }'

mc, _ := moov.NewClient()

var accountID string

mc.CreateTransfer(ctx, accountID, moov.CreateTransfer{
  Amount: moov.Amount{
    Currency: "USD",
    Value:    100, // $1.00
  },
  Destination: moov.CreateTransfer_Destination{
    PaymentMethodID: "string",
    AchDetails: &moov.CreateTransfer_AchDetailsBase{
      CompanyEntryDescription : "Gym dues",
      OriginatingCompanyName : "Whole Body Fit",
    },
  },
  Source: moov.CreateTransfer_Source{
    PaymentMethodID: "string",
    AchDetails: &moov.CreateTransfer_AchDetailsSource{
      CompanyEntryDescription : "Gym dues",
      OriginatingCompanyName : "Whole Body Fit",
    },
  },
})

Set the SEC code

You have the option of specifying an SEC code in certain ACH transfer request scenarios. If none is provided, Moov will handle the SEC code on your behalf (CCD for business accounts and PPD for individual accounts).

Individual to business transactions

You have the option of specifying an SEC code on an ACH transaction that has an individual account as the source and a business account as the destination. The following SEC codes can be provided in source.achDetails when making a transfer POST request: WEB, TEL, PPD. If no SEC code is provided, the SEC code will be set as WEB.

Other transaction scenarios

If the source and destination of an ACH transaction are both business accounts, the SEC code will be set as CCD. If the source is a business account and the destination is an individual account, the SEC code will be set as PPD.

Add addenda records

When you create a transfer, you can add supplemental payment information with an addenda record. Set an addenda in the source.achDetails and destination.achDetails object. Moov supports standard ACH and properly formatted TXP addenda.

Use cases for ACH addenda include:

• Tax payments (TXP addenda) required by the IRS and many state agencies
• B2B payments that include remittance or invoice references
• Specialized payments in healthcare, payroll, or government

The example below shows a transfer with a TXP addenda record. Addenda must use valid Nacha characters and be less than 80 characters in length.

curl -X POST "https://api.moov.io/accounts/{accountID}/transfers" \
  -H "Authorization: Bearer {token}" \
  -H "x-idempotency-key: UUID" \
  -H "X-Wait-For: rail-response" \
  -H "x-moov-version: v2026.07.00" \
  -d '{
    "amount": {
      "value": 10000,
      "currency": "USD"
    },
    "source": {
      "paymentMethodID": "afaa9b4a-4fd7-4678-9fb7-d62e550fa13c",
      "achDetails": {
        "secCode": "CCD",
        "companyEntryDescription": "Tax payment",
        "originatingCompanyName": "The Body Shop Yoga",
        "addenda": [
          {
            "record": "TXP*123456789*94105*960301*1*10000*2*5000*3*15000"
          }
        ]
      }
    },
    "destination": {
      "paymentMethodID": "346039ed-2282-4936-bc30-1c3c396876aa",
      "achDetails": {
        "addenda": [
          {
            "record": "Invoice #INV-2025"
          }
        ]
      }
    },
    "description": "Federal tax payment"
  }'

Data masking

ACH addenda, especially TXP records, may contain sensitive information such as SSNs or tax identifiers. For privacy and security reasons, Moov masks personally identifiable information and returns a safe addenda string in the response. If an addenda record has been masked, isMasked will be true, as shown below.

{
  "achDetails": {
    "addenda": [ 
      {
        "isMasked": true,
        "record": "TXP*XXXXX6789*94105*960301*1*10000*2*5000*3*15000"
      }
    ]
  }
}