ACH Standard Entry Class code

RCK SEC code: Re-presented Check Entry

Returned check re-presented as a debit.

What RCK is for

A paper check returned for insufficient or uncollected funds is presented again as a single ACH debit.

The consumer account a returned check is drawn on.

Authorization

Notice, given before the check is accepted, that a returned check may be re-presented electronically. The Rules limit which checks qualify, including an amount cap; check them before re-presenting.

A summary in general terms: the Nacha Operating Rules set the exact requirements, and Regulation E adds its own for consumer accounts.

Debits, credits and addenda

Debits only. A credit sent as RCK is returned R36.

Addenda on a forward entry: none on the forward entry. Returns (addenda type 99) and Notifications of Change (type 98) follow their own layouts whatever the SEC code.

Returns

RCK has its own codes: R50 (state law), R51 (ineligible item or improper entry; 60 days, written statement), R52 (stop payment; 60 days) and R53 (both the item and the entry presented; 60 days, written statement).

Common mix-ups

RCK re-presents a check that already bounced; ARC, BOC and POP convert a check that was never presented.

Where RCK sits in a NACHA file

The SEC code is a batch-level field: positions 51–53 of the Company/Batch Header record (type 5), so every entry in the batch shares it, and a file that mixes SEC codes puts them in separate batches. The batch header also carries the Company Name, Company Identification and Company Entry Description that Receivers see on their statements.

To read a RCK batch record by record, open the file in NACHA Navigator, a free sister site that parses NACHA files in your browser without uploading them.

Look up RCK from code or an AI agent

REST · GET · no key

curl -s 'https://payopskit.com/api/v1/codes/RCK?set=ach-sec'

MCP · tools/call · lookup_payment_code

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "lookup_payment_code",
    "arguments": {
      "code": "RCK",
      "set": "ach-sec"
    }
  }
}

Response (JSON)

{
  "code": "RCK",
  "set": "ach-sec",
  "found": true,
  "matches": [
    {
      "set": "ach-sec",
      "code": "RCK",
      "name": "Re-presented Check Entry",
      "description": "Returned check re-presented as a debit.",
      "details": {
        "direction": "debit",
        "addendaTypes": null,
        "minAddenda": 0,
        "maxAddenda": 0
      }
    }
  ]
}

The MCP server is at /mcp (Streamable HTTP, no key); the API and MCP docs show how to connect Claude, Cursor or VS Code.

Source: Nacha Operating Rules, Appendix Three (Standard Entry Class codes). The code’s name is the Rules’ own; the rest is this site’s plain-language summary, informational and not a substitute for the Rules or your ODFI agreement.