Overview

Learn how Cards on File uses stored tokens and Account Updater data to improve payment decisions.

Cards on File lets you charge a payment method by using its stored token. Use Account Updater data and transaction responses before each retry.

Why it matters

A payment attempt has a cost. Repeated declines can also resemble fraud, especially in batch or recurring payment flows.

Use this guidance to:

• Avoid unnecessary authorization attempts.
• Reduce preventable decline rates.
• Request a new payment method when needed.

Recommended flow

1. Retrieve the latest token details when Account Updater is enabled.
2. Evaluate token-update-status before authorizing the payment.
3. Process the payment only when the status allows it.
4. Evaluate decline codes and stop retries when required.
5. Collect updated payment details when the stored method cannot be used.

Account Updater information can appear in a token response. It can also appear with a token-based authorization response.

Key fields

Use these fields to evaluate token updates and declined transactions.

Field	Purpose
token-id	Identifies the stored payment method.
token-update-status	Reports the latest Account Updater result.
result-code	Identifies the issuer response for a declined transaction.
display-message	Provides a readable decline message.

Related topics

• See Account Updater Responses before authorizing a stored token.
• See Manage Declines to determine whether a retry is allowed.
• See Tokens before implementing token retrieval.