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. The fraud-check step is a commerce action — see the Commerce Actions guide for how actions run on journey steps.
Last updated
Was this helpful?
