esset | Stripe Developers | Page 1

thin hillBOT Jan 25, 2023, 7:28 AM

#

tough garnet Jan 25, 2023, 7:28 AM

#

Hi! Can you share the request ID (req_xxx)? Here's how you can find it: https://support.stripe.com/questions/finding-the-id-for-an-api-request

Finding the ID for an API Request : Stripe: Help & Support

Find help and support for Stripe. Our support center provides answers on all types of situations, including account information, charges and refunds, and subscriptions information. Get your questions answered and find international support for Stripe.

plain bough Jan 25, 2023, 7:28 AM

#

Sure, req_2w1flGDHEUeHYb

#

sorry wrong request id

#

hang on

#

oh never mind! it was the right one: req_2w1flGDHEUeHYb

#

my bad.

tough garnet Jan 25, 2023, 7:35 AM

#

No problem. There's no public information available in Stripe's doc that tells what information Stripe uses to determine if the person is identical to another.

#

Are you use that the information you passed to create a person is unique?

plain bough Jan 25, 2023, 7:36 AM

#

OK, is there a good way of identifying this specific error (like an error code) and handle it?

#

In this specific case, the information is almost unique. We're doing onboarding via API, and the user has provided themselves a both beneficial owner + representative. However, there's 1 digit in their SSN that differs (mistyped) between the two persons.

Essentially, the data is "bad", so we'd need a good way to (1) avoid it or (2) recover from the scenario (we have limited control over the data since it's coming from KYC in a separate system that we're using; our bank provider)

tough garnet Jan 25, 2023, 7:40 AM

#

There's no dedicated error code for this kind of error I'm afraid.

plain bough Jan 25, 2023, 7:42 AM

#

OK. I guess we could provide less information about the owner (name + email is the only ones required) to reduce the risk of conflict

#esset