Decision
With Trigger and Rules defined, a scenario evaluation results in a global score that can be tedious to interpret: the amplitude of scores evolves over the lifetime of a scenario, and different scenarios may use different scales for scoring.
In the Marble mental model, a decision is characterized by an Outcome, which can be: Approve, Review, or Decline. This approach is more convenient for use in decision workflows.
To illustrate this, consider these examples:
- Decision taken by a scenario triggered for each card transaction payout:
- Approve: This triggers a frictionless transaction approval.
- Review: This triggers a 3DS challenge.
- Decline: This declines the transaction.
- Decision taken by a scenario triggered for each SEPA transaction payout:
- Approve: This triggers a frictionless transaction approval.
- Review: This suspends the transaction and requires a manual review.
- Decline: This declines the transaction.
To convert the global score into an outcome, a scenario defines two thresholds:
- A maximum score until which the outcome will be Approve.
- A maximum score until which the outcome will be Review.
It is better illustrated by this image
You can adapt these thresholds during the lifetime of a scenario. Adding rules may raise the global score, and you can change thresholds to curate the outcome without impacting workflows based on those outcomes.
In some cases, only two of the three possible outcomes may be useful and used in a scenario.
For instance, some types of transactions may be either approved or reviewed, while other types may be either approved to rejected (without an option for manual review).
Updated 3 months ago