#Sergei P.

1 messages · Page 1 of 1 (latest)

idle idolBOT
void blade
#

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).

chilly wyvern
#

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.

chilly wyvern
void blade
#

e.g. collect the card details, and then check the brand before confirming the payment

chilly wyvern
#

As I can see, it will happen on the server side, right?

void blade
#

What will happen server-side?

chilly wyvern
#

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.

void blade
#

And then you can re-prompt them to re-enter details

#

stripePaymentMethodHandler inside that function

chilly wyvern
#

Great, thanks, I'll try

void blade
#

You can't intercept the updatePaymentIntent call, and anything after that you risk the checkout flow becoming weird

void blade