# Update the beneficiary name of an outgoing wire transfer

Update the beneficiary name of an OWT in PENDING_CONFIRMATION state. Clears and re-runs CoP/VoP validation with the new name.

Endpoint: PATCH /outgoing_wire_transfers/{id}
Version: v3
Security: auth_token, api-key

## Path parameters:

  - `id` (string, required)
    The unique identifier of the Outgoing Wire Transfer transaction.

## Request fields (application/json):

  - `name` (string)
    The new beneficiary name. Mutually exclusive with acceptVerifiedName. For FasterPayments/BACS: max 140 chars matching pattern ^[a-zA-Z0-9\/\-?:().,'+\s#=!"%&;\{@\r\n]$. For IBAN: max 150 chars.

  - `acceptVerifiedName` (boolean)
    Set to true to accept the account name returned with a CLOSE_MATCH or EXACT_MATCH VoP/CoP result. Mutually exclusive with name.

## Response 200 fields (application/json):

  - `id` (string, required)
    The unique identifier of an Outgoing Wire Transfer transaction.

  - `profileId` (string, required)
    The profile Id which a specific identity, instrument or transaction type is linked to.

Profiles contain configuration and determine behavioral aspects of the newly created transaction, for example, fees that may apply.

You can have one or more profiles linked to your application, and these can be used to drive different behaviors according to your product's needs.

Profile Ids can be found in the Multi Portal, in the API Credentials page.

  - `tag` (string)
    The tag field is a custom field that can be used to search and filter.

  - `sourceInstrument` (object, required)
    The source managed account from where the funds were taken.

  - `sourceInstrument.type` (string, required)
    Enum: "managed_accounts"

  - `sourceInstrument.id` (string, required)

  - `transferAmount` (object, required)
    The amount, in same currency as source and destination, that was transferred from the source.

  - `transferAmount.currency` (string, required)
    The currency expressed in ISO-4217 code. Example: GBP, EUR, USD.

  - `transferAmount.amount` (integer, required)
    The monetary amount, scaled to the lowest denomination of the currency.

Example, an amount of 1000 for a EUR currency is actually 1000 Euro cents or EUR 10.00.

  - `purpose` (string)
    The purpose of the payment.

  - `description` (string)
    Transaction description.

  - `type` (string)
    The wire transfer rails used, from SEPA, Faster Payments, SWIFT or RIX.
    Enum: "SEPA", "FASTER_PAYMENTS", "SWIFT", "RIX"

  - `destination` (any)

  - `state` (string, required)
    The state of the Outgoing wire transfer transaction, as follows:
  - INVALID: The wire transfer has failed initial validation checks.
  - PENDING_CHALLENGE: The wire transfer requires the completion of a transaction confirmation challenge before it can be submitted.
  - SUBMITTED: The wire transfer has been submitted to the sending financial institution for processing.
  - REJECTED: The wire transfer that was submitted was rejected.
  - APPROVED: The wire transfer that was submitted has been approved and is being processed by the sending financial institution.
  - FAILED: There was an issue with the wire transfer, and the transaction has failed.
  - COMPLETED: The requested funds have been sent from the source instrument.
  - RETURNED: The wire transfer has been returned to the sender.
  - SCHEDULED: The wire transfer will be executed at the scheduled time.
  - CANCELLED: The scheduled wire transfer has been cancelled.
  - PENDING_CONFIRMATION: The wire transfer requires a manual confirmation by the user before proceeding.
    Enum: "INVALID", "PENDING_CHALLENGE", "SUBMITTED", "REJECTED", "APPROVED", "FAILED", "COMPLETED", "RETURNED", "SCHEDULED", "CANCELLED", "PENDING_CONFIRMATION"

  - `rejectedInfo` (string)
    Additional info when the outgoing wire transfer has been rejected, as follows:
  - SYSTEM: The wire transfer was rejected by the system.
  - USER: The wire transfer was rejected by the user.
    Enum: "SYSTEM", "USER"

  - `challengeExemptionReason` (string)
    The Reason the transaction was exempted from SCA verification
    Enum: "LOW_VALUE", "TRUSTED_BENEFICIARY"

  - `creationTimestamp` (integer, required)
    The time when the transaction was created, expressed in Epoch timestamp using millisecond precision.

  - `scheduledTimestamp` (string)
    The epoch timestamp at which the transaction is scheduled to be executed.

  - `executionTimestamp` (string)
    The epoch timestamp at which the transaction was executed, transitioning to a final state such as COMPLETED, REJECTED, or FAILED.

  - `cancellationReason` (string)
    The reason the scheduled transaction was cancelled.

  - `validationOutcomes` (array)

  - `validationOutcomes.category` (string, required)
    Enum: "UK_CONFIRMATION_OF_PAYEE", "SEPA_VERIFICATION_OF_PAYEE"

  - `validationOutcomes.categoryResult` (any, required)

## Response 409 fields (application/json):

  - `errorCode` (string)
    Enum: "INVALID_STATE", "CONFLICT_BENEFICIARYID_NAME", "CONFLICT_EXTERNALACCOUNTID_NAME", "MODEL_CONSTRAINTS_VIOLATED", "NO_NAME_TO_ACCEPT"