feat: added hidden payment methods for headless

[ArushKapoorJuspay]

Type of Change

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

Description

Adds a hiddenPaymentMethods prop that allows merchants to filter out specific saved payment methods. Supported in both the embedded (PaymentElement) and headless (PaymentSession) flows.

Changes

• src/hyper-loader/Types.res
  • Changed getCustomerSavedPaymentMethods type from unit => promise<JSON.t> to option<JSON.t> => promise<JSON.t>
  • Updated defaultGetCustomerSavedPaymentMethods stub to accept optional param
• src/hyper-loader/PaymentSession.res
  • Forwards call-time options argument to PaymentSessionMethods
• src/hyper-loader/PaymentSessionMethods.res
  • Added ~options: option<JSON.t> parameter; parses hiddenPaymentMethods internally
  • Applied filterSavedMethodsByHiddenList on customerPaymentMethodsRef after initial sort
  • isApplePayPresent, isGooglePayPresent, and customerDefaultPaymentMethodRef all derived from the filtered list
  • Removed stale debug Console.log2

Filter Logic

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

Backwards Compatibility

• Embedded flow: omitting hiddenPaymentMethods preserves existing behaviour
• Headless flow: getCustomerSavedPaymentMethods() with no argument → no filtering

How did you test it?

Checked the customers call list response after passing hiddenPaymentMethods prop

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! 🙌