> For the complete documentation index, see [llms.txt](https://docs.peakcommerce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peakcommerce.com/integrations/fraud-and-risk/seon-fraud-prevention.md).

# SEON

PeakCommerce integrates with **SEON** to screen signups and orders for fraud before they're accepted. SEON evaluates an applicant from their email, phone, IP, device, and billing details and returns a fraud score plus the signals (applied rules) behind it — so you can stop bad orders before they ever become a subscription.

## What it is

SEON is a fraud- and risk-intelligence provider. In PeakCommerce it runs as a **`fraud_check` commerce action** on a journey step, powered by a configured SEON integration. It is an opt-in, journey-configured check — you place it where it matters (signup, checkout) rather than running it as a blanket global guardrail.

## What you can do with it

* **Score every applicant in real time** — when a customer reaches the fraud-check step, PeakCommerce calls SEON's Fraud API and receives a score and state.
* **Branch on the result** — the action returns a decision (allow / block, with an unknown-state fail-open) that journey logic acts on: proceed, send to manual review, or decline. Two decision modes are supported — **score mode** (block at or above your configured threshold) and **state mode** (proceed on APPROVE/REVIEW, block on DECLINE).
* **Keep a record you can act on** — the fraud score and state are persisted on the customer, and the result (transaction id, score, state, applied rules) can be written back to your billing system, e.g. Zuora's `SeonFraudResult__c`, for later reference.

## How it fits

Connect a SEON integration (your license key, base URL), test the connection, then add a fraud-check action to the relevant journey steps and set the threshold or decision mode. The check is one action among others on the step, so it composes with the rest of your commerce logic.

## Who and when

Set up by an admin with integrations permissions; configured by whoever owns the journey. Add it to any flow where a fraudulent signup or order would be costly.

## Gotchas

SEON is fraud-only — it carries no catalog, accounts, or billing. Tune the threshold to your risk tolerance: too low blocks good customers, too high lets fraud through.

See also: [Fraud and risk integrations](/integrations/fraud-and-risk/fraud-and-risk.md). The fraud-check step is a *commerce action* — see the Commerce Actions guide for how actions run on journey steps.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.peakcommerce.com/integrations/fraud-and-risk/seon-fraud-prevention.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
