Use this file to discover all available pages before exploring further.
A CoworkerIdentityCheck represents a manual or Stripe Identity-based verification of a customer’s identity or address. Each check is linked to a Coworker and a Business (location).The VerificationType determines the nature of the check:
VerificationType
Purpose
IdDocument (1)
Verifies the customer’s identity using an official document (passport, driver’s license, ID card, etc.)
Address (2)
Verifies the customer’s address using a supporting document (lease agreement, insurance policy, voter card, etc.)
When VerificationType is IdDocument, use IdentityDocumentType to specify the document kind, along with IdentityDocumentNumber, IdentityDocumentIssuedBy, and IdentityDocumentExpirationDate. When VerificationType is Address, use AddressDocumentType instead.IdentityCheckProvider controls how the check is performed: Manual (1) means the operator reviews documents directly, while StripeIdentity (2) delegates verification to Stripe Identity.The VerificationStatus tracks progress through the check lifecycle: Pending → Submitted → Successful or Failed (or Cancelled).
This endpoint requires OAuth2 authentication. Include a valid bearer token in the Authorization header.
The authenticated user must be a full unrestricted administrator or have the CoworkerIdentityCheck-List role.
The list of CoworkerIdentityCheck records matching the query. See the Get one CoworkerIdentityCheck endpoint for the full list of properties returned for each record.
Partial records — The listing endpoint returns a summary representation of each CoworkerIdentityCheck. The following fields are not populated in the Records[] response: Description, IdentityCheckProvider1, VerificationType1, Description1, IdentityCheckProvider2, VerificationType2, Description2.To get all fields, fetch the full record using the Get one CoworkerIdentityCheck endpoint.Important for updates: When updating a record via PUT, always retrieve the full record with a GET request first, apply your changes to that complete data, and then send the updated record. Do not use data from a listing response as the base for a PUT request, as missing fields may be unintentionally cleared.