OMNO selects a PSP for each transaction using routing, constrained by eligibility rules. You can influence or pin selection with the following parameters.
| Parameter | Used by | Effect |
|---|---|---|
routerId | Cashier, PayIn, Payout | Process with a specific router. |
directRouteId | Direct Link PayIn/Payout | Process with a specific Direct Link route (no OMNO UI). |
Provide at most one. If neither is set, default routing applies.
| Field | Effect |
|---|---|
kycVerified | Whether the customer is KYC verified in your system. Some PSPs require KYC; this narrows eligible providers. |
previousTransactionCount | Number of previous transactions the customer made in your system. Used by first-time-deposit (FTD) and similar rules to select a provider. |
These are sent on the create requests (cashier session, pay-in, pay-out). See the request schemas under APIs.
Beyond routing, OMNO filters which PSPs a customer is eligible for. PSPs can be restricted to customer groups and KYC groups/levels, so a customer only sees, or is routed to, PSPs whose rules match that customer's group and KYC level. Eligibility filtering and routing rules work together.
Related fields (on the customer / cashier session request):
| Field | Effect |
|---|---|
customer.customerGroups | Groups the customer belongs to; matched against PSP group rules. |
customer.kyc.kycLevels | KYC levels for the customer; matched against PSP KYC rules. |
customer.kyc.allowBypass | [TBD: meaning of allowBypass] |
[TBD: how groups/levels are configured in the dashboard]
[TBD: behavior when no PSP is eligible — likely NO_PROVIDER_AVAILABLE; confirm]
[TBD: whether eligibility filtering applies to Direct Link and Payment Page too, or Cashier only]