wc-payment-tokens

To charge saved WooCommerce payment tokens, validate the posted saved-token selection at checkout by verifying the nonce, user ownership, and gateway ID, then attach the validated token to the order using HPOS-safe order token access patterns.

Creating WooCommerce payment tokens requires instantiating subclasses like WC_Payment_Token_CC or WC_Payment_Token_ECheck only after your provider returns a reusable provider token, ensuring you store provider tokens only and validate required fields like last4, expiry, and card type.

WooCommerce My Account saved payment method management involves securely adding, deleting, and setting default tokens, requiring strict user ownership and nonce checks to prevent unauthorized modification of saved payment tokens.

Yes, retrieve order-attached WooCommerce payment tokens with HPOS enabled by using HPOS-safe order token access APIs to fetch default tokens and read customer tokens without relying on deprecated post meta functions.

Checkout validation fails for saved WooCommerce payment tokens when gateway ID filtering is incorrect, the nonce check fails, or user ownership validation does not match the customer attached to the token.

Yes, you need a provider token to store WooCommerce saved card data because the system enforces provider-token-only storage, meaning raw card data is never exposed or trusted directly within the WC_Payment_Tokens implementation.