#Sergei P.
1 messages · Page 1 of 1 (latest)
We're using a Beta features of Stripe Payment Elements
Which beta features?
The user shouldn't see AMEX or VISA icon at all when they open our payment page
AFAIK, that's not possible with any of the Elements right now (e.g. hiding specific brands).
I cannot say what exact beta features we are able to use (if there are some), but what I know is that the Stripe account for our company was added to the Beta program (or something like this) so if needed we can use any Beta feature which exists at all. Even if we are not able to use it now, we can ask Stripe to allow us to use it.
If it is possible to deny the user to proceed with the card number refers to some restricted card brands, it is ok to still show some icons
There's no beta feature to restrict to specific brands on the Element directly, you'd need to do it manually using this flow (which is a beta): https://stripe.com/docs/payments/run-custom-actions-before-confirmation
e.g. collect the card details, and then check the brand before confirming the payment
As I can see, it will happen on the server side, right?
What will happen server-side?
These custom actions which we need to implement manually, they will integrate into the flow in the server side, not frontend, right? So, the user enters a card number, clicks "Pay", then the request is sent to the server and then we can process some custom logic to deny it in case if card brand is restricted.
No, I think you'd check the brand of the attached PM in your client-side handler here: https://stripe.com/docs/payments/run-custom-actions-before-confirmation#payment-method-details
And then you can re-prompt them to re-enter details
stripePaymentMethodHandler inside that function
Great, thanks, I'll try
You can't intercept the updatePaymentIntent call, and anything after that you risk the checkout flow becoming weird
Well your account needs to be gated to the beta. Is it?