Skip to main content

Compliance, built into the flow

Prets does not rely on policy documents to stay compliant. Compliance is enforced through design:
  • customers make all choices themselves;
  • no option is preselected;
  • no advice or suitability logic is applied;
  • decisions stay with providers;
  • every step is traceable.
This keeps your organisation outside regulated activities by construction.

What comes next

When you move forward, documentation covers:
  • security and authentication;
  • API and webhook reference;
  • test and production environments;
  • onboarding and rollout support.
Most teams start with an embed. Integration deepens as volume grows.