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

# Pagos Account Updater

Pagos provides two options for account updater:

> [card] [Batch Account Updater API](https://docs.pagos.ai/account-updater/batch-api-overview.md)
>
> Request updated card details in batches to keep your vault up to date.

> [card] [Real-Time Account Updater API](https://docs.pagos.ai/account-updater/real-time-api-overview.md)
>
> Update card details in real time during checkout to boost approval rates.

## Tips for Handling Updated Credentials Carefully

Account Updater updates attach to the card, not the transaction. As a result, Pagos Account Updater—both Real-Time and Batch—works for both customer-initiated and merchant-initiated payments, and for card-on-file or keyed cards. A few behaviors matter when you feed updated credential details back into authorizations or tokenization:

* If Pagos Account Updater returns a new PAN, drop the customer's CVV from the authorization. The CVV belongs to the old card.
* An updated expiry doesn't always mean a new card. Networks sometimes return a stale expiry or correct one a customer mistyped. If the authorization with the updated expiry declines, retry with the original.
* An expiry of 12/2099 is an industry placeholder, not a real date. Keep the customer's original expiry.
* Old credentials can keep working after a card is replaced. Only an authorization can confirm if the old credentials will still work; it's up to the issuer on which credentials they will accept.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.