#battbot-terminal-inspectpm
merry brook
What kind of integration have you built? Server-driven? A flow using one of our mobile sdks?
barren boughBOT
battbot-terminal-inspectpm
barren boughBOT
merry brook
Gotcha - if you're using the server-driven flow there's a beta that'll help with that (if you click on the "Collect, inspect, and confirm" tab at https://docs.stripe.com/terminal/payments/collect-payment?terminal-sdk-platform=server-driven&process=#process-payment you'll see more details)
You'll need to write into support to see if you're eligible, but essentially you'd write your own logic to inspect the payment method that's presented and then choose to continue with confirmation or not
radiant grove
but it seems like i only reject it by not capturing it
the Stripe Reader itself will still show successful though
that will result in confusion for the user
merry brook
No, if you look at the link I sent you the beta flow would be different. Collecting the PM and confirming the intent would be two separate calls, and you just wouldn't confirm if it's a brand you don't want
radiant grove
would it result in the reader showing failed transaction to the user?
do you have a method where it can be specified as parameters to the payment intent what type of card is allowed?
crisp mural
Hi 👋
I'm jumping in as my colleague needs to go.
crisp mural
The beta does not allow you to specify a card brand up front.
You would need to cancel the Payment Intent and return some sort of informative message to your POS .
radiant grove
we have some merchants that wants to disallow credits cards
and some merchants that wants to disallow AMEX
right now the only thing stripe allows is disabling card brands on the platform level, which we don't want to do
we really want flexibility per transaction what type of card we allow
this also goes for our online transactions as well as in store terminal transactions
crisp mural
In that case you should reach out to stripe-terminal-betas@stripe.com to inquire about the beta. It would allow you to customize this handling in your server-side code.