Manage the Lifecycle of Checkout Tokens and Saved Payment Profiles

Classify the reference when it is created

A short-lived checkout token may be usable only for a specific submission. A gateway-managed saved payment profile may support future payments under account rules and customer permissions. Store the reference type, provider, environment, and customer association with the application record.

Handle deletion and replacement deliberately

When the user removes a method, check which system owns deletion and what should happen to any recurring orders. Update local display only with a confirmed state. When a replacement card or profile is created, verify it belongs to the correct merchant and customer before attaching it to an order or renewal.

Plan the end of a provider relationship

Ask how payment references are retained, moved, or deactivated in an approved migration. Some integration-specific references cannot be reused by a new provider. Plan how to request updated payment details from customers with affected future orders.

Validate lifecycle edge cases

• Short-lived token expires before checkout submits.
• A saved method is removed and no longer appears on a later order.
• A customer changes their default method without affecting another customer or merchant environment.