--- title: "Create an Account Updater request for a card" method: POST path: "/cards/{card_id}/account-updater" tags: ["Account Updater"] --- # Create an Account Updater request for a card `POST /cards/{card_id}/account-updater` ## Request - Base URL: `https://test-api.acquired.com/v1` - URL: `https://test-api.acquired.com/v1/cards/{card_id}/account-updater` - Auth: HTTP bearer - TypeScript: (a function with typed inputs; its response is checked against the schema) Manually create an Account Updater request for a stored card, asking the scheme to refresh the credentials held for it. This is an alternative to Acquired.com's automatic Account Updater processes (rebill decline, retry advice and the monthly expiry sweep). The request body is empty - the card is identified by `card_id` in the path. When the `Mid` header is omitted, the Mid is resolved automatically: the card's originating Mid if it is Account Updater capable, otherwise your company's first Account Updater capable Mid. The request flows through the same send → scheme response → processing pipeline as automatically triggered requests. Use the [list endpoint](/reference/list-account-updater) to track its status and outcome. A card can only have one pending request at a time: if one already exists, it is returned with a `200` response instead of creating a new one. ## Path parameters - `card_id` string, uuid, required ## Headers - `Company-Id` string, uuid - `Mid` string, uuid ## Response `200` OK - a pending Account Updater request already exists for this card and is returned unchanged. - AccountUpdaterRequest - `id` string, uuid: Unique ID assigned by Acquired.com for the Account Updater request. - `card_id` string, uuid: The stored card the request relates to. - `customer_id` string, uuid: The customer the card belongs to. - `mid_id` string, uuid: The Mid the request was submitted under. - `initiated_by` 'manual' | 'decline' | 'retry_advice' | 'card_expiry', nullable: What created the request. `manual` indicates a manual request made through this API; the other values are set by Acquired.com's automatic Account Updater processes. May be `null` for some older requests, where the source was not recorded. - `status` 'pending' | 'submitted' | 'completed' | 'failed': The lifecycle state of the request. - `pending` - created and waiting to be sent to the scheme. - `submitted` - sent to the scheme, awaiting a response. - `completed` - the scheme returned a result. - `failed` - the scheme could not process the request. - `outcome` 'card_updated' | 'card_expiry_updated' | 'no_change' | 'account_closed' | 'card_not_found' | 'provider_error' | 'unknown', nullable: The result of the request once it completes. `null` until the request reaches a terminal state. - `card_updated` - the card number (and usually expiry) changed. - `card_expiry_updated` - only the expiry date changed. - `no_change` - the card is still valid with no changes. - `account_closed` - the cardholder should be contacted (e.g. the account is closed). - `card_not_found` - the scheme did not recognise the card. - `provider_error` - the scheme could not process the request. - `unknown` - the result could not be determined. Shown for some older requests, for which the outcome and `outcome_detail` are not available. - `outcome_detail` object, nullable: The before/after card details. Populated only for the `card_updated` and `card_expiry_updated` outcomes; `null` for every other outcome and while the request is not yet complete. Full card numbers are never returned. The card BIN (`previous_bin` / `new_bin`) is included only when your account is permitted to receive card BIN data; otherwise those fields are omitted from the response. - `previous_bin` string: First 6 digits (BIN) of the card before the update. Only present when your account is permitted to receive card BIN data. - `previous_last4` string: Last 4 digits of the card before the update. - `previous_expiry_month` integer: Expiry month of the card before the update. - `previous_expiry_year` integer: Two-digit expiry year of the card before the update. - `new_bin` string, nullable: First 6 digits (BIN) of the updated card. `null` when only the expiry changed. Only present when your account is permitted to receive card BIN data. - `new_last4` string, nullable: Last 4 digits of the updated card. `null` when only the expiry changed. - `new_expiry_month` integer, nullable: Updated expiry month. - `new_expiry_year` integer, nullable: Updated two-digit expiry year. - `created_datetime` string, date-time: When the request was created. - `submitted_datetime` string, date-time, nullable: When the request was sent to the scheme. `null` while the request is still pending. - `completed_datetime` string, date-time, nullable: When the scheme response was received. `null` until the request is completed or failed. ## Other responses - `201`: Created - a new pending Account Updater request was created. - `401`: Unauthorized - `403`: Forbidden - you do not have access to this card. - `404`: Not Found - the card does not exist within your scope. - `422`: Unprocessable Entity - the card is not eligible for Account Updater. See `reason_code`. ## Changes - **2026-11-03** `9c9e8ec96e98`: 1 info - removed the `network_token_provisioned` enum value from the `reason_code` response property for the response status `422` [Operation history](https://skmtc.dev/acquired/apis/acquired-api/changes/cards/:card_id/account-updater/post.md) --- [API](https://skmtc.dev/acquired/apis/acquired-api.md) - [All operations](https://skmtc.dev/acquired/apis/acquired-api/llms.txt) - [OpenAPI document](https://skmtc.dev/acquired/apis/acquired-api/revisions/9c9e8ec96e98?raw)