Update a recipient's account | Redpin

This OAuth 2.0 Authenticated Update Recipient API allows you to update the account details of an existing recipient associated with a specific customer.

Authentication

AuthorizationBearer

OAuth 2.0 Bearer token authentication. This API uses OAuth 2.0 Client Credentials flow. Please refer to the Authentication section for detailed information on how to obtain and use your OAuth credentials.

Path parameters

customer_idstringRequired

Unique identifier for the customer to whom the recipient belongs.

recipient_idstringRequired

Unique identifier of the recipient to be updated.

Request

This endpoint expects an object.

namestringRequired

Name of the recipient as per their bank records.

typeenumRequired

Organisational type of a recipient; whether an Individual or Corporate.

Allowed values:

customer_own_accountenumRequired

Recipient to be updated is customer own account or not.

Allowed values:

client_reference_idstringOptional

A Reference Id that you can assign to this recipient, for your records.

nick_namestringOptional

Optional nickname for the recipient. Useful for quick searches and display purposes.

emailstringOptional

Email address of a recipient, which may be used in case of an issue with a transaction.

phone_numberstringOptional

Recipient's phone number.

mobile_numberstringOptional

Recipient's mobile number.

country_codestringOptional

Three-letter ISO 3166-1 alpha-3 country code representing the recipient’s country.

Three-letter [ISO 3166-1 alpha-3](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-3) country code representing the recipient's country.

payment_referencestringOptional

Optional payment reference required by some accounts. This reference should be used for future payments. It should not contain any special character.

addressobjectOptional

recipient_bank_detailsobjectOptional

You must also specify the currency of the recipient’s bank account using a three-letter ISO 4217 currency code (e.g., GBP for British Pound).

The following are the four supported combinations of recipient bank account details:

iban
account_number and swift_code
account_number, swift_code, and routing_code_value
account_number, routing_code_type, routing_code_value, and bank_country_code

Examples:

IBAN:

1 {"currency": "AED", "iban": "AE070331234567890123456"}

Account number and Swift code:

1 {"currency": "AED", "account_number": "12345678", "swift_code": "BOMLAEADXXX"}

Account number, Swift code, and Routing code value:

1 {"currency": "AED", "account_number": "12345678", "swift_code": "BOMLAEADXXX", "routing_code_value": "601613"}

Account number, Routing code type, Routing code value, and Bank country code:

1 {"currency": "AED", "account_number": "12345678", "routing_code_type": "SORT", "routing_code_value": "601613", "bank_country_code": "ARE"}

Recipient bank account details vary by country. For example, an IBAN is sufficient for most European and Nordic countries. However, for the United States, you must provide an account number, routing code type, routing code value, and the bank's country code. You must also specify the `currency` of the recipient's bank account using a three-letter ISO 4217 currency code (e.g., `GBP` for British Pound). The following are the four supported combinations of recipient bank account details: - `iban` - `account_number` and `swift_code` - `account_number`, `swift_code`, and `routing_code_value` - `account_number`, `routing_code_type`, `routing_code_value`, and `bank_country_code` **Examples:** 1. IBAN: ```json {"currency": "AED", "iban": "AE070331234567890123456"} ``` 2. Account number and Swift code: ```json {"currency": "AED", "account_number": "12345678", "swift_code": "BOMLAEADXXX"} ``` 3. Account number, Swift code, and Routing code value: ```json {"currency": "AED", "account_number": "12345678", "swift_code": "BOMLAEADXXX", "routing_code_value": "601613"} ``` 4. Account number, Routing code type, Routing code value, and Bank country code: ```json {"currency": "AED", "account_number": "12345678", "routing_code_type": "SORT", "routing_code_value": "601613", "bank_country_code": "ARE"} ```

confirm_recipientobjectOptional

Container for confirmation of recipient details.

This object is required only when the initial API call fails due to a Confirmation of Payee (CoP) or Verification of Payee (VoP) check failure.

If the failure is related to CoP/VoP, the API response will include request_identifier and event_id, which must be used in the subsequent retry request along with the appropriate customer_action.

Detailed instructions for handling these scenarios can be found in:

Container for confirmation of recipient details. This object is required only when the initial API call fails due to a [Confirmation of Payee (CoP)](https://www.wearepay.uk/what-we-do/overlay-services/confirmation-of-payee/) or [Verification of Payee (VoP)](https://www.europeanpaymentscouncil.eu/what-we-do/other-schemes/verification-payee) check failure. If the failure is related to CoP/VoP, the API response will include `request_identifier` and `event_id`, which must be used in the subsequent retry request along with the appropriate `customer_action`. Detailed instructions for handling these scenarios can be found in: - [UK Confirmation of Payee (CoP) Guide](/api-guide/regulatory-guides/cop-guide) - [SEPA Verification of Payee (VoP) Guide](/api-guide/regulatory-guides/vop-guide)

additional_detailsobjectOptional

Additional details for the recipient.

Response

Recipient updated successfully

Errors