# 3D Secure Authentications

3D Secure is a protocol designed to be an additional security layer for online payment transactions, including debit, credit, wallets and APMs. This protocol requires customers to complete an additional verification step with the card issuer when paying online.

Common 3D Secure Authentication methods include push notifications, face recognition, fingerprint, and dynamically generated one-time passwords (OTPs).

The 3D Secure Authentications report provides an overview of 3D Secure payment authentication attempts and allows you to see any 3DS details processed in transactions. You will be able to see in the 3D Secure Authentications Details panel information such as 3D Secure Authentication ID, 3DS Provider Contract ID, 3DS Version, Error number and description, Signature verification, Card brand information, Reason code and description, as well as more details.

For more information, including the frictionless and step-up flows, see the[ 3D Secure ](/verifone-central-getting-started/verifone-central/commerce/reporting/3d-secure-authentications.md)documentation.

## Availability <a href="#availability" id="availability"></a>

Merchants with the following roles in Verifone Central can access the 3D Secure Authentications report:

* Merchant Admin
* Merchant Reviewer
* Merchant Supervisor
* Merchant User
* Merchant Cashier

**Merchant Users** can only access the 3D Secure Authentications of their organization and cannot access the 3D Secure Authentications of their sub-organizations.

For more information on user roles and permissions, check the [Users and merchant roles](/verifone-central-getting-started/verifone-central/administration-tools/users-and-merchants-roles.md) article.

## Benefits <a href="#benefits" id="benefits"></a>

* One place to run reports for successful and non-successful 3DS transactions.
* Helpful for billing of 3DS authentications.
* Detailed view related to 3DS authentications (**example**: 3DS contract ID, organization ID, 3DS version etc).

## 3D Secure Authentications in Verifone Central <a href="#id-3d-secure-authentications-in-verifone-central" id="id-3d-secure-authentications-in-verifone-central"></a>

1. Log in to your [Verifone Central](broken://pages/xtNZm2bMCANroETthpG2) account.
2. Navigate to **Commerce** -> *Reporting* and then click on **3D Secure Authentications**.<br>

   <div data-with-frame="true"><img src="https://verifone.cloud/sites/default/files/inline-images/1_140.JPG" alt=""></div>
3. You can generate reports using different types of filters to query 3D Secure authentication data.<br>

   <div data-with-frame="true"><img src="https://verifone.cloud/sites/default/files/inline-images/2_92.JPG" alt=""></div>

   * Filter by 3DS authentication identifiers:
     * **3DS Authentication ID**: it is a unique 3D Secure ID attached to 3DS authentication.
     * **3DS Provider Contract ID**: use the 3D Secure Contract ID, that can be found under *Administration* > [3DS Contracts](/verifone-central-getting-started/verifone-central/administration-tools/3ds-contracts.md).
     * **Scheme Transaction ID**: is assigned by the schemes for 3DS authentication. This ID will help link 3DS Authentication, the order, and the transaction ID. It allows us to backtrack from the order and transaction page to identify the associated 3DS authentication using the Scheme Transaction ID. &#x20;
   * Filter by **date**: Select the start and end date for when the authentication occurred.
   * Filter by **Organization**: you can filter the results according to the organization(s) you are part of, by selecting the needed organization(s) from the main dropdown menu, or by selecting one of the below three options:
     * **Name** - use the name of the desired organization or part of the name.
     * **Organization ID** - use the organization ID, that can be found under *Administration* > *Organization Company and Sites*.
     * **Business Identifier Value** - use the business identifier value, that can be found under *Administration* > *Organization Company and Sites*.&#x20;
   * Filter by **3DS Statuses**:
     * **Successful**: 3DS authentication successfully completed
     * **Failed**: 3DS authentication didn’t go through
     * **Unable to complete**: 3DS authentication is abandoned or dismissed
     * **Successful attempts**: 3DS authentication is a successful challenge authentication
     * **Challenge required**: 3DS authentication where the card issuer has determined that the transaction requires additional authentication to meet security requirements (applies to consumer authentication 2.0 - decoupled authentication)
     * **Rejected**: 3DS authentication rejected by the card issuer


---

# 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://docs.verifone.com/verifone-central-getting-started/verifone-central/commerce/reporting/3d-secure-authentications.md?ask=<question>
```

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.