Onboard with confidence

During onboarding, our anti Fraud Engine runs thorough validation checks to verify key details such as:

• Identity verification
• Bank account ownership
• Blacklist screening
• Duplicate signature detection
• Credit checks
• Account utilization monitoring

This ensures you onboard only legitimate customers, giving you total peace of mind from the start.

Mandate checks for added security

Once a mandate is signed, additional checks can be performed to ensure everything is in order. Based on these checks, a mandate can be:

• Automatically refused
• Flagged for manual intervention
• Approved after verification

This keeps your business secure every step of the way.

Global protection across industries

From e-commerce and energy to mobility and beyond, our anti Fraud Engine can be configured to adapt to your industry and keeps you protected at every step.

Partnered with global security tools like:

• itsme (Belgium identity verification)
• iDIN (Netherlands bank verification)
• Mastercard and Visa (card verification)
• IBAN-Name Check providers
• VAT Check services
• Credit Check companies

We ensure seamless and secure validations worldwide.

How fraud rules work

Fraud rules use an if-then logic to automatically detect suspicious activity and take action.

Setting up fraud rules

Fraud rules are organized into two categories: Twikey-specific checks on your documents and customer data, and Account Checks (AIS) based on bank account information.

Condition combination

When you set up a rule, you choose how conditions are evaluated:

• Any — The rule triggers if at least one condition is true (OR logic)
• All — The rule triggers only if all conditions are true simultaneously (AND logic)

Condition operators

All conditions support the following operators:

• is equal to — Exact match
• is not equal to — Does not match
• is less than — Below a threshold value
• is more than — Above a threshold value
• is between — Within a range (requires lower and upper bounds)

Twikey-specific fraud rules

These rules analyze documents, signatures, and IBANs processed through Twikey:

• Number of documents with the same signature — Detects when multiple documents have been signed by the same person. Use this to flag suspicious patterns of reuse. Threshold operators apply.
• Number of documents with the same IBAN — Identifies when multiple documents reference the same bank account. Useful for detecting coordinated fraud. Threshold operators apply.
• Number of customers with the same signature — Flags when the same signature appears across multiple customer accounts. Threshold operators apply.
• Number of customers with the same IBAN — Detects when different customers share a bank account. Threshold operators apply.
• Signature is on the blacklist — Checks if the signature matches a known fraudulent signature in your blacklist.
• IBAN is registered on the blacklist — Checks if the IBAN matches a known fraudulent account in your blacklist.

Account Checks (AIS)

Account Information Services (AIS) provides real-time access to your customer's bank account data via PSD2-compliant providers. This includes transaction history, account balance, and account status. Twikey uses AIS to verify customer legitimacy and detect risky patterns automatically.

These rules monitor the customer's bank account behavior and financial activity:

• Number of transactions on the account — Monitors transaction volume. Use threshold operators to flag accounts with unusual activity patterns. Threshold operators apply.
• Number of Direct Debit transactions linked to the account — Counts successful Direct Debit transactions. Threshold operators apply.
• Number of failed Direct Debit transactions linked to the account — Monitors payment failures. High failure rates may indicate risk. Threshold operators apply.
• Account balance — Checks the account's available balance. Threshold operators apply.

Actions when fraud is detected

When a rule is triggered, you can automatically:

• Cancel agreement — Immediately reject the agreement
• Mark as awaiting approval — Flag for manual review
• Send email to the document agent — Notify the responsible team member
• Mark as fraud — Tag the agreement as fraudulent
• Send webhook — Trigger external system notification

Best practices

• Combine multiple conditions for more accurate fraud detection
• Start with "Mark as awaiting approval" to avoid false positives
• Use webhooks to integrate with your existing fraud management systems
• Regularly review flagged agreements to fine-tune your rules
• Set threshold operators carefully — too strict rules may block legitimate customers, too loose rules may miss fraud

Need help? Contact Twikey Support to configure fraud rules for your specific industry and risk profile.