Rule reference
Define the scheme, scope, conditions, outcome, and activation profiles for a rule.
Use this reference when specifying configuration to the implementations team. Rules reference native fields exposed for the scheme request and any applicable service enrichment.
Scope
Specify the scheme and endpoint, then the wallet or token requestor. Mastercard wallet identifiers and Visa token requestor identifiers are different namespaces; use the identifier supplied for your programme. A custom requestor can be scoped by its agreed identifier. All Wallets rules run after wallet-specific rules.
Condition operators
| Operator | Purpose |
|---|---|
| Equals / Not Equals | Compare a field with a configured value |
| Contains | Match contained text |
| Greater Than / Less Than | Compare numeric values |
| Is Present | Check that the field exists |
| Is Empty | Check for a missing or empty field |
Agree how conditions are combined, the field type, value, and handling of absent data for your scheme when configuring a rule.
Outcome and methods
Choose approve, decline, or additional authentication. A step-up rule selects the relevant activation profiles where methods are returned. Visa Approve Provisioning does not itself return methods; its method-selection request is configured separately.
Required fallback
A rule set must have a default outcome. A yellow fallback selects its own default activation profiles. See building rules for ordering and validation.
Updated 20 days ago