--- title: "Review 3D Secure results" slug: "review-three-d-secure-results" updated: 2026-10-05T21:00:25Z published: 2026-10-05T21:00:25Z canonical: "resource.payrix.com/review-three-d-secure-results" --- > ## Documentation Index > Fetch the complete documentation index at: https://resource.payrix.com/llms.txt > Use this file to discover all available pages before exploring further. # Review 3D Secure results Three-Domain Secure (3D Secure or 3DS) is an authentication protocol that helps issuers verify cardholder identity during card-not-present (CNP) transactions. By sharing additional transaction and device data during checkout, 3DS helps reduce fraud, improve authorization decisions, and support risk-based authentication. Payrix Pro does not perform 3DS authentication. Instead, we accept EMV 3DS authentication data generated by certified third-party providers and sent in API-based transaction authorization requests. This article explains how to verify 3DS enablement and review available authentication results in the Payrix Pro portal. ## Overview Payrix Pro accepts EMV 3DS authentication data generated by certified third-party providers, such as [Cardinal Commerce](https://vcasdocs.cardinalcommerce.com/), [Paay](https://docs.3dsintegrator.com/docs/overview), or [Ravelin](https://developer.ravelin.com/merchant/guides/3d-secure/overview/). If your workflow requires 3DS, you must integrate a certified provider and submit authentication results through the Payrix Pro API. When permitted by card network requirements, 3DS authentication remains optional. 3DS authenticated transactions provide the following benefits: - Helps reduce transaction fraud - Improves authorization rates and qualifies for lower interchange rates under eligible card brand programs - Supports issuer verification of higher-risk transactions - Reduces checkout friction through risk-based authentication - Supports liability shift when card brand, issuer, authentication, and provider requirements are met When you process a transaction with 3DS data, you can use the Payrix Pro portal to: - Confirm whether your account is enabled to accept 3DS data for supported card brands. - Identify transactions submitted with 3DS authentication data. - Review basic issuer authentication results returned during transaction processing. > [!WARNING] > Important! > > The portal provides a simplified view of 3DS authentication results. Full EMV 3DS metadata, authentication values, cryptograms, Directory Server transaction IDs, card network responses, and processor validation details are only available through third-party providers and the Payrix Pro API. > > To implement or troubleshoot 3DS authentication workflows, see [Submit 3D Secure authentication data](https://docs.worldpay.com/apis/payrix/dev-int-guide/direct-payments/transaction-data/submit-three-d-secure-authentication-data). ## Prerequisites To review 3DS authentication results in the Payrix Pro portal: - Confirm 3DS is enabled for each supported card brand. - Confirm transacting merchants are boarded on VCore. - Integrate a certified 3DS provider. - Process transactions using the Payrix Pro API that includes authentication data returned by your 3DS provider. ## Enable 3D Secure on Payrix Pro Before processing transactions with 3DS authentication data, you must verify that 3DS is enabled for each supported card brand. To verify 3DS enablement in the Payrix Pro portal: 1. Select [Settings](/v1/docs/settings-partners) in the main side bar. 2. Select [Setup Details](/v1/docs/parameters-setup-details-partners) in the Business Settings section. 3. Select the **Transaction Limits** tab. 4. Review the following parameters: - *MC 3DSecure Enabled* - *Visa 3DSecure Enabled* - *Amex 3DSecure Enabled* - *Discover 3DSecure Enabled* If a card brand is not enabled, contact your Strategic Partner Manager (SPM) to request enablement. ## Review 3DS Transaction Results The portal provides a simplified view of issuer authentication outcomes and omits detailed 3DS processing data. After a transaction is submitted with 3DS authentication data, the [Transaction Details](/v1/docs/transaction-details-partners) page displays available issuer authentication results. To review available 3DS results: 1. Select [Payment History](/v1/docs/payment-history-partners) in the Payments category in the main side bar. 2. Select any field in the applicable transaction row to open the Transaction Details page. On the Transaction Details page, review the 3DS status badge or open the Alerts tab for authentication results. Detailed 3DS authentication metadata, cryptograms, and processor validation results are not available in the portal. ### Check the 3DS Status Badge The Transaction Details panel includes a 3DS status badge that summarizes the reported authentication outcome. The status badge indicator summarizes the authentication outcome but does not display authentication values or network-level validation details. The 3DS status badge can display one of the following status values: - **Match:** Cardholder authentication succeeded. Displayed as a checkmark icon. - **Failed or Attempted:** Authentication was attempted, but the issuer could not verify the cardholder. Displayed as an X icon. - **Not provided:** Authentication data was not submitted or could not be validated. Displayed as a minus icon. ### Review Issuer Authentication Alerts The Alerts tab displays issuer authentication results returned during processing. When available, 3DS alerts use a **Type** value of **3DS**. Additional validation details and network response data are available only through the API. See the following table for possible issuer result alert values for 3DS transactions: | Code | Message | Description | | --- | --- | --- | | Authentication passed | 3DS authentication successful | Cardholder authentication succeeded | | Authentication is invalid | 3DS authentication invalid | Submitted authentication data was invalid | | Authentication failed | 3DS authentication failed | Cardholder authentication failed | | Authentication was not validated | 3DS authentication not validated | Authentication could not be validated | | Authentication successful without liability shift | 3DS authentication successful without liability shift | Cardholder authentication succeeded, but the transaction did not qualify for liability shift | A person or entity that receives an account from a card company or card issuer. The movement of funds between a customer (cardholder or eCheck account holder) and a merchant to purchase a good or service. The process of placing funds on hold with a customer's bank to verify the availability of the amount required for a transaction. A PayFac-as-a-service platform. Software companies can act as payment facilitators without taking on the associated risks, compliance burdens, and investment. A member-based corporation, such as Visa or Mastercard, that facilitates electronic payments between consumers, businesses, and banks, replacing cash and checks. It also sets and enforces rules among members and promotes its own brand. A business that enables financial transactions with customers from various channels such as credit cards and debit cards or bank accounts. Worldpay is the primary processor of the Payrix Pro platform, which offers limited omnichannel integration options for compatibility with third-party processors TSYS, Chase Payment Tech, Fiserv, and Global Payments.