# Solutions, routing & PSP eligibility

Omno decides which provider processes each transaction in two stages: it **filters** the providers a customer is eligible for, then **routes** among the eligible ones.

## Solutions and merchant PSPs

- A **Solution** is one of Omno's provider integrations.
- When you authorize a Solution and add it to a **Router** (or a **Direct Link Route**), it becomes one of your **merchant PSPs** (`merchantPSP`).
- A **Router** selects among your merchant PSPs for Cashier and standard pay-in/payout flows. A **Direct Link Route** does the same for [Direct Link](/guides/concepts/direct-link).


## Router vs Direct Link Route

| Parameter | Used by | Effect |
|  --- | --- | --- |
| `routerId` | Standard pay-in and payout | Process with a specific Router. |
| `directRouteId` | [Direct Link](/guides/concepts/direct-link) pay-in and payout | Process with a specific Direct Link Route (no Omno UI). |


Provide **at most one**. If neither is set, default routing applies. Cashier sessions follow your **default Router**.

## Signals that affect selection

| Signal | Effect |
|  --- | --- |
| `kycVerified` | Whether the customer is KYC-verified in your system. Some providers require it; this narrows the eligible set. |
| `previousTransactionCount` | How many transactions the customer has made with you. Used by first-time-deposit and similar rules. |


## Eligibility filtering

Beyond routing, Omno **filters** which providers a customer is eligible for. Providers can be restricted by **customer group** and **KYC level**, so a customer is only offered providers whose rules match. Eligibility and routing work together.

| Field | Effect |
|  --- | --- |
| `customer.customerGroups` | Merchant-defined group labels (for example `"Vipgroup"`, `"Test"`), matched against a provider's group rules. |
| `customer.kyc.kycLevels` | Merchant-defined KYC level labels (for example `"Identity Check"`, `"Mail Verification"`), matched against a provider's KYC rules. |
| `customer.kyc.allowBypass` | Whether KYC bypass is permitted for the customer. |


Eligibility filtering applies to the **Cashier**. When no provider is eligible, the transaction's `detailedStatus` is `NO_PROVIDER_AVAILABLE`.

## Build it →

- [Customers, groups & KYC](/guides/concepts/customers) · [Transaction lifecycle](/guides/concepts/transaction-lifecycle)
- [Cashier → Full Cashier](/cashier/full-cashier) · [Direct Link](/direct-link)