---
title: "Update Payee Details"
method: POST
path: "/v3/payees/{payeeId}/payeeDetailsUpdate"
tags: ["Payees"]
deprecated: true
---

# Update Payee Details

`POST /v3/payees/{payeeId}/payeeDetailsUpdate`

> **Deprecated.**

Use v4 instead

Update payee details for the given Payee Id.

## Path parameters

- `payeeId` string, uuid, required

## Request body

- UpdatePayeeDetailsRequestV3
  - `address` PayeeAddressV3
    - `line1` string, required
    - `line2` string, nullable
    - `line3` string, nullable
    - `line4` string, nullable
    - `city` string, required
    - `countyOrProvince` string, nullable
    - `zipOrPostcode` string, nullable
    - `country` string, required — Valid ISO 3166 2 character country code. See the <a href="https://www.iso.org/iso-3166-country-codes.html" target="_blank" a>ISO specification</a> for details.
  - `individual` IndividualV3
    - `name` IndividualV3Name, required
      - `title` string
      - `firstName` string, required
      - `otherNames` string
      - `lastName` string, required
    - `nationalIdentification` string — If not authorized to view, value will be masked. Example: XXXXX1234
    - `dateOfBirth` string, required — If not authorized to view, value will be masked. Example: - XXXX-XX-XX
  - `company` CompanyV3, nullable
    - `name` string, required
    - `taxId` string, nullable — Company Tax Id must be between 6 and 30 characters long
    - `operatingName` string, nullable
  - `language` string — An IETF BCP 47 language code which has been configured for use within this Velo environment.<BR> See the /v1/supportedLanguages endpoint to list the available codes for an environment.
  - `payeeType` 'Individual' | 'Company' — The type of the payee
  - `challenge` ChallengeV3
    - `value` string, required
    - `description` string, required
  - `email` string, email, nullable
  - `contactSmsNumber` string — The phone number of a device that the payee wishes to receive sms messages on

## Response `204`

Request accepted

## Other responses

- `400` — Invalid request. See Error message payload for details of failure
- `401` — Invalid access token. May be expired or invalid
- `403` — The authentication does not have permissions to access the resource This usually occurs when there is a valid authentication instance (client or user) but they do not have the required permissions
- `404` — The resource was not found or is no longer available

---

[API](https://skmtc.net/velopaymentsapi/apis/velo-payments-apis.md) · [All operations](https://skmtc.net/velopaymentsapi/apis/velo-payments-apis/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/velopaymentsapi/velo-payments-apis/revisions/05c3f09fc50a/schema)