Using The Risk Management Page

Partners can find tools to mitigate boarding and transactional risk on the Risk Management page.

Alerts

Merchants and transactions submitted to the Platform are analyzed for risk mitigation before approval. Noncompliant submissions (based on standards set by Worldpay for Platforms or its Partners) trigger alerts to Platform Risk for action to be taken to prevent malicious behavior. Most risk decision types are applied through Groups by Platform Risk for monitoring purposes.

Notes
Risk Alerts can be configured to only trigger a follow-up action for transaction or Merchant actions.
Web Alerts can be configured for any action taken on the Platform as a notification only.

Risk Decisions

Risk Decisions are used to create automated risk parameters and guidelines that can even block transactions from processing. The basic workflow for a Risk Decision is:

Trigger → Action → Target

See Using Decisions for Risk Mitigation to learn how to set up Risk Decisions.

The following is an example of a Risk Decision flow being applied to enable Risk Alerts:

Example: A transaction has exceeded the Merchant’s designated “High Ticket” transaction amount threshold. As a result, we would like to be notified that this has happened and we would like to hold the transaction until we have time to manually review the transaction for suspicious activity.

Explained:

Trigger: Transaction Ticket Size: “High Ticket” (applied through Group)
Action: Send an Alert (notification) and Hold (the Target).
Target: The Merchant’s transactions.

Result:

By configuring group risk rules based on “High Ticket” transaction size (set as an amount threshold)¹, merchants exceeding the threshold will trigger an Alert notification for Platform Risk and its partners, placing a Hold² on the merchant’s current transactions (pending further review)³.

Alert Queues and Statuses

Queues are a list of alerts for a Risk Analyst to review.

Merchant: Flagged accounts that have been submitted for boarding within the Portal
Transaction: Flagged based on the decision criteria in place

Each Alert within a Queue is tagged with a status to indicate its progress. The following table describes each status:

Risk Queue Status	Description
Open	The most recent alerts in the queue - within each sub-queue, an analyst can make immediate decisions. With this, analysts can make quick decisions for common flags and review other cases in more detail.
Reviewed	Tickets that have been marked for review and require further action. Note: Pending alerts will be marked as Hold or Send Funds to Reserve.
Approved	Alerts that have been approved for boarding or settlement.
Blocked	Alerts for actions that have been blocked, such as for a transaction with no CVV or that exceeds the allowable transaction limit. Note: Rules and Decisions are configured by Worldpay for Platforms and its Partners for merchants, which determine when to block a transaction.

Reviewing Tickets

As tickets are reviewed, there are a number of actions to take depending on the alert type. Each of these actions will have an impact on a merchant’s account and should be taken with caution.

Action Option	Action Outcome
APPROVE	Approves the boarding or transaction of a merchant
MARK FOR REVIEW	Marks a merchant for pending further review
REFUND	Refunds a transaction submitted by a merchant
SEND TO RESERVE	Captures a transaction but sends it to a merchant’s reserve
ADD NOTE	Logs notes regarding the case or merchant on Portal

Data to Review

Field	Description
MERCHANT NAME AND PORTAL	The merchant name and shortcut to enter the merchant’s Portal
ACTIVE DISPUTES	Indicates if a merchant has any active disputes in our system
TRANSACTION RISK SCORE	Generated when a transaction is reviewed by the Risk AI system; the closer the number is to 100, the higher the confidence in the transaction.
ALERT CODE	The reason code for the alert; for example, max sale amount or capture above authorization amount
STATUS	Where the status of a transaction is displayed; common statuses include Held or Reserved.

CVV Data

The Card Verification Value (CVV) Number on a credit or debit card is a 3-digit number located on the back of Visa®, Mastercard®, and Discover® branded credit and debit cards.

On an American Express® branded card, it is a 4-digit numeric code on the front of the card.

Field	Description
NOT PROVIDED	CVV data was not provided when the merchant entered the card
UNAVAILABLE	CVV data was not available via the submission method
MISMATCH	CVV information submitted does not match the card brand’s verification system
MATCH	CVV information matches the card brand’s verification system

AVS Data

The Address Verification Service (AVS) is used as a fraud prevention tool in card-not-present (CNP) transactions. AVS compares the billing address used in the transaction with the issuing bank’s address information for the cardholder.

Important!
AVS can only be used in the United States and Canada.

Field	Description
NOT PROVIDED	AVS data was not provided when the merchant entered the card
UNAVAILABLE	AVS data was not available for that account via submission method or the card issuer doesn’t support AVS
MISMATCH	AVS information submitted does not match the card brand’s verification system
PARTIAL MATCH	AVS information submitted partially matches the card brand’s verification system
MATCH	AVS information matches the card brand’s verification system

Alert Profile

When a transaction is selected, you will be taken to an Alert profile with an overview of the flagged transaction details. To review a transaction within the Portal, use the following:

Customer Information: Any information on the cardholder that was sent to the Portal
Transaction Information: Information on a transaction as generated by the Portal
Payment Information: The cardholder’s information that was used in the transaction

Alerts

Risk Factors: All alerts associated with this transaction
Holds: Shows the merchant’s transactions that are on hold
Customer Transactions: Any related transactions for this cardholder