> ## Documentation Index
> Fetch the complete documentation index at: https://codebeans-payment-rules-pro.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Combining conditions with And / Or

> How the joiner changes what your rule matches, and what to do when you need both.

Advanced customizations hold up to five conditions, joined by a single **And** / **Or** selector that applies to all of them.

![The And / Or radios above the condition group](https://mintcdn.com/codebeans-payment-rules-pro/0guf-DxrSbw6Ls57/images/advanced-conditions.jpg?fit=max\&auto=format\&n=0guf-DxrSbw6Ls57\&q=85\&s=95eafad3416d3447c808767adfc3dd81)

## The two joiners

**And** — every condition must be true. Each condition you add makes the rule fire *less* often.

> Cart total over ₹10,000 **and** shipping to Germany **and** customer not logged in

**Or** — one true condition is enough. Each condition makes the rule fire *more* often.

> Currency is USD **or** currency is CAD **or** currency is AUD

## Choosing between them

The joiner follows from the shape of your intent:

* **Listing alternatives** — several countries, several currencies, several tags → **Or**
* **Narrowing to a case** — a specific combination of circumstances → **And**

A useful check: read the right-hand **Description** panel aloud. It prints the joiner as a badge between conditions. If the sentence sounds right, the rule is right.

## The mixed-logic limit

> [!WARNING]
>
> There is one joiner per rule. You cannot express *(A or B) and C* in a single advanced customization.

Two ways around it:

**Split into several rules.** *(Germany or Austria) and cart over ₹10,000* becomes two rules — one for Germany, one for Austria, each with the cart-total condition. Rules are independent, so two rules hiding the same method behave as an Or between them.

**Use a sub-condition.** Sub-conditions refine their parent condition rather than joining the top-level group, which covers many cases that look like they need mixed logic — narrowing *Cart contains products* by collection or vendor, for example, instead of adding a second top-level condition.

## Multiple rules interact

Rules do not know about each other. Every active rule is evaluated, and a method hidden by any one of them is hidden. This is why splitting works — and why an unexpectedly missing payment method is usually a second, forgotten rule rather than a bug in the one you are looking at. Check the full [customizations list](https://codebeans-payment-rules-pro.mintlify.site/your-payment-methods/the-customizations-list.md) before assuming.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.