# Frictionless Failed Authentication The steps to follow this flows are: All 3-D Secure flows has the following steps, some of them don’t need validation, some of them need it. *** **Characteristics:** * Card not enrolled in 3D Secure, or * Issuer declines authentication, or * Technical error occurs **Flow Steps:** ``` 1. Setup → Get authentication tokens 2. Capture → Collect device data automatically 3. Enroll → 3D Secure check: FAILED/NOT AVAILABLE 4. Result → Authentication failed (ECI: 07 for VISA/AMEX, 00 for Mastercard) 5. Decline → Transaction may be declined or processed without 3DS 6. End → Handle according to merchant policy ``` **API Responses:** * Setup: `status: "Completed"` * Enroll: `status: "Authentication_failed"` * No validation step available **Common Reasons:** * Card not enrolled in 3D Secure program * Issuer technical issues * Invalid card information * Authentication system unavailable --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://firstoken.gitbook.io/api-docs/api-reference/risk/payer-authentication-3d-secure/detailed-flow-scenarios/frictionless-failed-authentication.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.