> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/online-payments/api-integration-methods-auth-and-endpoints/blocking-failed-3ds-transactions.md).

# Blocking failed 3DS transactions

The purpose of 3-D Secure is to safeguard the online payment by applying an additional authentication step of the cardholder before sending an authorization request to the card issuer.

However, adoption of 3-D Secure is significantly different across geographic regions. This leads to a variety of payment flows, depending on if 3-D Secure is mandatory or not in that specific country.

Given the role of Verifone as a Payment Gateway, and the differences across regions where merchants can sell, it is necessary to add a blocking rule based on the result of the 3-D Secure authentication to enforce the business flow required by each country.

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

The **Blocking Rulesets** in Verifone Central is available under the *Administration* tab and can be used by any user with a Merchant Admin role.

<div data-with-frame="true"><figure><img src="/files/hk6VczlAodWVQfZh55bi" alt=""><figcaption></figcaption></figure></div>

The availability of 3D-Secure depends on each acquirer. Consult the list of supported acquirers together with the functionality available [here](/online-payments/supported-acquirers.md).

## Workflow in Verifone Central <a href="#workflow-in-verifone-central" id="workflow-in-verifone-central"></a>

Merchants that fall under the requirements of PSD 2 and require a 3DS authentication from shoppers located inside the European Economic Area (EEA) need to create two blocking rules to block transactions that either failed or rejected the 3-D Secure authentication process.

Blocking rulesets must be set at Merchant Site level. As a Merchant Admin, in Verifone Central, go under **Administration** > **Blocking Rulesets** and create two new blocking rulesets, blocking based on the 3DS Authentication statuses: N (Failed) and R (Rejected). These need to be two independent blocking rulesets.

**Create a blocking ruleset for failed 3DS transactions**

<div data-with-frame="true"><figure><img src="/files/kT9z0c1rE0BQPgtogIhz" alt=""><figcaption></figcaption></figure></div>

**Create a blocking ruleset for rejected 3DS transactions**

<div data-with-frame="true"><figure><img src="/files/qpuwqAplbyh5vMfEqZPC" alt=""><figcaption></figcaption></figure></div>

Read the full documentation for blocking rulesets [here](/online-payments/fraud-management/blocking-rulesets.md).

## Reporting <a href="#reporting" id="reporting"></a>

Failed transactions due to blocking rulesets will have a response code = 9998 with the response description *Transaction blocked by validation rules*. Further reporting can be done based on the 3D Secure status N (Failed) and R (Rejected).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.verifone.com/online-payments/api-integration-methods-auth-and-endpoints/blocking-failed-3ds-transactions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.