Lotus allows partners to define transaction rules at multiple levels—platform, co-applicant, affiliate, BIN range, or individual card. Controls can restrict usage by merchant type, location, amount, and more. Updates are applied in real time via REST API, ensuring immediate enforcement on the next transaction.

---

List of Rules Copied!

Each rule defines conditions based on several parameters, such as:

• Authorized amount: Daily, weekly, or monthly limits on authorized amounts.

• MCC (Merchant Category Code): Rules can be created based on MCCs, allowing configuration of transaction limits per specific merchant categories.

• Entry mode: Rules can be defined for specific entry modes (e.g., swipe, chip, contactless).

• Business Scope: Rules can be filtered to apply on Domestic, International transactions or both.

• For MCC or entry mode-based rules, the system supports the definition of:

  1. Maximum allowed amount per transaction.

  2. A specific time frame during which the rule is enforced.

  3. These rules ensure fine-grained control over transaction authorization, enhancing security and flexibility in transaction management.

---

Rules Hierarchy Copied!

Rules can be defined at different levels, the lower the rule value the higher its priority. The Lotus platform has processor level up to PAN level. If any condition is not met, the transaction will be denied.

Rule Name	Level	Description
Girasol	0	Rules generate by Girasol
Issuer	1	Rules applied to issuer
BIN	2	Rules applied to BIN
Sub-Issuer	3	Rules applied to sub-issuer
BIN-Range	4	Rules applied to bin range
PAN	5	Rules applied to PAN