## Retrieve merchant settings

Retrieves current self-service settings for your merchant account. These are values you control directly and can modify using `update-merchant-settings`.

To view read-only account settings managed by Reservepay, use `retrieve-configuration`.

## Endpoint signature

```http
POST https://api.reservepay.com/merchants/retrieve-merchant-settings HTTP/1.1
Content-Type: application/json
Accept: application/json
Authorization: Bearer <token>

{}
```

Returns: object.merchant_setting

## Response attributes

### `preferred_communication_language` (string)

**Always present**. The preferred language for communication (e.g., 'en', 'th').

Possible values:

- `en`
- `th`

### `payout_contact_authorization_required` (boolean)

**Always present**. Whether contact payouts require authorization by a second user before processing.

Possible values:

- `true`
- `false`

### `payout_allow_self_authorization` (boolean)

**Always present**. Whether the user who requested the payout is allowed to authorize it themselves.

Possible values:

- `true`
- `false`

### `payout_skip_authorization_for_api_key` (boolean)

**Always present**. Whether payouts created via merchant API keys bypass the authorization requirement.

Possible values:

- `true`
- `false`

## Merchant setting attributes

### `preferred_communication_language` (string)

**Always present**. The preferred language for communication (e.g., 'en', 'th').

Possible values:

- `en`
- `th`

### `payout_contact_authorization_required` (boolean)

**Always present**. Whether contact payouts require authorization by a second user before processing.

Possible values:

- `true`
- `false`

### `payout_allow_self_authorization` (boolean)

**Always present**. Whether the user who requested the payout is allowed to authorize it themselves.

Possible values:

- `true`
- `false`

### `payout_skip_authorization_for_api_key` (boolean)

**Always present**. Whether payouts created via merchant API keys bypass the authorization requirement.

Possible values:

- `true`
- `false`

## Errors common to all endpoints

### `UNHANDLED_ERROR`

This error occurs when the server encounters an unexpected internal error that
it cannot handle gracefully. This typically happens due to bugs, infrastructure
issues, or edge cases that weren't anticipated during development.

### `INVALID_ARGUMENTS`

This error occurs when the request contains invalid or missing parameters.
Common cases include missing required fields, or values that don't match the
expected format or type.

### `BAD_VERSION`

This error occurs when making requests to an API version that does not exist.
This commonly happens when using an outdated SDK or when the API version
specified in the request URL is incorrect.