# Gateway Pools

Gateway Pools give you full control over how payments are routed inside Funnelish.

Instead of relying on a single processor, **you can group multiple gateways together and set rules to decide which one handles each transaction.** 

This helps you:

* Increase authorization rates
* Reduce failed checkouts
* Lower processing fees
* Protect against risk and limits

{% hint style="warning" %}
**Note:** At the moment, Gateway Pools are only available for **Credit Card processors**.
{% endhint %}

### How Gateway Pools Work

When a customer checks out, Funnelish automatically evaluates your conditions and **routes the payment through the most suitable gateway in your pool.**

#### Example scenarios:

* A declined transaction can be retried automatically through a backup gateway.
* High-ticket orders can be sent through a lower-fee processor.
* Different currencies can be routed to the most efficient local gateway.
* Certain card brands (Visa, Mastercard, Amex) can be tied to specific processors.

### Setting Up Gateway Pools

You can set up and manage Gateway Pools either globally (from your account) or directly inside a funnel.

#### 1. Connect your gateways

Before creating a pool, make sure your preferred gateways are connected. You’ll need at least two gateways available to build a pool.

1. Go to Settings > Payments 
2. Click on Connect a new gateway
3. Select Credit Card
4. Choose and connect your preferred Credit Card Gateways. Once added here, these can be added with just one click at funnel level.

> → **Quick jump to** [**Credit Card Gateways**](/start/collecting-payments/card-payments.md) **& how to connect them.**

#### 2. Create a gateway pool

1. Go to **Account > Payments** (or create it directly inside a funnel under **Funnel Apps > Funnelish Pay**).
2. Click **Create Gateway Pool**.
3. Select which gateways you want to include in the pool.
4. Choose a **default gateway**. This is the processor Funnelish will try first for every transaction.
5. For the remaining gateways in the pool, add **conditions** to decide when they should be used.

#### Conditions you can include:

When setting up your pool, you can combine one or more of the following conditions:

* **Transaction declined** → Retry with another gateway to save the sale.
* **Split-volume** → Spread transactions based on a fixed amount or percentage across processors to manage risk and limits. 
* **Product type** → Route one-time or subscription products differently.
* **Tags** → Apply special handling for high-risk or priority products.
* **Card brand** → Assign Visa, Mastercard, Amex, etc. to specific processors.
* **Currency** → Process orders in the most efficient local gateway.
* **Regions** → Ensure buyers use gateways that work best in their country.
* **Amount** → Assign gateways by order value (e.g., high-ticket purchases).

#### 3. Adding the gateway pool to a funnel

Once your pool is created, you can add it directly inside a specific funnel through **Funnelish Pay**.

<figure><img src="/files/N2X31vaZXI1wYoHG2k60" alt=""><figcaption></figcaption></figure>

4. **Upgrade your pages**

{% hint style="danger" %}
Your pages should be upgraded to v2 editor for gateway pools to work.
{% endhint %}

* Please update your checkout & upsell/downsell pages to v2 editor from here:

<figure><img src="/files/jq0EWL5nmw1xlqpKN9gg" alt=""><figcaption></figcaption></figure>

{% hint style="success" %}
Funnelish will automatically re-attempt or direct transactions through your specific conditions.
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://docs.funnelish.com/advanced-features/gateway-pools.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.