cardBrandAcceptance with Allowed filter, bypasses 'Select payment method' within the payment sheet

[realkrutosh]

Describe the bug

I have customer card details saved, where the card issuer is Visa. I want to restrict the payment brands to only Visa and Mastercard using the following configuration in initPaymentSheet:

cardBrandAcceptance: {
  filter: CardBrandAcceptanceFilter.Allowed,
  brands: [CardBrandCategory.Visa, CardBrandCategory.Mastercard],
},

With this configuration enabled, the saved Visa card no longer appears in the Payment Sheet. However, once the configuration is removed, the saved card reappears and can be used normally.

This suggests that the filter is incorrectly excluding saved cards, even when they match the allowed brand criteria.

Expected behavior

If a saved customer card matches the filter criteria (e.g., Visa or Mastercard), the Payment Sheet should still display it in the payment method selection UI.

Steps to reproduce

1. Save a Visa card to a customer profile.
2. Initialise the Payment Sheet with the cardBrandAcceptance filter set to allow only Visa and Mastercard.
3. Open the Payment Sheet.
4. Observe that the saved Visa card is ignored and payment sheet shows Add card UI
5. Remove the filter configuration.
6. Open the Payment Sheet again.
7. Observe that the saved Visa card now appears.

Smartphone (please complete the following information):

• Device: All
• OS: All
• Version: All

Additional information

🕵🏻‍♂️ Although, if the cardBrandAcceptance configuration is set to disallow the listed brand categories. The flow matches the expected outcome.

cardBrandAcceptance: {
    filter: CardBrandAcceptanceFilter.Disallowed,
    brands: [CardBrandCategory.Amex, CardBrandCategory.Discover],
},

[porter-stripe]

Hi @realkrutosh thanks for sharing this. Would this card happen to be a co-branded card? Do you see the same behavior with Mastercard? I'm not able to repro on my side but going to try a few more cases.

[realkrutosh]

Hi @realkrutosh thanks for sharing this. Would this card happen to be a co-branded card? Do you see the same behavior with Mastercard? I'm not able to repro on my side but going to try a few more cases.

It’s a Visa Card issued by one of the Big 4 banks in Australia. I can probably share a screen recording if that helps. Thanks again 🙏

[porter-stripe]

@realkrutosh, thank you for the context! I was able to reproduce your issue using test card number 4000050360000001, which is a co-branded eftpos Australia/Visa card.

The issue occurs because this card can be processed through eftpos Australia under the hood, so it doesn't appear after being saved. For users who need to support co-branded cards, I recommend using Disallowed instead of Allowed to work around this limitation. Allowed is filtering out this card because it could be eftpos Australia.

This behavior is confusing and not optimal. I'm going to initiate an internal discussion about how we can improve the handling of co-branded cards in the future.

[realkrutosh]

@realkrutosh, thank you for the context! I was able to reproduce your issue using test card number 4000050360000001, which is a co-branded eftpos Australia/Visa card.

The issue occurs because this card can be processed through eftpos Australia under the hood, so it doesn't appear after being saved. For users who need to support co-branded cards, I recommend using Disallowed instead of Allowed to work around this limitation. Allowed is filtering out this card because it could be eftpos Australia.

This behavior is confusing and not optimal. I'm going to initiate an internal discussion about how we can improve the handling of co-branded cards in the future.

That clears things up, thanks for looking into it. For now, I’ll go ahead with the workaround as you suggested. Cheers! Happy for us to keep this issue open until internal discussion results into either fix or won't fix (stick with workaround for now)?

Thanks again 🙏