#VanessaD
heavy trout
strong salmon
so for example, if I have a customer who wants to pay with amex, and I don't want to accept amex, there is no way to do that ?
unreal cradle
you can use Stripe Radar to block certain card brands which is the best solution
but you can also take a look at this example https://glitch.com/~stripe-block-amex
what I was saying about brand blocking not being available is more related to configuring the PaymentIntent not to accept certain brands of cards
both of these solutions means that the customer will confirm the card payment first and then we would have to do a verification of the card brand (either with Radar or from your backend logic) instead of being automatically blocked on the front-end
strong salmon
Are these approach possible with usage based subscription ? I mean that when the customer enters their card information, he is not charged directly but at the end of the billing cycle
unreal cradle
I think if you're using Radar yes, since if you're setting up a Payment Method for future usage we tried to authorize the card for $0 which will fail with the Radar rule
strong salmon
I tried but it's not working, maybe it's not possible with platform in India ?
unreal cradle
mmm I'm not sure
India has very specific rules and regulations
I think you can write to https://support.stripe.com/?contact=true for more accurate response on the India regulations there
strong salmon
ok thanks and about the second option the glitch link, all the logic is made in the front-end and not in the back-end ?
unreal cradle
no actually the back code is also included there
strong salmon
yes but there is just the creation of the paymentint, nothing to block the payment on the server side ?
unreal cradle
oh sorry my bad, you're right, in the Readme of the glitch there's a description of how to implement the blocking with a manual confirmation process
strong salmon
no problem, thanks!
I tried with another platform in Europe and Radar FFT does not block the amex card with subscription usage based without charging
hot marten
there's a toggle in the Dashboard settings somewhere to run custom Radar rules on SetupIntents, which is what you probably need if you want to block a card from being saved if it's not being charged. ; https://dashboard.stripe.com/test/settings/radar
strong salmon
it's not working in my case because I don't have setup_intent
hot marten
hmm, hard to say really without looking at some specific examples!
strong salmon
I tried with this Stripe sample https://github.com/stripe-samples/subscription-use-cases/tree/main/usage-based-subscriptions
hot marten
yeah that's a really old-style sample, so it doesn't quite check the card details with a SetupIntent when attaching them to a Customer for a Subscription, so indeed there is no opportunity for any custom rules to be run
strong salmon
ok so this one will be better https://github.com/stripe-samples/subscriptions-with-card-and-direct-debit
hot marten
I believe so
strong salmon
ok I will try, thanks
light fjord
Hey, taking over here. Let me know if there's any follow-up Qs I can answer!