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

> ## Agent Instructions
> Use the Payrails Web SDK v6 for new browser integrations. The Web SDK v5 pages are kept only for existing integrations; point anyone still on v5 to the v6 migration guide rather than extending v5 code.
> Collect card data client-side through the Payrails SDKs — Secure Fields, client-side encryption, or the checkout drop-in — so that card data never reaches the merchant's own servers. Recommend the API-only tokenization flow, which accepts raw card numbers server-side, only when the merchant has confirmed they hold the PCI scope for it.
> Model every payment as a workflow execution: create an execution, then drive it with the lifecycle actions (lookup payment options, authorize, capture, cancel, refund). Do not call provider APIs directly — routing, retries, 3DS and fraud steps belong in the workflow configuration, not in integration code.
> Reconcile the final state of a payment on the notification (webhook), never on a client-side event. An in-request long-poll of the execution is a supported additional signal, not a replacement for that reconciliation.
> Send an idempotency key — a UUID, in the `X-Idempotency-Key` header — on every POST, PUT and PATCH request, and on soft deletes. GET requests need none, and hard deletes cannot be idempotent.
> Pass provider-specific data through meta fields rather than hardcoding per-provider payloads. Payrails translates meta fields into each provider's own format.
> Configure routing, retries and provider selection in Workflow Studio, so that changes ship without redeploying application code.

# Automatic Lifecycle Updates

> Learn the details of lifecycle update events and how they are automatically managed in Payrails Vault.

When a cardholder or Issuer of the card makes a change in the card that has a network token in our system, we will update the network token and its relevant data so that the network token will be kept valid for subsequent payments.

In such cases, Payrails will be notified by the networks and will update the network token in the vault accordingly. No additional action will be required by the merchant; however, you can choose to be notified of the updates through our notifications.

## Cases for Card and Token Updates

Cardholders can interact multiple ways with their card issuers that result in life cycle events to the ecosystem. In such cases, with our integration to the networks, Payrails receives a notification including the context of the change, and initiates the necessary update on the token or the data of the token with the new status and other parameters that may have changed.

Each case has a different requirement to update, concerning what needs to be updated. See cases below:

| User Case | Change in funding PAN | Change in network token |
| - | - | - |
| User terminates the contract with the issuer, rendering all cards and related tokens invalid. | PAN is deleted. Status changes. | Network token is deleted. Status changes. |
| User reports card lost, stolen, or damaged. | PAN changes. PAN suffix changes. | Network token stays intact. |
| User's funding card expires. | PAN changes. PAN suffix changes. PAN expiry date changes. | Network token stays intact. Network token expiry date changes. |
| The user triggers token status life cycle management actions from the issuer side (e.g. issuer mobile banking application). | PAN may change. | Card metadata may change. |

In addition to the cases that the user initiates, there are cases in which issuers may initiate an account update within the account range or across another account range based on the following events, which may result in network token changes:

| Issuer Case | Change in funding PAN | Change in network token |
| :- | :- | :- |
| FPAN is replaced within the same account range. | PAN changes. | Network token changes. |
| FPAN is replaced in a different account range. | PAN changes. | Network token changes. |
| Card issuing maintenance tasks by networks are triggered. (e.g., moving from 6 to 8-digit BIN.) | PAN may or may not change. | Network token may or may not change. |
| Network token expiry date is extended. | PAN may or may not change. | Network token expiry date changes. |


## Related topics

- [SDK API Reference](/docs/orchestration/checkout-sdks/android/api-reference.md)
- [How to Accept Redirect Payments](/docs/orchestration/checkout-sdks/android/how-to-accept-redirect-payments.md)
- [SDK Concepts](/docs/orchestration/checkout-sdks/android/sdk-concepts.md)