Manual review

As a Rule manager user, you have an option to create rules that mark transactions for manual review. These transactions appear in the side navigation under Manual review → Pending review. They are pending manual review and a decision at this point. It is on the gateway or merchant now to decide how to proceed.

You review a transaction by adding your decision to it. You can mark a transaction as good, probably good, probably bad, or bad. If necessary, add a comment to support your decision. Your team members can add further comments to the thread.

• A good transaction doesn't contain any indicators that would suggest illegitimate user behavior.
• A probably good transaction doesn't belong to any fraud patterns, however, you can't say with high certainty that it's a good one. This may occur due to a lack of data, an unknown emerging fraud pattern, etc.
• A probably bad transaction carries one or more suspicious indicators connected to customer behavior, location, etc.
• A bad transaction contains user behavior that is usually associated with e-commerce fraud.

Reviewed transactions move in the side navigation from the section Pending review to the section Reviewed. You see what decision a reviewer took for each transaction, as well as any available comments.

Important: Marking a transaction as reviewed with a specific decision notifies your application accordingly if you've integrated the Fraugster webhook. You receive the webhook notification and can trigger further actions on your end as desired.

Without the webhook integration, marking a transaction as reviewed doesn't trigger any further action. Its status doesn't change automatically.

Review transactions

To review a transaction:

1. Log in to your Fraugster account and navigate to Manual review → Pending review. If you have transactions available for review, the Manual review section in the side navigation is marked with .
2. Select and mark the transaction with one of the available options. Add a review note if necessary.
3. Select SAVE.

It is also possible to review a transaction from the transaction page. A transaction that is pending review shows a notification at the top of the page .

You can add comments to a reviewed transaction at a later stage, or change your decision if necessary. Select Update review on the transaction page and save your changes when done. We keep a log of all updates introduced through manual review:

Reviewed transactions

When you review a transaction, it moves to the section Reviewed automatically. Go to Reviewed to view all reviewed transactions for a given period of time. Choose a different time range in the upper-left corner of the screen to update what you see. A quick range selection is also available, for example Last 30 days or Last quarter.

info

Use to pin the date and merchant filters across all pages of your account where the filters apply. For the merchant filter, the pin becomes visible when you select at least one merchant.

You can also filter transactions by the reviewer. Select the filter Reviewed by and choose the desired names.

Webhook notifications

Fraugster uses webhooks to notify your application when an event happens in your Fraugster account. A successful integration allows you to receive event notifications so your application can automatically trigger specific actions.

You can use the webhook tool to get notified when a transaction has been manually reviewed and given a decision. Read more in Fraugster webhook and consider adding webhooks to your Fraugster integration for a better experience with manual review.

Priority

When multiple rules within the same ruleset hit a transaction, Fraugster applies the following prioritization flow to determine which rule should take priority. The order of events is relevant here:

1. Check rule vs. list priority. Lists have priority over rules. Approve lists take priority over decline lists.
2. Check the priority of each rule – high, medium, low.
3. Check the action priority (high to low) – approve → decline → manual review → psd2 → custom.
4. Check the custom priority – within the custom group only.
5. Check the ID of the rule – the rule with the lower ID (i.e. the rule created earlier in time) takes priority over its younger counterpart.

Want to give it a try?

If you don't have access to manual review today, but would like to start using it, please contact our Customer Support team at [email protected].