identity-verification | Securely collect and verify identity documents | Identity Management library

You need to first upload the file to Stripe's API using the "create file upload" call. You can then use the file upload's ID (file_...) to update the account's legal_entity.verification.document attribute.

(This process is explained here:

• https://stripe.com/docs/connect/identity-verification#uploading-a-file
• https://stripe.com/docs/connect/identity-verification#attaching-the-file)

Since the file is provided by the user, you have two choices for creating the file upload:

• have your app upload the file to your backend server, then on your backend, use the file to create the file upload

• create the file upload directly from the app (using your publishable API key), and send the resulting file_upload's ID (file_...) to your backend

Here's an example for creating file uploads client-side, using jQuery: https://jsfiddle.net/captainapollo/d8yd3761/.

You could do the same thing from your iOS app's code. Basically all you need to do is send a POST request to https://uploads.stripe.com/v1/files with an Authorization header with value Bearer pk_... (where pk_... is your publishable API key) and type multipart/form-data, with the file's contents as the request's body. This blog post should be helpful for sending multipart/form-data requests using Swift: http://www.kaleidosblog.com/how-to-upload-images-using-swift-2-send-multipart-post-request

If the file on S3 is public, you could just pass the URL to Stripe:

Since the NuGet protocol does not really describe when a package should be "verified" when used outside of Nuget.org, we at MyGet now use the following convention:

• If a package originates from a MyGet feed, it is shown as "verified" (e.g. it comes from your feed)
• If a package is proxied from, e.g. NuGet.org, the package is never shown a verified as MyGet reaches out upstream to fetch the package and its not part of your feed yet. Additionally, since the V2 protocol does not expose the verified boolean, we can never show the verified label for upstream package sources.