Payment method rules
Retail Extensions · Rule · checked 2026-10-23
Payment method rules decides which payment methods each group of your customers may use at the till. For example, customers who order through a delivery platform pay only by that platform's method, and only your account customers may buy on account. When the cashier presses Pay, the methods a customer may not use are dimmed on the payment screen, with your reason beside them. This page covers what the app adds, how to write your rules, how to switch it on, and how to remove it.
What it does
When the cashier presses Pay, your shop sends the priced sale to the app's service. The service finds the rule for the sale's customer and answers before the payment screen opens.
| The cashier sees | When |
|---|---|
| The payment screen, with some methods dimmed and "Not for this sale: ⟨your reason⟩" | The customer's rule leaves out those methods. The cashier takes one that is not dimmed. |
| "This sale can't be paid", with "Customers in ⟨group⟩ can't pay at this till: use one with ⟨methods⟩." | The rule leaves out every method this till offers. Nothing is paid. |
| The payment screen, as always | No rule applies to the customer, or the rule leaves out none of this till's methods. |
| The refund choices, as always | A refund, or the returned items of an exchange: these are not checked. An exchange's new items are checked as a sale. |
| The sale goes on with every method, and is flagged on Sales to review | The service did not answer within 3 seconds, has not been sent the app's user yet, or could not read your shop. |
After the check, the till keeps the answer for exactly that sale. If the cashier then adds a line or changes the customer, the till says "The sale changed after the check. Press Pay again." Pressing Pay again checks the sale again. The app writes nothing to your shop.


What you set up first

- Install the app from the App library (see About Retail Extensions). The install adds the role IVENDNEXT PMR Integration, with no one in it. The check comes in switched off.
- Make a user for the app. Tick Is Desk User, give it the role IVENDNEXT PMR Integration alone and save. Then generate its API key: on the user, open Settings and press Generate Keys. Give the user no User Permissions.
- Search Desk for Role Permissions Manager. Give IVENDNEXT PMR Integration Read on Customer Group. The service reads your customer group tree, so that a group can take the rule of a group above it.
- Stop cashiers moving a customer into another group. The till lets a cashier change a customer's group, so a cashier could move a customer into a group whose rule allows more payment methods, or into a group with no rule. Search Desk for Customize Form, open Customer, set Customer Group's Perm Level to 1 and save. Then in Role Permissions Manager, give level 1 Write on Customer only to the roles that may move customers, such as your managers. A cashier's change to the group then does not save, though the till still says Saved: the customer's profile shows the group unchanged. A cashier also can no longer give a new customer a group: a customer created at the till takes your default customer group (Selling Settings), or none if you have not set one, and a manager sets the right one. Check the level 1 rows already there: Sales Master Manager has one by default, and none of your cashiers' roles may have level 1 Write.
- Search Desk for Registered Application and open IVENDNEXT PMR Rules feed. Choose the app's user as its Application User and save. Leave the feed switched off.
- Write your rules (below).
- In the App library, find the app under Installed and press Details. On the app's record, press Connect again. The record then says that it sent the API key of the app's user.
- Switch the check on (below).
If you must never sell on account unchecked, then change the check's When the service is down to Stop until the service answers (refuse), after Connect again. Every sale then waits on the service.
The rules
Search Desk for IVENDNEXT PMR Rule and press Add. Make one record for each customer group that needs a rule. The record is named by its customer group. Only a System Manager can add or change these records, unless you give another role rights on them in Role Permissions Manager. That role also needs Select on Customer Group and Mode of Payment, or the rule's lookups find nothing.
| Field | What it does |
|---|---|
| Customer group | The group this rule is for. One rule per group. |
| Switched on | Untick to stop using the rule. The group then takes the rule of the nearest group above it that has one. |
| Rule | Only these payment methods: the till leaves out every other method. Every payment method but these: the till leaves out the methods listed. |
| Payment methods | The methods, as your Mode of Payment records name them, such as Cash, Credit Card or On Account. |
| Words the cashier reads | Shown beside each method left out, such as "Talabat customers pay with Talabat." Blank: "Customers in ⟨group⟩ pay with ⟨methods⟩." or "Not for customers in ⟨group⟩." |

