feat: added hiddenPaymentMethods customization prop

[ArushKapoorJuspay]

Type of Change

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

Description

Adds a new hiddenPaymentMethods prop inside savedMethodCustomization that allows merchants to filter out specific payment methods from the SavedMethods section only. The new payment methods list is unaffected.

Changes

• src/Types/PaymentType.res
  • Added hiddenPaymentMethods: array<string> field to the savedMethodCustomization type
  • Added hiddenPaymentMethods: [] to defaultSavedMethodCustomization
  • Added "hiddenPaymentMethods" to unknownKeysWarning to avoid spurious console warnings
  • Parsed the new field in getSavedMethodCustomization using getStrArray
• src/Utilities/PaymentUtils.res
  • Added filterSavedMethodsByHiddenList utility function
  • Applied filter at both saved-methods pipeline call sites (standard + grouped)
  • Added hiddenPaymentMethods to useMemo dependency array in useGetPaymentMethodList
• src/PaymentElement.res
  • Chained filterSavedMethodsByHiddenList before filterSavedMethodsByWalletReadiness in the saved methods useEffect pipeline
  • Added hiddenPaymentMethods to the useEffect dependency array
  • Removed redundant Array.copy (dead code since Array.filter returns a new array)

Behaviour

Input	Result
["apple_pay"]	Hides saved Apple Pay entries
["google_pay"]	Hides saved Google Pay entries
["card"]	Hides all saved cards (credit + debit)
["google_pay", "card"]	Hides saved Google Pay and all saved cards
["wallet"]	No effect — silently ignored
[] / omitted	No filtering, existing behaviour preserved

Notes

• Filter runs before filterSavedMethodsByWalletReadiness so merchant intent takes priority
• Matching is case-insensitive
• ["wallet"] is explicitly not supported — merchants must pass specific method names like "apple_pay" or "google_pay"

How did you test it?

Passing all these payment_methods in the prop one by one to verify whether that payment method has been removed or not

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  

[github-actions]

🚫 Missing Linked Issue

Hi 👋 This pull request does not appear to be linked to any open issue yet.

Linking your PR to an issue helps keep the project tidy and ensures the issue is closed automatically.

✔️ How to fix this

• Add a keyword like Fixes #123 or Closes #456 to your PR description or a commit message.
• Or link it manually using the "Linked issues" panel in the PR sidebar.

✅ Tip: You can link multiple issues.
🚫 Note: If only one issue is linked, it must be open for this check to pass.

Once linked, this check will pass automatically on your next push or when you re-run the workflow.

Thanks for helping maintainers! 🙌