Skip to main content
All CollectionsGetting Started
Understanding the Decision Engine
Understanding the Decision Engine

Learn more about Inscribe’s default fraud rules and available customization options.

Alice Gregson avatar
Written by Alice Gregson
Updated over a week ago

Inscribe's Decision Engine is comprised of default fraud rules, and features to help you set custom document checks and fraud rules. As a best practice, we recommend you start by leveraging our default fraud rules along with custom checks, then modify fraud rules over time as needed. Learn more about:

Custom Document Checks

Document checks are a simple, automated way of checking the properties of the documents you receive. Whether you only accept utility bills that were issued within the last two months or driver’s licenses that haven't yet expired, you can enforce these requirements without worrying about the operational overhead.

Setting up a custom document check can be done with just a few clicks from the settings page. In the screenshot below, we show an example configuration for requesting documents via Collect. This check ensures that the document submitted via the Collect session is a bank statement. If the document submitted is not a bank statement, it will be rejected and the customer will be notified.

Default Fraud Rules

Fraud rules are sets of conditions that determine if a document is fraudulent. Over 25 default conditions are automatically enabled by Inscribe to detect any suspicious activity on a document. These conditions or rules include detection for font issues, overlaid text, document software, flattened PDFs, date mismatches, and much more. To see the default rules that have been set, go to the fraud rules section of the settings page.

Custom Fraud Rules

While we recommend using the default fraud rules and detectors set by Inscribe, you can disable or modify these rules based on your preferences.

Setting up a custom fraud rule can be done with just a few clicks from the settings page by selecting the the New rule button. In the screenshot below, we show an example configuration for invoices. Specifically, any document submitted that's an invoice that's been seen before, will be marked as fraudulent.

Did this answer your question?