Allocations

Allocations control which sub-gateways a given customer sees at checkout. Routing decides the provider behind a payment; allocations decide the set of checkout options a customer is even offered. You manage them under Addons → RelyPay → Allocation.

Addons → RelyPay → Allocation

How visibility works

Each allocation rule lists the sub-gateways that remain visible to the customers it matches. If no rule matches an order, every sub-gateway is visible — the screen's empty state reads:

No rules. All sub-gateways visible to all clients.

So the safe default is "show everything", and each rule you add narrows what a matched group of customers sees. A rule never adds a gateway a customer could not otherwise use — it only hides the ones you leave out.

Criteria you can build a rule on

A rule targets customers using one of:

• Country
• Client Group
• Product Group
• Config Option Group
• Product Addon
• Product Bundle

Product-based rules (Product Group, Config Option Group, Product Addon, Product Bundle) can add an optional secondary filter — such as Country or Client Group — for finer targeting, for example "customers in the UK buying the Reseller plan".

First-match order

When several rules could apply, RelyPay evaluates them in this order and the first match wins:

1. Product-based rule with a secondary criterion
2. Product-based rule
3. Country
4. Client Group
5. Default — all sub-gateways visible

This means your most specific rules take precedence, and anything not covered falls through to "show everything".

A worked example

Suppose you want Indian customers to see UPI, Cards and Net Banking, but international customers to see only Cards and PayPal:

1. Add a Country rule for India listing RelyPay — UPI, RelyPay — Cards and RelyPay — Net Banking.
2. Add a Country rule for your international markets listing RelyPay — Cards and RelyPay — PayPal.

Any customer not matched by either rule still sees every sub-gateway, so nobody is ever left without a way to pay.

Allocations only affect visibility

Allocation never blocks checkout. It only hides or shows sub-gateways as a convenience. This is a licensed feature, and if your license cannot be confirmed for an extended period the filter simply stops applying — all gateways show again — so your customers can always pay.

Related pages

• Routing — which provider takes each payment
• Sub-gateways — the checkout options a rule shows or hides
• Troubleshooting — what to check if a method is missing for a customer