# Settle ACH Origination

Simulates the receiving bank settling an ACH origination. Only available in sandbox.
Applies to an ACH origination in `IN_TRANSIT` status. In sandbox, an origination created with [Create ACH Origination](/products/partner-api/reference/ach/create_ach_origination_api_v1_jiko_accounts__account_id__ach_originating__post) reaches `IN_TRANSIT` on its own shortly after creation, and stays there until you settle or return it.
### What follows
- The origination moves to `PROCESSED` and you receive `transfers.ach.out.success`.
- A `DEBIT` origination, which pulls money from the counterparty, funds the account.

A `202` means the request was accepted, not that the origination has settled. Follow the outcome through webhooks and the origination's status.

Endpoint: POST /api/v1/sandbox/jiko-accounts/{account_id}/ach-originating/{transfer_id}/settle/
Version: Version: efe65e5b
Security: HTTPBearer

## Description:

  - `What follows` ()
    The origination moves to PROCESSED and you receive transfers.ach.out.success.A DEBIT origination, which pulls money from the counterparty, funds the account. A 202 means the request was accepted, not that the origination has settled. Follow the outcome through webhooks and the origination's status.

## Security:

  - `HTTPBearer` (unknown)
    http bearer

## Path parameters:

  - `account_id` (string, required)

  - `transfer_id` (string, required)

## Header parameters:

  - `x-jiko-idempotency` (string, required)
    A UUID you generate to identify this request. Reusing a value that was already sent is rejected as a duplicate request.

  - `x-jiko-signature` (string, required)
    Base64-encoded HMAC-SHA256 hash of `x-jiko-idempotency + request pathname + body`, keyed with your shared secret. See [Authentication](/products/partner-api/guides/building/auth) for the full algorithm and a code sample.

## Response 202:

  - `202` (unknown)
    Successful Response

## Response 404:

  - `404` (unknown)
    Not Found

## Response 404 fields (application/json):

  - `type` (string, required)

  - `instance` (string, required)

  - `detail` (string, required)

  - `trace_id` (any)

## Response 422:

  - `422` (unknown)
    Unprocessable Content

## Response 422 fields (application/json):

  - `type` (string, required)

  - `instance` (string, required)

  - `detail` (string, required)

  - `trace_id` (any)

## Response 404 examples:

  - `Account not found` (unknown)

  - `Origination not found` (unknown)

## Response 422 examples:

  - `Origination not in transit` (unknown)