Stripe Identity

[dbartenstein]

Hi!

Are there any plans to support Stripe Identity?

P.S.: Happy 2022 🍀 to the whole dj-stripe team and thanks for your great work 👏!

[jleclanche]

Hi Dominik, happy 2022 :)

Yes it's possible, though it's been low priority so far. I can make sure at least the models end up in 2.7 though.

[dbartenstein]

Hi Dominik, happy 2022 :)

Yes it's possible, though it's been low priority so far. I can make sure at least the models end up in 2.7 though.

Hi Jerome,

thanks for your swift reply! 🙇

As Stripe Identity is not yet available in most European countries, priority is not that high. But we hope that Stripe Identity will become available in the first quarter 2022. It looks promising.

[jleclanche]

I'm not informed on it at all, so take this as personal opinion, but I don't think it will be available in Europe particularly soon. Maybe by the end of the year if lucky.

[dbartenstein]

I'm not informed on it at all, so take this as personal opinion, but I don't think it will be available in Europe particularly soon. Maybe by the end of the year if lucky.

Hmm, that would be too late for us as we want to have a solution no later than Q2/2022. We were already approached by several companies which provide ID verification services. I have just sent another email to Stripe support asking them for an ETA. Let’s see - I still believe in miracles 🪄 ;-)

[dbartenstein]

Hi @jleclanche and @arnav13081994,

as Stripe identity is now available in Europe, we’d like to see Stripe identity supported by dj-stripe. What’s your take on this?

Best,
Dominik

[jleclanche]

Hey Dominik. As I mentioned on the Slack channel, this is something we'll plan to do and prioritize but I don't think we will have it done quickly, as it's a significant piece of work.

[jleclanche]

Please test 2.8.0a1

[dbartenstein]

Hi @jleclanche,
we have been using Stripe Identity with djstripe for some months now and it works well! 👏

We noticed that some document fields are not expanded by default:

• dob
• expiration_date
  https://docs.stripe.com/api/identity/verification_reports/object#identity_verification_report_object-document

Would it make sense to set expand_fields = ["document.dob", "document.expiration_date"] for VerificationReport in general?

[jleclanche]

Yes makes sense. We can add this.

[jleclanche]

I've done this and cherry-picked it for 2.8.4, but we don't have any plans for when to release 2.8.4 yet.

[dbartenstein]

I've done this and cherry-picked it for 2.8.4, but we don't have any plans for when to release 2.8.4 yet.

Thanks @jleclanche - would be great to have the release 2.8.4 in the next weeks. Would that be feasible?

Btw, it would also make sense to include document.number in the expand_fields list.

[jleclanche]

Yes, I can make sure we do a release next week or so.

[dbartenstein]

@jleclanche what I also found is that the client_reference_id seems to be missing for VerificationSession:
https://docs.stripe.com/api/identity/verification_sessions/create#create_identity_verification_session-client_reference_id

Btw, would you prefer that I create separate issues or is a discussion here fine with you?

[jleclanche]

Please create individual issues so we can track them for 3.0. Thank you!

[dbartenstein]

@jleclanche thanks a lot for dj-stripe 2.8.4!

We just found out:
"stripe.error.PermissionError: Request req_SdXDpPDGU9Csib: To access sensitive verification results, configure a restricted API key with appropriate permissions. Learn more here: https://stripe.com/docs/identity/access-verification-results"

Therefore the webhook event processing failed:

  File "/home/zemtu/django-env-py3.11/lib/python3.11/site-packages/django/db/models/query.py", line 637, in get
    raise self.model.DoesNotExist(
djstripe.models.identity.VerificationReport.DoesNotExist: VerificationReport matching query does not exist.

document.dob and document.expiration_date require restricted API keys to have access.

@jleclanche
What’s the best way forward here? I assume by default dj-stripe should not require restricted API keys?

[jleclanche]

Yikes. I don't know what the best way forward here is. I guess I will be removing those from the minor release.
I need to think about how to really solve this, but to address your use case you will have to specify these in the API call to force expand them, and add a restricted key in your database for it.

[dbartenstein]

Yikes. I don't know what the best way forward here is. I guess I will be removing those from the minor release. I need to think about how to really solve this, but to address your use case you will have to specify these in the API call to force expand them, and add a restricted key in your database for it.

Jep, I also propose removing it from the minor release.