# Create a Shield rule

> Create a Shield rule that blocks a payment, sends it to review, requires 3D Secure or allows it based on your conditions, then reorder, turn off or delete it.

A custom rule decides on a payment based on your own conditions: its amount, its currency, its
payment method, the customer's email or phone, the country of their IP address.

The owner, an Administrator or a custom role with **Manage Shield** creates and edits rules;
**View Shield** is enough to read them. Custom rules are part of **Shield Advanced**, included in
the **Scale** and **Enterprise** plans and offered as an [add-on](https://docs.wajub.com/dashboard/subscription/add-ons)
on the others. Without it, the tab shows **Custom rules are part of Shield Advanced**. Shield must
be [activated](https://docs.wajub.com/dashboard/shield/enable). No security code is asked for.

## The steps

1. **Open the dialog**

   In **Shield**, open the **Rules** tab, then click **Create rule**. The **Create rule** dialog
   opens.

2. **Name the rule**

   The **Name** is required, 120 characters at most. The &#x2A;*Description (optional)** tells your
   members what the rule is for.

3. **Choose the action**

   Under **Action**, **Block** declines the payment. **Send to review** lets it through and adds
   it to the **Reviews**, unless Shield already blocks it. **Challenge with 3DS** has a card
   payment confirmed with the customer's bank, where the card's processor offers it. &#x2A;*Allow (bypass other rules)** lets the payment through, unless it matches
   your blocklist or exactly matches a sanctioned name.

4. **Choose the mode**

   Under **Mode**, **Enforced** acts on payments. **Monitor only** counts the matching payments
   without deciding anything: the rule carries the **Monitor only** badge, and its firings show
   like the others, so you can judge it before enforcing it.

5. **Add the conditions**

   Under **When all of these are true**, choose a **Field**, an **Operator** and a **Value**.
   **Add condition** adds another one, up to 10: the rule only applies when all of them are true.
   The fields are **Transaction amount**, **Currency**, **Payment method**, **Customer email**,
   **Customer phone**, **IP country**, **First transaction from this customer** and **Matches an
   entry in the blocklist**.

   ![The Create rule dialog: the name Large orders from abroad, the Send to review action, the Monitor only mode and two conditions on the transaction amount and the IP country.](https://docs.wajub.com/dashboard/en/light/shield-rule-dialog.webp)

   *The rule only applies when all its conditions are true.*

6. **Create the rule**

   Leave **Active** on so that it applies straight away, then click **Create rule**. The message
   &#x2A;*Rule created.** appears, and the rule is added at the bottom of **Your custom rules**.

## Rule order

Shield reads your rules from top to bottom, and the first enforced rule that matches the payment
decides; a rule in **Monitor only** never decides. The arrows on each row move it up or down one
place. A customer allowed from the reviews becomes an **Allow** rule placed at the top of the
list. [Rules](https://docs.wajub.com/risk/shield/rules#which-one-wins), in the developer docs, explains what wins.

## Edit, turn off or delete a rule

The switch on each row turns the rule off or back on: an inactive rule is kept, and never
evaluated. The row's menu offers **Edit rule**, which opens the dialog again, and **Delete rule**,
which asks for confirmation: the payments it would have targeted then go through unchanged.

If your plan loses **Shield Advanced**, your rules are kept but no longer apply; they resume if
you get the add-on back. Customers allowed from the reviews stay allowed on every plan.

## Built-in protections

Below your rules, **Built-in protections** sums up the checks Shield applies to every payment,
with no setup. **Shield Advanced** adds more.
