> ## Documentation Index
> Fetch the complete documentation index at: https://docs.revolv3.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Account Updater

> Learn how Account Updater automatically keeps stored credit card information current. Understand when cards are updated and how to handle update notifications.

## What is Account Updater?

**Account Updater** is a service that automatically updates stored credit card information when cards are:

* **Replaced**: Customer gets a new card (lost, stolen, expired)
* **Expired**: Card expiration date changes
* **Updated**: Bank changes card details

**Why it's useful:**

* **Reduces failed payments**: Cards stay current even when customers don't update them
* **Better for subscriptions**: Recurring payments continue working
* **Less customer friction**: Customers don't need to manually update expired cards
* **Higher success rates**: More payments go through successfully

**How it works**: When you process a payment, the processor checks with the card network to see if the card has been updated. If it has, Revolv3 automatically updates your stored payment method with the new information.

## When Account Updater Runs

Account Updater checks for updates:

* **During payment processing**: When you charge a stored payment method
* **Automatically**: Revolv3 handles it—you don't need to do anything
* **Periodically**: Processors check with card networks for updates

**You'll know an update happened** when you see `accountUpdateMessage` and `accountUpdateDateTime` in the payment response.

## Understanding Account Update Notifications

When Account Updater updates a card, you'll see additional fields in the payment response:

<CodeGroup>
  ```json theme={null}
  {
    "customerId": null,
    "invoiceId": 185317,
    "merchantInvoiceRefId": "ABC309500654810",
    "networkTransactionId": "538302743384089",
    "invoiceStatus": "Paid",
    "invoiceAttemptStatus": "Success",
    "message": "Approved",
    "amount": {
      "currency": "USD",
      "value": 1.03
    },
    "paymentMethodId": 6061,
    "paymentMethodTypeId": 1,
    "paymentProcessor": "WorldPay",
    "paymentMethodCreditCardDetails": {
      "binNumber": "444433",
      "paymentLast4Digit": "1111",
      "paymentExpirationDate": "1130",  // Updated expiration date
      "accountUpdateMessage": "NEW_EXPIRY",  // Indicates what was updated
      "accountUpdateDateTime": "2025-10-30T11:46:33"  // When it was updated
    }
  }
  ```
</CodeGroup>

## WorldPay Account Updater Response Codes

If you're using WorldPay, you may also see response codes with account update notifications:

| Code  | Response Message                               | What It Means                     | Recommendation                                                  |
| ----- | ---------------------------------------------- | --------------------------------- | --------------------------------------------------------------- |
| `500` | The account number was changed                 | Card number was updated           | Use the new account number from the response                    |
| `501` | The account was closed                         | Account is closed                 | Contact customer to collect new payment details                 |
| `502` | The expiration date was changed                | Expiration date updated           | Update stored expiration date (Revolv3 does this automatically) |
| `504` | Contact the cardholder for updated information | Bank requires contacting customer | Prompt customer to provide updated payment details              |
| `507` | Cardholder has opted out of the update program |                                   |                                                                 |

**Reference**: [WorldPay Account Updater Documentation](https://docs.worldpay.com/apis/wpg/usdomesticacquiring/managedaccountupdater)

## How to Handle Account Updates

### Automatic Updates (Recommended)

**Revolv3 handles updates automatically**—you don't need to do anything special. When Account Updater updates a card:

* Revolv3 updates the stored payment method
* Future payments use the updated information
* You're notified via `accountUpdateMessage` in the response

**What you should do:**

* **Log the update**: Store `accountUpdateMessage` and `accountUpdateDateTime` for your records
* **Notify customer** (optional): Let them know their card was updated automatically
* **Handle special cases**: Contact the customer

## Real-World Scenarios

### Scenario 1: Card Expiration Updated

**What happens:**

1. Customer's card expires (old: 03/25, new: 03/26)
2. You charge the stored payment method
3. Account Updater detects the new expiration
4. Revolv3 updates the stored payment method automatically
5. Payment succeeds with the updated expiration

**Response shows:**

```json theme={null}
{
  "accountUpdateMessage": "NEW_EXPIRY",
  "accountUpdateDateTime": "2025-10-30T11:46:33",
  "paymentExpirationDate": "0326"  // Updated date
}
```

**What you do**: Revolv3 handled it. Just log it for your records.

### Scenario 2: Card Replaced

**What happens:**

1. Customer's card was lost/stolen and replaced
2. New card has a new number
3. Account Updater detects the change
4. Revolv3 updates the stored payment method

**Response shows:**

```json theme={null}
{
  "accountUpdateMessage": "UPDATE",
  "paymentLast4Digit": "2222"  // New last 4 digits
}
```

**What you do**:

* Log the update
* Optionally notify customer that their card was updated
* Future payments will use the new card automatically

### Scenario 3: Account Closed

**What happens:**

1. Customer closed their account with the bank
2. Account Updater detects it
3. Payment may fail or be declined

**Response shows:**

```json theme={null}
{
  "accountUpdateMessage": "CLOSED"
}
```

**What you do**:

* Contact the customer
* Ask for a new payment method
* Update your records
* For subscriptions, pause until customer updates

## Best Practices

1. **Monitor account updates**: Log `accountUpdateMessage` to track when cards are updated
2. **Handle closed accounts**
3. **Notify customers**: Optionally notify customers when their card is automatically updated
4. **Keep records**: Store update timestamps for auditing
5. **Note**: Most updates are automatic and don't require action

## Processor Support

Account Updater is supported by:

* **WorldPay**: Full support with detailed response codes
* **Other processors**: Support varies—check with Revolv3

**In sandbox**: Account Updater is only supported by WorldPay. Other processors may not show account updates in sandbox.

## Common Questions

**Q: Do I need to do anything when a card is updated?** A: Usually no—Revolv3 handles it automatically. Just log the update for your records.

**Q: What if the account is closed?** A: Contact the customer to get a new payment method. The old one won't work anymore.

**Q: How often does Account Updater check?** A: It checks during payment processing. There's no separate "check" you need to run.

**Q: Can I disable Account Updater?** A: It's automatic and beneficial—there's usually no reason to disable it. Contact Revolv3 if you have specific concerns.

**Q: What if I don't see account update messages?** A: Either no update was needed, or your processor doesn't support Account Updater. Check with Revolv3.

## Next Steps

* [**Payment Methods Guide**](/docs/core-concepts/paymentmethod/paymentmethod-guide) — Learn about storing payment methods
* [**Subscriptions**](/docs/core-concepts/subscription/create-subscription) — See how Account Updater helps with recurring payments
* [**Make a Payment**](/docs/getting-started/make-a-payment) — See account update fields in payment responses

***