---
title: "Fabrick Advice"
description: "Transaction Risk Analysis to request an exemption from Strong Customer Authentication and protect exempted transactions against chargebacks (powered by Riskified)."
url: "https://docs.fabrick.com/en/payment-hub-and-orchestra/ecommerce/features/fraud-prevention/fabrick-advice/"
language: "en"
---

# Fabrick Advice

**Fabrick Advice** is the complementary service to [**Fabrick Guaranteed payments**](https://docs.fabrick.com/en/payment-hub-and-orchestra/ecommerce/features/fraud-prevention/fabrick-guaranteed-payments/) that allows performing a *Transaction Risk Analysis (TRA)* to benefit from PSD2 exemptions\
(*Powered by Riskified*).

The risk analysis with Fabrick Advice is twofold:

- a **first pre-authorization analysis**, aimed at evaluating the transaction's eligibility for exclusion from the authentication process
- a **second analysis**, more accurate, applied to exempted transactions and aimed at guaranteeing them against potential chargebacks.

Exemptions are applicable to transactions with amounts within the thresholds of **100 / 250 / 300 €**, based on the fraud rates of the reference acquirer.

---

## Fabrick Advice - Transactional Scenarios

![Fabrick Advice](https://docs.fabrick.com/en/assets/images/advice-flusso-c09136362393209b06374ef471ec1d3b.png)

Placed in the context of the entire transactional flow, Fabrick Advice can determine the following scenarios.

![Fabrick Advice](https://docs.fabrick.com/en/assets/images/advice-schema-49b6367e8aa387f6a6452e8e106948d7.png)

### Transaction **not eligible** for **TRA** application

The transaction is normally processed through a **3DS** flow.

### Transaction **eligible** for **TRA** application

The transaction is analyzed by Fabrick Advice, which can return one of the following outcomes.

#### Possible outcomes

- **Fraud**\
  Transaction with a high risk of fraud.\
  The transaction process is interrupted with a **dedicated KO**.

- **3DS2**\
  The transaction presents a moderate risk of fraud.\
  Proceeds with authentication.

- **Exemption**\
  The transaction presents a low risk of fraud.\
  It is possible to proceed with an exemption request:

  - **Exemption accepted**\
    The transaction is processed under exemption and, upon a positive outcome, **Fabrick Guaranteed Payments** is applied, guaranteeing the transaction in the event of fraud.
  - **Soft decline**\
    The issuer rejects the exemption request.\
    The transaction is subject to security protocols.

---

## Service Activation

**Fabrick Advice** activation can be requested from your **commercial representative**.\
**Fabrick Guaranteed Payments** must already be active.

---

## Implementation

For implementation, the same steps required for **Fabrick Guaranteed Payments** must be followed.

The main differences compared to that service are that, in addition to the *approved* or *declined* outcomes:

- it may be required to **authenticate the transaction** (soft error `8006` for API Only integrations, automatically handled in others).
- the transaction may **not be authorized** due to a high fraud risk (error 7422).

### Supported Integrations

✓ — Checkout Page

✗ — Pay By Link

✓ — Web Component

✓ — Lightbox

✓ — API Only

✓ — Plugin (Check the dedicated page)

---

## 3DS Authentication Verification

### Enable the **ThreeDS** field

By enabling the **ThreeDS** field on the **Fabrick Payment Orchestra Merchant Back Office**\
(*NO DISPLAY > API Only* or *Payment page > Other integrations*), it is possible to verify whether a transaction has been authenticated.

The field is located in the two pages of the dropdown menu under **Payment Page → Fields\&Parameters**

![Advice_MBO_1.png](https://docs.fabrick.com/en/assets/images/advice-mbo-1-33776f39549ab429e143f28f81419119.png)

![Advice_MBO_3.png](https://docs.fabrick.com/en/assets/images/advice-mbo-3-53a714876db2f4a045b8194909e0d800.png)

### Authentication Details

An authenticated transaction may have:

- `authenticationLevel`: `2C`, `2F`, `1F`, `1H`
- `authenticationStatus`: `Y` or `A`

A transaction with a failed authentication may have:

- `authenticationLevel`: `2C`, `2F`, `1F`
- `authenticationStatus`: `null` or values other than `Y` and `A`

A transaction for which authentication was requested but the card is not 3DS enrolled may have:

- `authenticationLevel`: `1H`
- `authenticationStatus`: `null`\
  In this case, as with authenticated transactions, since the merchant is 3D-enabled, **liability falls on the issuer**.

---

## Testing Fabrick Advice in Sandbox

In **sandbox**, for transactions with an amount below **250 EUR**, it is possible to test the main production scenarios by populating the **PrimaryEmail** field:

```json
{
	...
    "OrderDetails": {
		...
        "CustomerDetail": {
			...
            "PrimaryEmail": "",
			...
		}
		...
	}
...
}
```

and using the cards indicated as shown in this table.

| Email                                                                     | Card             | Outcome                                             |
| ------------------------------------------------------------------------- | ---------------- | --------------------------------------------------- |
| [tra.decline@sandbox.fabrick.com](mailto:tra.decline@sandbox.fabrick.com) | 4012000000003101 | OK, No 3D – Rejected by Fabrick Guaranteed Payments |
| [tra.approve@sandbox.fabrick.com](mailto:tra.approve@sandbox.fabrick.com) | 4012000000003101 | OK, No 3D – Approved by Fabrick Guaranteed Payments |
| [fraud@sandbox.fabrick.com](mailto:fraud@sandbox.fabrick.com)             | 4012000000003101 | KO – High Risk Profile (Fraud)                      |
| [sca@sandbox.fabrick.com](mailto:sca@sandbox.fabrick.com)                 | 4012000000003101 | OK, 3D                                              |
| [sca@sandbox.fabrick.com](mailto:sca@sandbox.fabrick.com)                 | 4012000000003028 | KO – Authentication failed                          |
| [sca@sandbox.fabrick.com](mailto:sca@sandbox.fabrick.com)                 | 4775718800003024 | KO – Authorization denied                           |

Payloads and usage scenarios are available on [**Fabrick Guaranteed payments**](https://docs.fabrick.com/en/payment-hub-and-orchestra/ecommerce/features/fraud-prevention/fabrick-guaranteed-payments/#payload-and-usage-scenarios)

---

## Production Activation

Before proceeding with production activation, as with **Fabrick Guaranteed Payments**, it is necessary to share with Fabrick some tests on **standard scenarios**.

### Examples of required scenarios

- Transaction authorized and approved by the service, subsequently captured
- Transaction authorized and approved by the service, subsequently cancelled
- Transaction authorized and declined by the service, subsequently cancelled
- Transaction authenticated and authorized, subsequently captured
- Transaction declined by the service for "Transaction Rejected - High Risk Profile (Fraud)"