Saved Payment Methods Panel

About this block

Saved Payment Methods Panel lists three cards as ruled rows: brand, last four digits, expiry, a default tag, and a delete link. The lede states the architecture plainly: “Every row here is a token at the payment processor. We never saw the full number, so there is no full number here to steal.” The delete footer adds: the processor token dies with the row, no archive, no undo, the next checkout simply asks for the card again. The bottom note closes the consent loop: cards land here only when the save box is ticked at checkout, never saved silently.

Cards are one array of three rows. The token explanation and the no silent save footer are the two trust mechanisms; the panel without them is a plain card list.

When to use

Reach for this block on the account payment tab inside the account section. The delete action must wire to the processor token removal endpoint in production, the text makes a promise the backend must keep or the copy misleads.

A natural flow around it on an Ecommerce Pro page:

Before

• Account overview

After

• Checkouts
• Contact routes

What you can display

One strong use is the three card wallet with the token explanation. Other saved methods panels:

• Single card. The minimal one row state with the same footer copy and the add prompt prominent.
• With PayPal. A mixed methods list adding a non card row and its own separate token note.
• Empty state. No saved cards yet, the add prompt and the save box reminder as the only content.

Tip: the no silent save footer is the consent signal buyers increasingly expect; it belongs on every store running saved cards.