WooCommerce saved payment methods can make repeat checkout more convenient for customers who return to your store. In the documented Stripe for WooCommerce integration, an eligible logged-in customer can choose to save a payment method during checkout and use it again later. The feature is connected to the customer account, so it is different from a guest checkout flow.
This setup does not require the WordPress site to store the full card number and CVC directly. The integration uses tokenization: the payment processor retains the sensitive payment data, while the site uses a token or payment reference. That architecture reduces the need to handle raw card details, but it does not remove the need for HTTPS, maintained software, secure administration, gateway requirements, and appropriate compliance review.
What WooCommerce Saved Payment Methods Actually Do
When saved payment methods are enabled, a customer can associate an eligible payment method with a WooCommerce account. During a later checkout, the saved method can be selected again instead of entering payment details from the beginning. The documented behavior applies to the Stripe for WooCommerce integration; it should not be treated as a description of every third-party Stripe gateway or custom payment integration.
Account-based saving versus guest checkout
The account requirement is central to this feature. A logged-in customer can select “Save payment information to my account for future purchases” when that option is displayed. Guest checkout customers cannot save payment information through this account-based flow because there is no customer account with which to associate the saved method.
For that reason, the store must allow customer account creation if customers are expected to save methods. Account creation alone does not guarantee that every payment method will be available, but without an account the documented saving workflow cannot be associated with the customer.
Saved methods and Link are different flows
Stripe Link is a separate card-saving flow. If Link is enabled, it may save the customer’s cards within its own checkout experience. As a result, the standard WooCommerce saved-payment checkbox may be hidden. A missing checkbox therefore does not automatically mean that the Stripe configuration is broken; first determine whether Link is handling the saving experience.
Before Enabling the Feature in WooCommerce
Before making the feature available on a production store, review the documented settings and the customer account flow. The relevant configuration is located at WooCommerce > Settings > Payments > Stripe, in the Payments & transactions section.
Configuration checklist
- Open the Stripe settings at WooCommerce > Settings > Payments > Stripe.
- Enable saved card payment methods in the Stripe extension settings.
- Confirm that the store allows customer account creation.
- Check whether Link is enabled and understand which saving flow customers will see.
- Verify that the checkout uses HTTPS and that the intended payment methods are configured.
- Test the complete customer journey in a staging or test environment before enabling it on a live store.
These checks establish the conditions for the documented feature, but they do not guarantee universal availability. Country, currency, customer eligibility, payment-method rules, checkout configuration, and other gateway settings can affect what appears to a particular customer.
How Customers Save a Payment Method During Checkout
The customer-facing process is account-based. A customer signs in, or uses the store’s account-creation flow when account creation is allowed, and proceeds through checkout with an eligible payment method. If the saving option is available, the customer selects “Save payment information to my account for future purchases” before completing the payment.
The customer checkout sequence
- Sign in to a WooCommerce customer account, or create an account according to the store’s settings.
- Proceed to checkout and choose an eligible payment method.
- Select the save-payment option when it is displayed.
- Complete the purchase so the payment method can be associated with the customer account.
On a later checkout, the customer can select the saved method. The precise visibility of the option can vary with the checkout configuration and payment-method eligibility. Guest customers should not expect to see an account-based saving option.
Why the checkbox may be missing
Start by checking whether Link is enabled, because Link may save cards within its own payment flow and hide the usual WooCommerce checkbox. If Link is not the reason, review account-creation settings and the eligibility of the selected payment method. Restrictions connected with country, currency, gateway configuration, or other payment-method rules can also affect what the customer sees.
How Customers Manage Saved Payment Methods in My Account
After a method has been saved, customers manage it from My Account > Payment Methods. This area provides the account-level controls documented for the Stripe integration and gives customers a way to review their available payment methods outside the checkout page.
The My Account payment-methods screen
From the payment-methods screen, customers can add, view, and remove saved methods. They can also set a default method. The default method is selected first during a later checkout, which can make repeat purchases more direct while still leaving the customer able to choose another available method.
This workflow should be distinguished from Link’s own card-saving behavior. Removing a method from the WooCommerce account should be understood as an action within the documented WooCommerce Stripe account flow; it should not be presented as automatically changing every payment profile held by a separate wallet or payment service.
Tokenization Versus Storing Card Details on the WordPress Site
Tokenization changes what the WordPress site handles. Instead of storing raw card credentials for later use, the site uses a token or payment reference that points to payment data retained by the payment processor. The documented Stripe integration states that the full card number and CVC are not stored directly on the WordPress site.
What the site stores and what the processor retains
The payment processor retains the actual sensitive payment information. The store uses the tokenized reference when the customer chooses the saved method for a later payment. WooCommerce documentation also explains that a token can be associated with limited identifying details, such as the last four digits, card brand, and expiration date. These details help customers recognize which saved method they are selecting, but they are not the full card credentials.
Tokenization is therefore different from keeping card numbers and CVC values in the WordPress database. It reduces the need for the site to handle raw payment data, but it is not a complete security guarantee. The WordPress installation, administrator accounts, checkout, extensions, themes, hosting environment, and gateway configuration still require appropriate protection and maintenance.
It is also important not to describe tokenization as automatic PCI compliance. Applicable requirements depend on the payment flow, gateway configuration, merchant setup, and jurisdiction. Merchants should review the requirements relevant to their own store rather than assuming that the tokenized architecture eliminates every responsibility.
Which Payment Methods Can Be Saved in the Documented Stripe Integration
The documented Stripe for WooCommerce integration lists a defined group of payment methods that can be saved to a customer account. This list should not be confused with every payment method visible in the Stripe Dashboard. The extension supports only a subset of Stripe’s broader catalogue, and availability can depend on the merchant’s configuration and eligibility.
Documented savable methods and scope limitations
The documented savable methods include:
- Credit and debit cards.
- ACH.
- BACS during checkout only.
- Bancontact.
- BECS.
- Canada PADs.
- iDEAL | Wero.
- SEPA Direct Debit.
BACS is specifically identified as available for saving during checkout only. The presence of a method in the documented list still does not guarantee that it will appear for every merchant or customer. Country, currency, account eligibility, product type, payment-method rules, and the specific checkout flow can affect availability. Adaptive Pricing can also make some methods unavailable for saving, although previously saved methods may still be usable in some cases.
Troubleshooting, Production Checks, and Responsible Use
A missing save option should be investigated through the actual store configuration rather than assumed to be a general Stripe limitation. The documented feature depends on account settings, the selected payment method, checkout behavior, and the interaction between WooCommerce and Stripe settings.
A diagnostic order for missing save options
- Check whether the customer is logged in or whether the store allows account creation.
- Review the saved-payment setting in the Stripe configuration.
- Check whether Link is enabled and may be providing a separate saving flow.
- Review whether Adaptive Pricing affects the selected payment method.
- Verify the customer’s country, the transaction currency, and payment-method eligibility.
- Test the method in the checkout configuration used by the store, preferably in a staging or test environment.
Do not infer support from the Stripe Dashboard alone. The documented WooCommerce extension supports a defined subset of methods, and individual availability can change with merchant, customer, product, currency, and gateway conditions.
Production security checklist
- Use HTTPS for the WooCommerce site and checkout.
- Keep WordPress, WooCommerce, the Stripe extension, themes, and security controls maintained.
- Protect WordPress administration and review the gateway’s security requirements.
- Confirm that the customer can add, view, remove, and set a default method from My Account.
- Validate the checkout and payment-method behavior before production rollout.
- Review applicable PCI, privacy, fraud-prevention, operational, and legal requirements for the store.
Saved payment methods are useful when the account flow, gateway settings, and customer expectations are clear. Tokenization means that the full card number and CVC are not stored directly on the WordPress site according to the documentation, but it does not make the store risk-free or remove general security responsibilities.
In summary, WooCommerce saved payment methods with the documented Stripe integration require an account-based customer journey, an enabled setting in the Stripe configuration, and a checkout that supports the selected method. Customers manage saved methods under My Account > Payment Methods, where they can add, view, remove, and set a default method. Tokenization keeps sensitive payment data with the processor while the site uses a token or reference. The documented savable methods include cards, ACH, BACS during checkout only, Bancontact, BECS, Canada PADs, iDEAL | Wero, and SEPA Direct Debit, subject to configuration and eligibility. Explore our WordPress plugins, WooCommerce extensions, themes and membership plans to find the right tools for your website.