Accéder directement au contenu
Créez un compte
ou
connecter-vous
Logo de la documentation Stripe
/
Demander à l'assistant IA
Créez un compte
Connectez-vous
Démarrer
Paiements
Revenus
Plateformes et places de marché
Gestion de fonds
Ressources pour les développeurs
AperçuDécouvrir tous les produits
Commencer à développer
Commencer le développement
À propos des API
Créer avec un LLM
Utiliser Stripe sans coder
Configurer Stripe
Créer un compte
Dashboard Web
Dashboard mobile
Migrer vers Stripe
Gérer le risque de fraude
Comprendre la fraude
Radar pour la protection contre la fraude
Gestion des litiges
Vérifier l'identité
    Présentation
    Démarrer
    Vérifier des pièces d'identité
    Gérer les résultats des vérifications
    Accéder aux résultats de vérification
    Réviser les résultats de vérification
    Flux de vérification
    Contrôles de vérification
    À propos des API
    Sessions de vérification
    Passer en production
    Avant de passer en mode production
    Cas d'usage pris en charge
    Identity en quelques mots
AccueilDémarrerVerify identities

Remarque

Cette page n'est pas encore disponible dans cette langue. Nous faisons tout notre possible pour proposer notre documentation dans davantage de langues et nous vous fournirons la version traduite dès qu'elle sera disponible.

Verification checks

Learn about the different verification checks supported by Stripe Identity.

Stripe Identity currently supports five types of verification checks: document, selfie, ID number, address, and phone.

Each verification check requires different information from your user, has different coverage, and has a different verification flow. After you’ve integrated one check, you can add another with minimal changes to your integration.

While document checks provide a defense against the use of fraudulent identity documents, it’s possible for fraudsters to get access to legitimate stolen documents. To prevent this, Stripe Identity can perform selfie checks on your users.

Selfie checks look for distinguishing biological traits, such as face geometry, from a photo ID and a picture of your user’s face. Stripe then uses advanced machine learning algorithms to ensure the face pictures belong to the same person.

In some places, such as the EU, there are privacy laws that require you to justify your use of biometric technology or offer an alternative, non-biometric means of verification. We recommend you offer an alternative verification option or consult with your legal counsel.

Availability

Selfie checks are available for government issued photo IDs from the following countries:

Afrique du Sud
Albanie
Algérie
Allemagne
Arabie saoudite
Argentine
Arménie
Australie
Autriche
Azerbaïdjan
Bahamas
Bahreïn
Bangladesh
Belgique
Bénin
Biélorussie
Bolivie
Brésil
Bulgarie
Cameroun
Canada
Chili
Chine
Chypre
Colombie
Corée du Sud
Costa Rica
Côte d’Ivoire
Croatie
Danemark
Égypte
Émirats arabes unis
Équateur
Espagne
Estonie
États-Unis
Finlande
France
Géorgie
Ghana
Grèce
Guatemala
Haïti
Honduras
Hong Kong
Hongrie
Inde
Indonésie
Irak
Irlande
Israël
Italie
Jamaïque
Japon
Jersey
Jordanie
Kazakhstan
Kenya
Koweït
Lettonie
Liban
Liechtenstein
Lituanie
Luxembourg
Macédoine du Nord
Malaisie
Malte
Maroc
Maurice
Mexique
Moldavie
Mongolie
Myanmar (Birmanie)
Népal
Nigéria
Norvège
Nouvelle-Zélande
Ouganda
Ouzbékistan
Pakistan
Panama
Paraguay
Pays-Bas
Pérou
Philippines
Pologne
Porto Rico
Portugal
République dominicaine
République tchèque
Roumanie
Royaume-Uni
Russie
Salvador
Serbie
Singapour
Slovaquie
Slovénie
Sri Lanka
Suède
Suisse
Taïwan
Territoires palestiniens
Thaïlande
Tunisie
Turquie
Ukraine
Uruguay
Venezuela
Vietnam

Adding selfie checks

To add selfie checks to your application, first follow the guide to collect and verify identity documents.

Adding selfie checks to VerificationSessions

