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

# Compliance in Practice

> How compliance works in day-to-day operations

## Provider-owned decisions

Funding decisions are never influenced by Prets.

Providers:

* define criteria;
* perform checks;
* approve or reject applications;
* issue contracts.

Prets only ensures applications are complete, structured, and clearly submitted.

## Traceability and auditability

Every step in the Prets flow is traceable. This includes:

* customer inputs;
* calculation assumptions;
* documents submitted;
* timestamps and confirmations.

This supports audits, complaints handling, and internal reviews — without additional work for merchants.

## Human support, without advice

When customers struggle, help is available.

Prets allows for human-in-the-loop support that is:

* procedural;
* technical;
* explanatory.

Support staff do not provide advice or steer decisions. This is especially important for less digital-savvy or vulnerable customers.

## Designed to keep merchants safe

Prets helps merchants:

* avoid regulated advice activities;
* reduce manual explanations that cross boundaries;
* rely on a consistent, compliant process.

Compliance is handled once — centrally — and applied consistently across all customers.

## Calm, consistent, defensible

Prets is built to stand up to scrutiny. Not through legal language, but through:

* clear boundaries;
* neutral presentation;
* customer-led decisions;
* provider-owned outcomes.

This makes Prets safe to scale — commercially and operationally.