> ## Documentation Index
> Fetch the complete documentation index at: https://docs.centsless.org/llms.txt
> Use this file to discover all available pages before exploring further.

# Compliance, audit, and fraud detection overview

> Every Centsless transaction produces a compliance status, fraud score, and audit hash. Use these endpoints to monitor patterns, detect abuse, and export regulatory evidence.

Every transaction processed by Centsless produces a compliance status, gets appended to the immutable hash chain, and receives a real-time fraud score. These signals are computed at transaction time and stored permanently — you cannot process a transaction without generating a compliance record. The endpoints in this section let you monitor aggregate compliance patterns, detect abuse, and export evidence for regulatory submissions.

## Compliance endpoints

<CardGroup cols={3}>
  <Card title="Export" icon="file-csv" href="/api-reference/compliance/export">
    Export transactions as a CSV file for regulatory reporting. Supports standard, full, and summary modes.
  </Card>

  <Card title="Audit logs" icon="shield-check" href="/api-reference/compliance/audit-logs">
    Query the immutable audit log and verify hash chain integrity to detect tampering.
  </Card>

  <Card title="Fraud" icon="triangle-exclamation" href="/api-reference/compliance/fraud">
    Retrieve merchant risk profiles and a ranked fraud overview across all merchants.
  </Card>
</CardGroup>

## Compliance status values

Every transaction receives one of three compliance statuses:

| Status | Meaning                                                                                                                                                                              |
| ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `PASS` | All compliance checks passed. The rounding calculation, jurisdiction match, and fraud score are within normal parameters.                                                            |
| `WARN` | One or more checks raised a soft flag. The transaction was processed, but the result warrants review — for example, a borderline fraud score or an unverified jurisdiction fallback. |
| `FAIL` | A critical compliance check failed. The transaction may have been blocked or may require immediate attention.                                                                        |

## Void analytics

**GET /analytics/voids** returns aggregate void statistics: total void count, void rate, amounts, and normalization check results that flag whether refunded rounding deltas correctly reverse the original transaction.

**GET /analytics/void-abuse** analyzes void patterns for potential abuse, including merchants with high void rates, normalization failures, and suspicious timing patterns such as voids clustered immediately before or after shift changes.

## Override report

**GET /overrides/report** returns all rounding overrides across your account with full employee attribution, reason codes, and the delta between the calculated rounding amount and the overridden value. Use this to audit whether manager overrides are being applied appropriately or to detect normalization abuse.