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

# Payment Methods

> How saved payment methods stay current—stable IDs, lifecycle statuses, network tokens, and what changes under an ID you already stored.

A saved payment method keeps the same ID for its whole life. When a customer's card is reissued, re-expires, or has its network token refreshed by the card network, PayNext updates that payment method in place—it does not create a new one.

That keeps your customer records and subscriptions intact across a card reissue, without asking the customer for anything. It also means the details behind an ID you stored can change.

<Warning>
  If you cache card details such as `last4`, the expiry, or the brand against a payment method ID, subscribe to [`customer.payment_method.updated`](/webhooks/introduction/event-types#payment-method-events) and refresh your copy when it fires. Nothing else tells you the card behind the ID changed.
</Warning>

## Lifecycle status

Every payment method returns a `status`.

| Status     | Meaning                                                 |
| :--------- | :------------------------------------------------------ |
| `active`   | Usable                                                  |
| `expired`  | The printed card expiry has passed                      |
| `replaced` | The card was reissued and newer details are in place    |
| `closed`   | The issuer closed the account                           |
| `invalid`  | The card details are no longer valid                    |
| `revoked`  | The customer cancelled the mandate or billing agreement |

For a card, `status` describes the physical card. For Cash App, Pix, PayPal Wallet, and Venmo, it follows the mandate or billing agreement: revoking it in the provider's own app sets `revoked`. Apple Pay and Google Pay wallet tokens are managed by the wallet and stay `active`.

## Network tokens

A <Tooltip tip="Processor-agnostic token that replaces the raw card number and survives card reissues.">network token</Tooltip> stands in for the card number when charging. The card networks keep it pointed at the customer's current card, so recurring charges keep working after a reissue, and authorization rates are typically higher than with a raw card number.

Cards with a network token return it under `details.network_token`, with its own `status`:

| Status                             | Meaning                                                |
| :--------------------------------- | :----------------------------------------------------- |
| `active`                           | Usable for charging                                    |
| `provisioning`                     | Being created                                          |
| `inactive`, `suspended`, `blocked` | Temporarily unusable; may recover                      |
| `expired`, `deleted`               | No longer usable                                       |
| `retired`                          | Removed by PayNext after a long period with no charges |
| `unknown`                          | No status reported                                     |

`details.network_token.last_synced_at` tells you when that state was last refreshed from the card network.

<Tip>
  **A card marked `expired` can still be chargeable.** The card status and the network token status are independent. While the network token is `active`, recurring charges go through it, and the printed expiry on the card no longer matters. Prompt the customer for a new card only when neither is usable.
</Tip>

## Card Account Updater

`card_updater` shows whether a card is enrolled in the card networks' account updater programs. When enrolled, a reissued card number and expiry are pushed to PayNext and applied to the existing payment method.

Enrollment depends on your processor supporting the service. See your processor's integration page for availability.

`fpan_out_of_sync` is informational: PayNext knows the stored card number is out of date and a refresh is on the way. Don't gate charging or customer prompts on it.

## Live values and charge-time values

The same payment method reads differently depending on where you see it:

| Where                                                      | What you get                                               |
| :--------------------------------------------------------- | :--------------------------------------------------------- |
| A customer, or the `customer.payment_method.updated` event | The current state                                          |
| A payment                                                  | The card details as they were at the moment of that charge |

`status`, `card_updater`, and `fpan_out_of_sync` are always the current values. `details.network_token.status` and `details.network_token.last_synced_at` are frozen at charge time on a payment, so a settled payment always shows what it was actually charged with.

## What happens when a payment method dies

When neither the card nor its network token is usable, or the customer revoked a mandate, PayNext stops attempting charges rather than sending a run of guaranteed declines. Subscriptions stay `past_due` and wait for a recovery. See [Recover Subscriptions](/guides/use-cases/recover-subscriptions#dead-payment-methods).

<Card title="Charge returning customers" icon="repeat" href="/guides/use-cases/charge-returning-customers">
  Use a saved payment method for a follow-up charge.
</Card>