#kayzer-paymentmethod-choice
1 messages · Page 1 of 1 (latest)
kayzer-paymentmethod-choice
Hey @hardy vortex ! You should be able to control the exact payment method type(s) that you want to accept so yes.
unless you mean debit cards and not debit payment methods
so debit card could be a part of these payment methods
okay, let's take a step back. What integration path are you using exactly?
i give you more context
it's a US customer who has some strict regulation on the accepted payment methods, so they would like to accept only debit one
What integration path are you using exactly?
Which product are you using? There are numerous way to integrate. But really Radar will be the only viable path for accepting debit card and rejecting credit cards
radar for fraud teams is not used here
then that's not really doable
so we have to collect the payment details first, check if it's credit or debit type and they act on that
but collecting that's doable only with elements
Are you accepting only card payments? If not, what else do you plan to accept?
that's the deal i have, i would like to use Payment Element
to accept different payment methods
what other payment methods? Please be clear and detailed and thorough
but i think ACH, and LPM
but what LPMs? Please be clear, and detailed and thorough
like you said "debits". Is iDEAL debits? I don't really grasp what that could mean so I'm asking if you can try and provide a lot more information so that I can help you
US lpm's he did'nt precise
Okay so I guess you mostly want to block credit cards and nothing else?
they want also to accept prepaid cards, im not sure of how this PM works, if it's debits or credits
All cards are a card PaymentMethod. Debit cards, credit cards, prepaid cards, Apple Pay, Google Pay, etc.
Sorry, it's really tricky to help when the ask isn't clear and I still don't really grasp your ask after all this back and forth.
Are you simply trying to block credit cards? If not, what else are you doing? Please try to write a clear summary, in one message, with multiple sentences if need be. I really need to be able to understand what you are doing
the customer was not clear on the exact payment methods they want to accept, they want only reject all credit payment methods.it would be simple to me if it's only around debit cards, i know the flow i will to adopt, it's the fact that it could be different payment methods who add the complexity
yeah unfortunately you can not what you are after if you want to do many payment methods and block credit cards specifically. In that case the only way is to use Radar for Fraud Teams. So you need to tell that to your customer, no way around it
yes thanks
If your customer only accepts cards it's different. You could use the legacy CardElement https://stripe.com/docs/payments/card-element
this lets you create a PaymentMethod first and then check whether it's a credit card or not before confirming the payment
Alternatively, you could ask for access to our current beta documented here: https://stripe.com/docs/payments/run-custom-actions-before-confirmation
This would let you confirm the card is a debit card before confirming the PaymentIntent server-side
it's a bit more convoluted but it would work too
ok nice to know
i will double check with the customer, in terms of the accepted payment methods
Sounds good!
thanks for the help
of course!