Documentation
BETA

Stored Payment Methods

Learn how to use Stored Payment Methods in Checkout.

Copy for LLM
View as Markdown

Stored Payment Methods let your customers securely store their card details during Checkout and reuse them for future purchases. This creates a faster and frictionless Checkout experience, reducing cart abandonment and improving conversion rates.

After saving their card details, when customers proceed to the checkout page, the stored card's brand and last four digits are automatically displayed and it's preselected to make the checkout even faster. Customers can store multiple cards and delete them directly during the checkout. If they remove all cards, the payment form resets to its initial default state.

How Stored Payment Methods work

Stored Payment Methods use the Payment Methods API by attaching a customer and Payment Connector to each stored PaymentMethod:
  • Customer: saved as the customer resource on the Payment Methods API. This value comes from the customerId attribute on the Cart. This value is used to determine which Stored Payment Methods belong to which customer and it is your responsibility to ensure the correct customerID value is set before Checkout is initialized. Therefore, the customer must already exist in Composable Commerce before they can use Stored Payment Methods.
  • Payment Connector: saved as the paymentInterface and, optionally, the interfaceAccount attributes on the PaymentMethod. These values are defined by the Payment Connector and set as regular environment attributes when deploying it.
Each Payment Connector that supports Stored Payment Methods must ensure that the PaymentMethods are up to date and created correctly.
A customer can have multiple Stored Payment Methods. The value attribute in the PaymentMethodToken represents the actual value required by each PSP to pay with a Stored Payment Method.