feat: unified view for saved and more payment methods screen

[sakksham7]

Type of Change

• Bugfix
• New feature
• Enhancement
• Refactoring
• Dependency updates
• Documentation
• CI/CD

Description

#1193

Added a parameter inside layout object, named as mergeSavedMethods, it is an object having structure as

mergeSavedMethods : {
      isMergedSavedMethodsList: bool,
      maxSavedItems: int,
    },

based upon which if there are saved payment methods and isMergedSavedMethodsList is passed as true then instead of coming on a separate saved payment methods screen, it will come in either tabs flow or accordion flow depending upon the layout.
maxSavedItems is used to configure how many saved methods we want to show initially and then the rest can be shown after clicking on show more.

Screen.Recording.2025-08-26.at.4.47.04.PM.mov

How did you test it?

Tested the following cases for both Accordion view and Tabs View :-

• When saved payment methods are present

• displaySavedPaymentMethods is false, isMergedSavedMethodsList is false or true No saved payment methods tab

• displaySavedPaymentMethods is true, isMergedSavedMethodsList is false Normal flow Saved payment methods screen

• displaySavedPaymentMethods is true, isMergedSavedMethodsList is true Saved payment methods in tabs or accordion

• When No saved payment methods are present

• each case will have no saved payment methods

Checklist

• I ran npm run re:build
• I reviewed submitted code
• I added unit tests for my changes where possible

[semanticdiff-com]

Review changes with  

[vsrivatsa-edinburgh]

Hmm. Quite confusing experience. If “Saved” implies all (saved) payment methods, why should it have a card icon. Right next it to is “Cards” with a card icon again. Worth revisiting

[sakksham7]

Hmm. Quite confusing experience. If “Saved” implies all (saved) payment methods, why should it have a card icon. Right next it to is “Cards” with a card icon again. Worth revisiting

Thanks for pointing this out, we’ll revisit the icons.