---
title: "Update a Reader"
method: PATCH
path: "/v0.1/merchants/{merchant_code}/readers/{reader_id}"
tags: ["Readers"]
---

# Update a Reader

`PATCH /v0.1/merchants/{merchant_code}/readers/{reader_id}`

Update a Reader.

## Path parameters

- `merchant_code` string, required
- `reader_id` string, required — Unique identifier of the reader that the payment is initiated on.

## Request body

- object
  - `name` string — Custom human-readable, user-defined name for easier identification of the reader.
  - `metadata` Metadata — Set of user-defined key-value pairs attached to the object. Partial updates are not supported. When updating, always submit whole metadata. Maximum of 64 parameters are allowed in the object.

## Response `200`

Returns the updated Reader object if the update succeeded.

- Reader — A physical card reader device that can accept in-person payments.
  - `id` string, required — Unique identifier of the reader that the payment is initiated on.
  - `name` string, required — Custom human-readable, user-defined name for easier identification of the reader.
  - `status` 'unknown' | 'processing' | 'paired' | 'expired', required — The status of the reader object gives information about the current state of the reader. Possible values: - `unknown` - The reader status is unknown. - `processing` - The reader is created and waits for the physical device to confirm the pairing. - `paired` - The reader is paired with a merchant account and can be used with SumUp APIs. - `expired` - The pairing is expired and no longer usable with the account. The resource needs to get recreated.
  - `device` ReaderDevice, required — Information about the underlying physical device.
    - `identifier` string, required — A unique identifier of the physical device (e.g. serial number).
    - `model` 'solo' | 'virtual-solo', required — Identifier of the model of the device.
  - `metadata` Metadata — Set of user-defined key-value pairs attached to the object. Partial updates are not supported. When updating, always submit whole metadata. Maximum of 64 parameters are allowed in the object.
  - `service_account_id` string, uuid — Identifier of the system-managed service account associated with this reader. Present only for readers that are already paired. This field is currently in beta and may change.
  - `created_at` string, date-time, required — The timestamp of when the reader was created.
  - `updated_at` string, date-time, required — The timestamp of when the reader was last updated.

## Other responses

- `403` — The request isn't sufficiently authorized to modify the reader.
- `404` — The requested Reader resource does not exist.

---

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