These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Fraud Detection System
- Who it's for
- Consumer lending teams
Consumer lending teams
Consumer lending operations need to know who applied, which source evidence was checked and who made the credit decision. The application record gives the Case Analyst a numbered case with a requested amount and purpose. The applicant record holds identity verification and consent details. A Fraud Investigator can examine an application-linked alert before the Credit Reviewer decides.
How Fraud Detection System is set up for you
Applicant verification
Keep a pending identity result visible until the Case Analyst has checked the provider reference and consent time. A declined result needs an understandable handoff to the application owner.
Application review
Assign each application to a person and preserve the submitted and review stages so the team can see what is awaiting action.
Alert investigation
Compare the linked rule, alert score and source evidence for a suspicious application. Record a confirmed or dismissed disposition separately from the credit decision.
Decision attribution
Use a named Credit Reviewer, decision time, reason codes and approved amount when the case reaches its decision.
Consumer lending operations need to know who applied, which source evidence was checked and who made the credit decision. The application record gives the Case Analyst a numbered case with a requested amount and purpose. The applicant record holds identity verification and consent details. A Fraud Investigator can examine an application-linked alert before the Credit Reviewer decides.
Begin with a small group of applicants and applications that includes a verified applicant, a submitted case and an alert with a known rule. Rehearse the handoff from Case Analyst to Fraud Investigator to Credit Reviewer. Ask each person to locate the same application and explain the source material behind the outcome. Then check the approved case's obligation and later repayment trail if your team also manages that work.
Agree how identity results and assessment documents arrive from providers. Use the provider reference as an identifiable source trail and keep the document on the linked application. A case should remain in review when the source material conflicts with the applicant record. That preserves a clear decision path when the team expands beyond the pilot.
Features to start with
Roles on the team
- Case Analyst
- Owns assigned application review and assembles case evidence.
- Fraud Investigator
- Examines alerts against their linked application and records a disposition.
- Credit Reviewer
- Makes an independent application decision after case review.
- Rule Steward
- Maintains the versioned rule register and reviews rule changes.
- Admin
- Configures users and operational access and resolves record setup issues.
Set up Fraud Detection System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.