#jackson_connect-verification-missingenum
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/1263912663638081590
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hi ๐
Unfortunately I cannot see the response for your GET request. I do see the Verification Record has a status of unverified though
PRODUCTION :060 > vr = Stripe::Identity::VerificationReport.retrieve('vr_1PWmfOCXdfp1jQhWdx3LkIDb', StripeAccount.platform_account.options)
=>
#<Stripe::Identity::VerificationReport:0x375adc id=vr_1PWmfOCXdfp1jQhWdx3LkIDb> JSON: {
...
PRODUCTION :061 > vr.selfie.status
=> "processing"
The value is returning a string that is not in the enum set.
@mortal wyvern Are you able to retrieve it on your side?
Retrieve what? As I said, I'm looking at the VerificationRecord and I'm not seeing what you are describing
Are you looking at the verificaiton session or the verificaiton report?
@mortal wyvern if you CURL it what does it show in the response body for you?
It won't show me anything because this isn't an object that belongs to me
Oh I thought dev support had a global admin API key or something
No, that would be massively insecure
We can view these objects internally but we cannot make API requests on your behalf
{
"id": "vr_1PWmfOCXdfp1jQhWdx3LkIDb",
"object": "identity.verification_report",
"client_reference_id": null,
"created": 1719611354,
"document": {
"address": null,
"error": {
"code": "document_type_not_supported",
"reason": "The document type is not one of the allowed document types."
},
"files": [
"file_1PWmehCXdfp1jQhWeVjxMLDH",
"file_1PWmetCXdfp1jQhWIi7PGJCj"
],
"first_name": "[redacted]",
"issued_date": {
"day": 1,
"month": 1,
"year": 1
},
"issuing_country": "IN",
"last_name": null,
"status": "unverified",
"type": "id_card"
},
"livemode": true,
"options": {
"document": {
"require_live_capture": true,
"require_matching_selfie": true
},
"email": {},
"id_number": {},
"phone": {}
},
"selfie": {
"document": "file_1PWmehCXdfp1jQhWeVjxMLDH",
"error": null,
"selfie": "file_1PWmfHCXdfp1jQhWkJFRRIxe",
"status": "processing"
},
"type": "document",
"verification_session": "vs_1PWmdgCXdfp1jQhWQjtQUYgZ"
}
Is this the same object that you see on your side?
No but let me check some of these other IDs
Also I've never heard of VerificationRecord I dont see that listed anywhere in the docs
is this something internal only on Stripe side you are mentioning?
Unfortunately, sometimes we don't name things consistently across the API and internal models.
Apologies for any confusion
no problem makes sense
Okay I see a different internal status for the selfie but it amounts to the same thing. I will flag this internally to get the status enum documentation updated.
yeah the issue is the docs say that this value can only be verified or unverified but now its coming back as processing on the API response
And if you built your integration logic based on thes enums that would cause problems so we should document all possible outcomes
exactly
Okay, feedback filed!
Happy to help ๐