#anthonyamar_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/1269992126528098371
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
I provided a related request ID because it was needed, but I don't have one real since I don't find the right API endpoint
Not sure I understand your ask?
Make this flow, but using the API, to prevent people from submiting two times the same Identities, both from selfies and document
Because people are signing up with multiple different account, but still the same document, and fraud us using promotion coupons normally created to be used for new customer only.
Would help if you initial message included the phrase block instead of just list. Now it's a little clearer
Yes sorry, I was meaning Block list, just like Radar For Teams block lists for emails, customer, IP...
The dashboard says "Add to list" by the way
And big thanks for answering that fast!
Nope, doesn't seem possible via the API I'm afraid: https://docs.stripe.com/identity/review-tools#block-list
Will relay the feedback!
Ok. Are we able to link (like relationship link) customer to an identity? Right now, it's only an email that represent the Identity. If I can relate a customer and its Identity, maybe I can make a script to check uniqueness of document?
You'd have to utilise metadata on either/both objects
Ok good thing, I can do that!
No way it can be set by default to: not accept twice the same identity?
Or any way we can store these ID after we get the verification_report, so we can block using uniqueness also?
Assuming that these ID are the same if two identical selfies and documents are submitted. (is this true?)
No, the idpbe_xxx isn't unique per document/ID
Erf. Is there any data that is unique per document and that we can get either/both through verification session or verification report? Not the email obviously, too easy to fraud
Well the verified_outputs hash (https://docs.stripe.com/api/identity/verification_sessions/object?identity_verification_session_object-verified_outputs) includes the ID details on a verified session so perhaps you can use those to have an internal blocklist?
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
Hum, great catch, maybe with a strict or nearly strict comparaison algorithm on each field to determine a chance of similarity, it can works fine for now! Thanks!
Identity is a great product, although it lacks some anti-fraud features like this to really use it at its full potential. We used it since a year or so right now, no problems at all, just some limitations! Hope it will be upgraded!
I've captured your feedback and will share with the Identity team, ty!