# Account Updates
source: https://developer.mastercard.com/payment-account-management/documentation/api-overview/account-update/index.md

The [Update Account](https://developer.mastercard.com/payment-account-management/documentation/api-reference/index.md) endpoint is used by an issuer or issuer's processor to advise of changes to an account. It will update the old PAN, expiration date, or PAN sequence number of the obsolete card with the replacement PAN, expiration date, or PAN sequence number of the new card.

If the PAN of the old card is mapped to a PAR, the same PAR value will be mapped to the PAN of the new card and associated tokens.

There are five reasons for sending an account update call:

* When an issuer changes the Brand Product for one of their cardholders to Mastercard, for example, Visa to Mastercard. During a brand flip update, the new account number must differ from the old account number.
* When an issuer changes portfolio from other networks to Mastercard, for example, Mastercard Gold to Mastercard World. During a portfolio flip, the new account number must differ from the old account number.
* When an existing cardholder's account number is changed, for example, PAN A to PAN B. During a replacement card update, the new account number must differ from the old account number.
* When an expiration date of an existing card is changed, for example, PAN A with expiration date 10-2024 is updated to PAN A with expiration date 10-2027. During an expiration change, both the old and new account number must be the same.
* When the card sequence number of an existing card is changed, for example, PAN A with card sequence number 01 is updated to PAN A with card sequence number 04. During a sequence number change, both the old and new account number must be the same.

### Required Fields {#required-fields}

Accounts may only be updated using the card number and the recommended parameters. Only one account update can be updated in a request corresponding to the reson code. The below table shows the parameters that apply for each of the following scenarios:

++**Key**++ ++**Description**++

**\[1\]** When an issuer changes portfolio from other network to Mastercard

**\[2\]** When an issuer upgrades the Product for one of their cardholders

**\[3\]** When an existing cardholder's account number is changed

**\[4\]** When an expiration date of an existing card is changed

**\[5\]** When the card sequence number of an existing card is changed

|           Scenario           |   \[1\]    |     \[2\]      |      \[3\]       |     \[4\]      |          \[5\]          |
|------------------------------|------------|----------------|------------------|----------------|-------------------------|
| Reason Code                  | BRAND FLIP | PORTFOLIO FLIP | REPLACEMENT CARD | EXPIRY UPDATED | SEQUENCE NUMBER UPDATED |
| Equivalent ABU Reason Code   | B          | P              | R                | E              |                         |
| Is ABU updated?              | ✔          | ✔              | ✔                | ✔              | ✖                       |
| Is MDES updated?             | ✖          | ✔              | ✔                | ✔              | ✔                       |
| Is PAR Vault updated?        | ✖          | ✔              | ✔                | ✖              | ✖                       |
| **OLD CARD DATA Fields**     |            |                |                  |                |                         |
| Old Card Number              | **🗹**     | **🗹**         | **🗹**           | **🗹**         | **🗹**                  |
| Old Expiry Year              | **🗹**     | **🗹**         | **🗹**           | **🗹**         | **🗹**                  |
| Old Expiry Month             | **🗹**     | **🗹**         | **🗹**           | **🗹**         | **🗹**                  |
| Old Card Sequence Number^\*^ | **☐**      | **☐**          | **☐**            | **☐**          | **🗹**                  |
| **NEW CARD DATA Fields**     |            |                |                  |                |                         |
| New Card Number              | **🗹**     | **🗹**         | **🗹**           | **↶**          | **↶**                   |
| New Expiry Year              | **🗹**     | **🗹**         | **🗹**           | **🗹**         | **↶**                   |
| New Expiry Month             | **🗹**     | **🗹**         | **🗹**           | **🗹**         | **↶**                   |
| New Card Sequence Number     | **☐**      | **☐**          | **☐**            | **☐**          | **🗹**                  |

Key: \[✔ = Yes; ✖ = No; **🗹** = Mandatory; **☐** = Optional; **↶** = Reuse Old Card Number; *Blank* = Do Not Include\]

^\*^ You should not include the Old Card Sequence number field unless it is reason code `SEQUENCE_NUMBER_UPDATED`. If you enter the wrong number it will prevent the update of the associated Tokens.

### Sequence of calls for expiry update and PAN sequence number update {#sequence-of-calls-for-expiry-update-and-pan-sequence-number-update}

1. First update expiry date with the old date in `oldCardInfo` and the new date in `newCardInfo`. Do not include the PAN sequence number fields in this request.
2. The second request to update Pan Sequence should contain new expiry date in both `oldCardInfo` and `newCardInfo`.

If you decide to update PAN sequence number before the expiry update:

1. Update PAN Sequence number with the old expiry date in both `oldCardInfo` and `newCardInfo`.
2. Update expiry date with the old date in `oldCardInfo` and the new date in `newCardInfo`. Do not include the PAN sequence number fields in this request.

Note:   

* PAN updates across different account ranges with the reasoncode `BRAND_FLIP` will only be updated in ABU.
* The ABU reason codes X and Y are not currently supported in PAM.
* A successful response to `/updateAccount` API means that the API call has been received successfully. It does not provide information on whether the updates have been applied in ABU, MDES Vault, or PAR Vault. Customers should use the `requestStatus` call to get that additional information.