Flag suspected fraud

The fraud flag is a governed boolean on the loan. Setting it records that the account is under fraud suspicion; it is not a final adjudication, and it does not silently rewrite customer or loan history. The investigation itself—evidence, ownership, decisions—lives in a servicing case, and any operational blocks are separate, explicit restrictions.

Set the flag

The flag is toggled with the governed command markAsFraud on the loan route. A human call carries LendEasy-Case naming an open case when case management is enabled; without it the call is rejected before execution.

curl -X PUT "$BASE/v1/loans/7204?command=markAsFraud" \
  -H "Authorization: Bearer $TOKEN" \
  -H "LendEasy-Tenant: demo-lender" \
  -H "LendEasy-Case: case_HBR_FRAUD_6" \
  -H "Content-Type: application/json" \
  -d '{
    "fraud": true
  }'

{
  "officeId": 1,
  "clientId": 412,
  "loanId": 7204,
  "resourceId": 7204,
  "changes": {
    "fraud": true
  }
}

The execution writes a governance record readable at GET /v1/loans/7204/governance-records, and maker-checker can park the command for a second approver.

The flag is not the investigation

The case records what is suspected, the evidence and source, observation time, urgency, and the specialist who owns the decision. Interactions, documents, and identity-verification outcomes attach there. Broad exports use neutral language such as “suspected” until a finding is confirmed—the boolean marks the loan; it does not narrate a conclusion.

Operational response is explicit

The flag itself does not block anything. Apply the intended controls as typed restrictions on the customer, scoped to the loan where appropriate:

• PAYMENT_HOLD while payment authenticity is in question;
• DISBURSEMENT_HOLD to stop outbound funding;
• AUTOPAY_HOLD to pause enrollments; and
• COMMUNICATION_HOLD where contact must pause during review.

Each restriction is its own governed call with its own governance record, and each is cleared explicitly when the basis ends. Essential borrower access and legally required communications are evaluated per restriction rather than disabled by a blanket status.

Resolution

• Not confirmed — clear the flag with the same route and { "fraud": false }, clear the linked restrictions, and record why they existed in the case.
• Confirmed — keep the flag, apply the approved response plan, and route any reporting, correction, or restitution through its own governed actions.

Either way the governance ledger preserves who set and cleared the flag, under which case, and when.

Correction and privacy

Evidence is access-controlled and retention-managed in the case. A data-correction or privacy request does not erase legally retained fraud evidence, but exports and decisions respect applicable access and minimization policy.