---
title: "Schedule running the Account Updater"
method: POST
path: "/scheduleAccountUpdater"
tags: ["General"]
---

# Schedule running the Account Updater

`POST /scheduleAccountUpdater`

When making the API call, you can submit either the credit card information, or the recurring detail reference and the shopper reference:
* If the card information is provided, all the sub-fields for `card` are mandatory.
* If the recurring detail reference is provided, the fields for `shopperReference` and `selectedRecurringDetailReference` are mandatory.

## Request body

- ScheduleAccountUpdaterRequest
  - `additionalData` object — This field contains additional data, which may be required for a particular request.
  - `card` Card
    - `cvc` string — The [card verification code](https://docs.adyen.com/payments-fundamentals/payment-glossary#card-security-code-cvc-cvv-cid) (1-20 characters). Depending on the card brand, it is known also as: * CVV2/CVC2 – length: 3 digits * CID – length: 4 digits > If you are using [Client-Side Encryption](https://docs.adyen.com/classic-integration/cse-integration-ecommerce), the CVC code is present in the encrypted data. You must never post the card details to the server. > This field must be always present in a [one-click payment request](https://docs.adyen.com/classic-integration/recurring-payments). > When this value is returned in a response, it is always empty because it is not stored.
    - `expiryMonth` string — The card expiry month. Format: 2 digits, zero-padded for single digits. For example: * 03 = March * 11 = November
    - `expiryYear` string — The card expiry year. Format: 4 digits. For example: 2020
    - `holderName` string — The name of the cardholder, as printed on the card.
    - `issueNumber` string — The issue number of the card (for some UK debit cards only).
    - `number` string — The card number (4-19 characters). Do not use any separators. When this value is returned in a response, only the last 4 digits of the card number are returned.
    - `startMonth` string — The month component of the start date (for some UK debit cards only).
    - `startYear` string — The year component of the start date (for some UK debit cards only).
  - `merchantAccount` string, required — Account of the merchant.
  - `reference` string, required — A reference that merchants can apply for the call.
  - `selectedRecurringDetailReference` string — The selected detail recurring reference. Optional if `card` is provided.
  - `shopperReference` string — The reference of the shopper that owns the recurring contract. Optional if `card` is provided.

## Response `200`

OK - the request has succeeded.

- ScheduleAccountUpdaterResult
  - `pspReference` string, required — Adyen's 16-character unique reference associated with the transaction. This value is globally unique; quote it when communicating with us about this request.
  - `result` string, required — The result of scheduling an Account Updater. If scheduling was successful, this field returns **Success**; otherwise it contains the error message.

## Other responses

- `400` — Bad Request - a problem reading or understanding the request.
- `401` — Unauthorized - authentication required.
- `403` — Forbidden - insufficient permissions to process the request.
- `422` — Unprocessable Entity - a request validation error.
- `500` — Internal Server Error - the server could not process the request.

---

[API](https://skmtc.net/adyen/apis/recurringservice.md) · [All operations](https://skmtc.net/adyen/apis/recurringservice/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/adyen/recurringservice/versions/c8af455aebe1/schema)