On the Risk Management page, Facilitators and Referrers can find tools to mitigate boarding and transactional risk.
Merchants and Transactions submitted to the Platform are analyzed for risk mitigation before approval. Noncompliant submissions (based on standards set by Payrix or its Partners) trigger alerts to Platform Risk for action to be taken to prevent malicious behavior. Most risk decision types are applied via Groups by Platform Risk for monitoring purposes.
Risk Alerts can only be configured to 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 are utilized 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
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.
Trigger - Transaction Ticket Size: “High Ticket” (Applied via Group)
Action - Send an “Alert” (notification) and “Hold” [the Target].
Target - The Merchant’s Transaction(s).
By configuring group risk rules based on “High Ticket” transaction size (set as an amount threshold)1, merchants exceeding the threshold will trigger an “Alert” notification for Platform Risk and/or its partners, placing a “Hold”2 on the merchant’s current transactions (pending further review)3.
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.
Risk Queue Status
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.
Tickets that have been marked for review and require further action.
Pending alerts will be marked as “Hold” or “Send Funds to Reserve”.
Alerts that have been approved for boarding or settlement.
Alerts for actions which have been blocked, such as for a transaction with no CVV or that exceeds the allowable transaction limit.
Rules/Decisions are configured by Payrix/Facilitator and Referrers for merchants, which determine when to block a transaction.
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.
Approves the boarding or transaction of a merchant
MARK FOR REVIEW
Marks a merchant for pending further review
Refunds a transaction submitted by a merchant
SEND TO RESERVE
Captures a transaction but sends it to a merchant’s reserve
Logs notes regarding the case or merchant on Portal
Data to Review
MERCHANT NAME AND PORTAL
The merchant name and shortcut to enter the merchant’s Portal
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
The reason code for the alert - for example, max sale amount, capture above auth. amount, etc.
Where the status of a transaction is displayed - common statuses include Held or Reserved.
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.
CVV data was not provided when the merchant entered the card
CVV data was not available via the submission method
CVV information submitted does not match the card brand’s verification system
CVV information matches the card brand’s verification system
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.
Warning: AVS can only be utilized in the United States and Canada.
AVS data was not provided when the merchant entered the card
AVS data was not available for that account via submission method or the card issuer doesn’t support AVS
AVS information submitted does not match the card brand’s verification system
AVS information submitted partially matches the card brand’s verification system
AVS information matches the card brand’s verification system
3D Secure (3DS) Data
3D Secure (3DS) is an XML-based protocol designed as an additional security layer for online credit and debit card transactions.
Visa - Verified by Visa (or) Visa Secure brands
Mastercard - SecureCode
JCB International - J/Secure
American Express American Express SafeKey
3DS data was not verified during the transaction
3DS data was not available for that account via submission method
3DS information matches the card brand’s verification system
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.
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.