How does PSP eligibility work?
Before routing, each provider is checked against the payment. Typical conditions are the countries and currencies it supports, the methods it offers, minimum and maximum amounts, daily or monthly volume caps, the customer groups or customer verification levels it may serve, and whether it supports Pay-In, Pay-Out or both. Providers that fail any condition are removed. Routing and cascading then work only within the eligible set.
Why does PSP eligibility matter for compliance and approval rate?
Sending traffic a provider is not set up for causes declines at best and contract breaches at worst. A provider licensed for some countries may not accept customers from others, and a provider with a USD 2,000 payment limit will reject anything above it. As an illustrative example: if 3% of 50,000 monthly payments exceed one provider’s limit, 1,500 payments fail when routing ignores the limit. With an eligibility rule, those payments go straight to a provider that accepts them.
How is PSP eligibility different from routing?
Eligibility answers “which providers may take this payment”. Routing answers “which of those should take it first”. Keeping them separate makes both easier to maintain: eligibility changes when contracts, licences or limits change, while routing changes when performance or cost data changes. It also means a cascade can never retry a payment on a provider that should not see it.
Where does Omno use it?
Omno’s PSP eligibility rules define, per PSP, which customer groups, customer verification levels, methods, currencies and amounts it can handle. Routing rules and cascade order then choose among the eligible PSPs, and the routing-decision log records which providers were eligible and which was selected.