How do fraud scoring, customer rules and limits work together?
Every transaction gets a risk score before it is processed. Your rules decide what happens at each score, from letting the payment through to stopping it before any provider sees it. Customer rules add what you know about the customer. You tag customers and set volume thresholds, and the rules allow or restrict providers and methods for each tag, so a new customer above a volume threshold can be kept to the methods you choose while a trusted repeat customer sees every method.
Customer blocking handles the clear cases. A customer can be blocked fully, or only from the methods where they caused trouble. Limits put a ceiling on exposure: amount and volume caps per provider and per method, so one provider or one method never carries more risk than you chose.
Two smaller controls stop avoidable declines. Custom field validation checks the data a customer types, such as a phone number or a national ID number, before it reaches a provider that would reject it. Custom decline messages replace a generic error with a clear next step, such as trying another method, so a declined customer is more likely to complete the purchase.
How do verification levels and customer groups control routing?
Every payment request can carry two pieces of context about the customer: the customer groups they belong to and their customer verification levels (KYC levels in the API). Both come from your systems; Omno does not run KYC. You decide what a group means, such as new, VIP or under review, and you decide how verification maps to levels, often based on results from your identity verification provider.
Omno matches that context against the rules on each provider. A provider that requires verified customers is removed for a customer who has not passed verification. A provider reserved for VIP customers is removed for everyone else. Routing then runs only on the providers that remain. This matters because acquirers and local method providers have different appetites. Some will accept new, unverified customers in a high-risk category. Others will only take verified repeat customers, and sending them anything else raises their decline and dispute rates and puts the relationship at risk.
The same rules apply to payouts. A merchant can require a higher verification level before allowing payouts through a given provider, which supports anti-money-laundering controls without extra code.
How do card blocking and shared blocklists reduce losses?
Card blocking is the simplest control and one of the most useful. When a card is linked to fraud or a chargeback, you block it, and further attempts with that card stop before they reach a provider. That protects your chargeback ratio and keeps the provider from seeing repeated bad attempts. With multi-merchant management, the same card can be blocked across your brands.
Fraud rarely stops at one shop. Omno lets partner merchants share their blacklists and blocked cards, with full data protection, so a card that one merchant blocked after fraud or a chargeback is refused at the others too. Each merchant decides what it shares and keeps control of its own lists.
What changes versus a single PSP?
A single PSP applies its own risk rules to all your traffic. You cannot tell it to treat verified customers differently from unverified ones, unless it offers that feature, and you cannot send risky segments to a provider better suited to them because there is only one. When its risk model tightens, your approval rate falls and you cannot route around it.
With Omno, risk becomes part of routing. You match each customer segment to the providers that want that segment. You stop known bad cards before any provider sees them. You give finance and risk teams separate permissions through role-based access control, so routing and blocking changes are made by the right people and leave a trail.
Why do risk controls matter for cross-border merchants?
Card schemes and issuers watch fraud and disputes closely. Visa’s Acquirer Monitoring Program combines fraud and dispute signals into one ratio per merchant, and acquirers pass the pressure on to merchants with high ratios. Keeping chargebacks and fraud low is therefore a condition of keeping card acquiring at all.
Verification-aware routing, card blocking and shared blocklists work on the causes. They keep unverified customers away from providers that will not tolerate them, stop repeat fraud across shops, and give acquirers a clear record of how each payment was handled.
Merchants in regulated and high-risk sectors face their own requirements, such as which methods may be offered in a market or to a customer with a given verification status. Rules like these are easiest to enforce in the routing layer: if a provider or method is not allowed for a market or a customer status, it is never offered. Combined with the transparency logs, that gives compliance teams evidence of what was allowed, what was blocked and why.