When creating a VerificationSession, use the options.document.require_matching_selfie parameter to enable selfie checks.

Command Line
cURL
curl https://api.stripe.com/v1/identity/verification_sessions \ -u "
sk_test_BQokikJOvBiI2HlWgH4olfQ2
:"
\ -d type=document \ -d "options[document][require_matching_selfie]"=true

This configures the verification flow to require a photo ID and a face picture from your user.

Accessing selfie check results

After it’s submitted and processed, the VerificationSession status changes depending on the result of the checks:

  • verified — Both the document and selfie checks were successful. The session verified_outputs contains extracted information from the document.
  • requires_input — At least one of the document or the selfie checks failed.

To access the captured selfie and document images, you’ll need to retrieve the associated VerificationReport, you can do this by expanding the last_verification_report field in the session:

server.js
Node
// Set your secret key. Remember to switch to your live secret key in production. // See your keys here: https://dashboard.stripe.com/apikeys const stripe = require('stripe')(
'sk_test_BQokikJOvBiI2HlWgH4olfQ2'
); const verificationSession = await stripe.identity.verificationSessions.retrieve( '{{SESSION_ID}}', { expand: ['last_verification_report'], } ); const verificationReport = verificationSession.last_verification_report;

The VerificationReport has document and selfie fields holding the results of the document and selfie checks. Here’s an example VerificationReport with successful document and selfie checks:

{ "id": "vr_cy86k8Ik4hZukQw25CXA7pl5", "object": "identity.verification_report", "type": "document", "verification_session": "vs_pEjfhDHsZcc7blyHjKiqmzWT", "created": 1611776872, "livemode": true, "options": { "document": { "require_matching_selfie": true } }, "document": { "status": "verified", "error": null, "first_name": "Jenny", "last_name": "Rosen", "address": { "line1": "1234 Main St.", "city": "San Francisco", "state": "CA", "postal_code": "94111", "country": "US" }, "document_type": "id_card", "expiration_date": { "day": 17, "month": 7, "year": 2024 }, "files": ["file_JGx9mji6T4usIuabAxX127HS", "file_COmkmMlbF5UY84gr9XFlrAoq"], "issued_date": { "day": 4, "month": 27, "year": 2021 }, "issuing_country": "US" }, "selfie": { "status": "verified", "error": null, "document": "file_OOkkqL2gWeITAQ6vC5AZoqVQ", "selfie": "file_mstcLmATGl9xb2JRM7vbQ8Sg", } }

To access the collected document and face images, see Accessing verification results.

Understanding selfie check failures

The document and selfie VerificationReport fields contain the collected data as well as a status and error fields to help you understand whether the check is successful or not.

The status field tells you whether each check is successful or not. The possible values are:

  • verified - The verification check is successful and the collected data is verified.
  • unverified - The verification check failed. You can check the error hash for more information.

When the verification check fails, the error field contains code and reason values to explain the verification failure. The error.code field can be used to programmatically handle verification failures. The reason field contains a descriptive message explaining the failure reason and can be shown to your user.

Document check failures

Failure details are available in the report document.error field.

Error codeDescription
document_expiredThe provided identity document has expired.
document_unverified_otherStripe couldn’t verify the provided identity document. See list of supported document types.
document_type_not_supportedThe provided identity document isn’t one of the session’s allowed document types.

Selfie check failures

Failure details are available in the report selfie.error field.

Error codeDescription
selfie_document_missing_photoThe provided identity document did not contain a picture of a face.
selfie_face_mismatchThe captured face image did not match with the document’s face.
selfie_unverified_otherStripe couldn’t verify the provided selfie.
selfie_manipulatedThe captured face image was manipulated.

Voir aussi

  • Verify your users’ identity documents
  • The Verification Sessions API
Cette page vous a-t-elle été utile ?
OuiNon
Besoin d'aide ? Contactez le service Support.
Rejoignez notre programme d'accès anticipé.
Consultez notre log des modifications.
Des questions ? Contactez l'équipe commerciale.
LLM ? Lire llms.txt.
Propulsé par Markdoc