#livermorebill_api
1 messages ¡ Page 1 of 1 (latest)
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
đ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1230789522921361478
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
hi
hi! it can be possible to implement, you'd need to check the fingerprint of the PaymentMethod the user enters and compare it to a list of other fingerprints you've saved.
https://support.stripe.com/questions/how-can-i-detect-duplicate-cards-or-bank-accounts
I guess what I need is to intercept the payment before it's made.
Can fingerprints do it?
yes, it's possible, it really depends how exactly you've integrated and the means and API calls you use to collect the customer's card details.
I found a new feature rule https://docs.stripe.com/radar/rules/supported-attributes#customers in the official docs, is there any way to implement it through that?
I don't think that's really the same concept no
For example, my rule is that after a certain bank card has purchased a subscription with a trial more than 10 times, the next time he purchases it he is not allowed to purchase it anymore
makes sense, but that's not something that's possible to express in Radar rules as far as I'm aware.
Can fingerprints do it?
yep
Create User -> Create Subscription -> Get Payment Connection -> Connection Provided to User
This is the processing flow in my project
So what part of the process do I need to add fingerprinting judgments to
possibly the "Get payment connection" part? I'm not sure, that's super highlevel.
do you have some specific details like exact code you wrote and API calls you make and how you frontend collects the payment details?
are you using Checkout in mode:"subscription"?
yes
then unfortunately it's not really possible to easily implement this sort of thing since you don't have a way to see the fingerprint during the Checkout page; you could only act on it after (for example cancel the user's subscription and contact them to explain why, when handling the Checkout completed webhook if you detect the card fingerprint they entered was one you know already).
Alternativel you'd need to use a more custom flow using Elements where you can more directly interact with the payment flow but that's a lot of work
What does a customized process look like
along the lines of https://docs.stripe.com/payments/accept-a-payment-deferred?platform=web&type=subscription but there's more to it which is not really documented well, for example you'd need to call https://docs.stripe.com/js/payment_methods/create_payment_method on the frontend so you can get the card object and look at its details like fingerprint before using it