There are two ways that a transaction can be set aside for manual review:
- The transaction reaches the amber threshold that has been established by the merchant.
- The transaction triggers a risk check which has an amber override.
Establishing an Amber Threshold
In the RevenueProtect system, any payment that reaches a risk score of 100 or more is refused. Merchants can also establish an amber threshold. After this score is reached, the transaction is sent for manual review. Note that if the score reaches 100, it is still be refused and not sent for manual review.
For example, if a merchant establishes a manual review threshold of 60, the behavior of the account follows this pattern:
The Amber threshold value is established at the merchant account level on the primary risk configuration page.
Establishing an Amber Override
Each risk rule can have the amber override option enabled. When this option is enabled, the transaction is sent for manual review whenever that rule was triggered. Note that the transaction is still refused if the overall risk score still reaches 100.
A common way to use the amber override is to establish monetary thresholds for manual review by utilizing the Transaction Amount Check. For example, a merchant can always review transactions over $1,000 by establishing that amount in the check and giving the check an amber override.
Manual Review Expiration
Merchants have 7 calendar days to accept or reject a payment after it was selected for manual review. If the review has not been actioned in that 7-day window, the payment is automatically accepted and the funds are captured. These reviews are logged as expired.