# transfers.ach.in.rejected

Incoming ACH Transfer - Rejected Event
Triggered when Jiko, when acting as the [RDFI](https://www.nacha.org/content/how-ach-payments-work) has rejected and returned an ACH transfer it received back to the ACH network.
The event names the ACH receiving by `ach_transfer_id`, which you can fetch with [Get ACH Receiving](/products/partner-api/reference/ach/get-ach-receiving-v1). It fires when the receiving's status becomes `REJECTED`. A rejected receiving can later be processed, so this event can be followed by a `transfers.ach.in.success` event for the same receiving.
Each status change has one event id. The same event can arrive more than once; discard repeats by `event_id`.

Endpoint: POST transfers.ach.in.rejected
Version: Version: 37bc941f

## Request fields (application/json):

  - `event_id` (string, required)

  - `timestamp` (string, required)

  - `payload` (object, required)

  - `payload.jiko_account_id` (string, required)

  - `payload.ach_transfer_id` (any)
    Present on every event sent after this field was introduced; older events returned by List Events do not have it.

  - `event_type` (string, required)

## Response 200:

  - `200` (unknown)
    Successful Response