---
title: "Reject an outgoing wire suspended for OFAC review"
method: POST
path: "/wires/{wire_id}/reject"
tags: ["Wires"]
---

# Reject an outgoing wire suspended for OFAC review

`POST /wires/{wire_id}/reject`

Declines an outgoing wire held in SUSPENDED_OFAC_REVIEW as prohibited or a true watchlist match, and notifies the fintech. Scope is limited to OFAC/watchlist decisions - true_match does not trigger any blocked-funds/GL movement in this phase. Requires the SyncteraForceTxnWrite permission. Resolving an already-resolved wire is idempotent.

## Path parameters

- `wire_id` string, uuid, required

## Headers

- `Idempotency-Key` string

## Request body

- RejectOfacWireRequest
  - `notes` string — Optional free-form notes recorded on the resolution audit record.
  - `reason` 'prohibited' | 'true_match', required — Structured decision reason for declining an outgoing wire suspended for OFAC review.

## Response `200`

Wire declined and removed from OFAC review

- Wire
  - `amount` integer, required — Transfer amount in cents ($100 would be 10000)
  - `bank_message` string — Instructions intended for the financial institutions that are processing the wire.
  - `batch_id` string, uuid — The batch ID associated with the wire if it was created via the batch payment API.
  - `case_id` integer — The case id associated with the wire.
  - `creation_time` string, date-time, required
  - `currency` string, required — 3-character currency code
  - `customer_id` string, uuid — The customer UUID representing the person initiating the Wire transfer
  - `effective_date` string, date, required — The effective date of the transaction once it gets posted
  - `fed_input_message_accountability_data` string — The Synctera-generated IMAD can be overwritten when the wire is uploaded to the FED. If that happens and we are provided with the new IMAD, it will be populated in this field.
  - `id` string, uuid, required — wire ID
  - `input_message_accountability_data` string — The input message accountability data consists of a 8 character cycle date (CCYYMMDD) an 8 character source and a 6 character sequence number.
  - `is_bulk` boolean, required — Whether or not the wire is a "bulk" wire created via the batch payment API.
  - `last_updated_time` string, date-time, required
  - `network` string — The network used to process the wire
  - `originating_account_id` string, uuid — Sender account ID
  - `originating_account_number` string, string, required — The account number representing the sender account. If the outgoing wire is a return, it refers to the sender of the initial wire not the sender of the return.
  - `receiving_account_id` string, uuid — The external account uuid representing the recipient of the wire.
  - `receiving_account_number` string, string, required — The account number representing the recipient account. If the outgoing wire is a return, it refers to the recipient of the initial wire not the destination of the return.
  - `recipient_message` string — Information from the originator to the beneficiary (recipient).
  - `return_data` ReturnData1 — Data associated with a returned wire
    - `original_end_to_end_identification` string
    - `original_id` string, uuid — UUID of the original wire that was returned. This field is populated if the system successfully matches the return to an original wire.
    - `original_instruction_identification` string
    - `original_transaction_id` string, uuid — Ledger transaction UUID of the original wire that was returned. This field is populated if the system successfully matches the return to an original wire.
    - `original_transaction_identification` string
    - `original_uetr` string
    - `previous_message_id` string, required — IMAD of the original wire that was returned
    - `reason` string — Additional information regarding the cause of the return
    - `reason_code` string — The code associated with the return reason
  - `sender_reference_id` string, required — Sender's id associated with fedwire transfer
  - `settlement_date` string, date — The settlement date of the transaction once it gets posted
  - `status` 'CANCELED' | 'COMPLETED' | 'DECLINED' | 'PENDING', required — The current status of the transfer
  - `status_details` 'APPROVED' | 'CANCELED' | 'DECLINED_DUAL_APPROVAL' | 'PENDING_DUAL_APPROVAL' | 'SUSPENDED_OFAC_REVIEW' — Additional details about the status of the transfer
  - `transaction_id` string, uuid, required — ID of the resulting transaction resource
  - `transaction_in_id` string, uuid — The transaction uuid of the incoming wire that triggered an outgoing return. This is only used if the outgoing wire is a return.

## Other responses

- `400` — BadRequest
- `401` — Unauthorized
- `403` — Forbidden error
- `404` — Resource not found
- `422` — Unprocessable entity request response
- `500` — Internal server error

---

[API](https://skmtc.net/synctera/apis/synctera-api.md) · [All operations](https://skmtc.net/synctera/apis/synctera-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/synctera/synctera-api/versions/b0d812e6cdd0/schema)