A customer takes their own group's rule. A group with no rule takes the rule of the nearest group above it in your customer group tree. A customer with no rule up the tree keeps every method. A group's own rule replaces the rule above it entirely: a method the rule above leaves out comes back unless the group's own rule leaves it out too. So these two rules give on-account credit to account customers only:
| Customer group | Rule | Payment methods |
|---|---|---|
| All Customer Groups | Every payment method but these | On Account |
| Account customers | Only these payment methods | Cash, Credit Card, On Account |
- Only the methods the till offers are left out. A method that is not on the till's POS Profile is never shown.
- Leaving out your first card method stops card payments at the till: a card reader cannot tell a credit card from a debit card before it charges. Leave out another card method only if your cashiers pick it by hand.
- An exchange pays its new items with store credit. A group whose rule is Only these payment methods can exchange only if the rule lists your store-credit method, such as Store Credit.
- The service reads your rules and your customer groups again within a minute of a change. Until then, the customers of a group you just made keep every method.
Switch the check on
- Search Desk for Retail Extension Subscription and open Payment method rules.
- Read what it is sent, and tick the consent.
- Choose the POS Profiles it answers. With none chosen, it answers every POS Profile.
- Switch it on and save.

What leaves your shop
The app's service runs at payment-method-rules.ivendnext.app, hosted by CitiXsys in the US. After the install, and when you press Connect again, your site sends the service its key from the App library, its address, the check's signing key, and the API key of the app's user.
At each Pay, and before each refund the till pays, your shop sends the priced sale: the store, the POS Profile, the company and the till's day and terminal, the signed-in cashier's user, the customer and their customer group, the price list, the currency and the till's language, the coupons, the details the cashier captured for the sale and for each line, each line's item code, item group, quantity, unit, price, amount and discount, the totals, the payment methods offered and the till's own reference for the sale. On a refund it also sends the original sale (or the order or layaway plan), which kind it was, and how it was paid. No card details are sent.
The service reads your IVENDNEXT PMR Rule records and your customer group tree with the app's user. It keeps them for up to a minute and keeps nothing of a sale. It keeps your site's keys until you remove the app. It writes nothing to your shop.
Limits
- A rule change can take up to a minute to apply.
- Refunds, and the returned items of an exchange, are not checked.
- If you make the app's user a new API key, press Connect again. If you disable the user, switch it back on (or give it a new key), then press Connect again. Until then every sale is flagged for review (or stopped, if you chose Refuse).
- Two methods together in one sale are not checked: the check answers before the cashier picks a method.
- A rule is per customer group. A customer who needs a rule of their own needs a group of their own.
- A POS Profile takes at most three checks, 10 seconds together. This one asks for 3 seconds.
- Until Connect again has sent the app's user, and whenever the service does not answer within 3 seconds, a sale goes on with every method and is flagged for review. A Pay after a quiet spell can take longer than usual.
- Offline, the till cannot ask the service, so it acts as when the service does not answer (above).
- The check does not run when a sale is parked to another till, on a layaway deposit, on an account collection, or in the back office's own POS screen.
- After you install the app again, the check comes in switched off and your rules are gone. Add your rules again (the uninstall exported them to a file). Give the app's user the role IVENDNEXT PMR Integration and its read right again, choose it again as the Application User of IVENDNEXT PMR Rules feed, press Connect again, then switch the check on with its consent.
How to remove it
- In the App library, find the app under Installed and press Details.
- On the app's record, press Export and uninstall and confirm. iVendNext first exports your rule records to a file, and tells the service that the app was removed.
- iVendNext removes the check, the rule records, the feed registration and the role.
- Make a new API key for the app's user, or disable the user, so the key the service had stops working.