Solutions
FRAPE is configured per organisation: rules, lists, thresholds and fallback behaviour are yours. Below is how that plays out by industry and by moment in the customer lifecycle. Examples are illustrative.
By industry
Score card-not-present payments for many merchants from one platform, with each merchant kept in its own tenant and its own policy.
Two-sided risk: fake sellers on one side, stolen payment methods on the other, and payouts that need a second look.
Applications, logins and money movement on one identity graph, so a profile change before a withdrawal is seen in context.
Instant delivery leaves no time for manual review on every order, so rules settle the obvious cases and queues take the rest.
Stop free-trial farming and card testing at sign-up without adding friction for the customers you want to keep.
By moment
type: signup
Repeat and throwaway identities, multi-accounting, promotion abuse.
Catch throwaway and repeat identities before they get an account: alias reuse, device history and list hits.
Device already linked to several recent sign-ups → signal rule raises the score; policy asks for a challenge.
type: login
Credential stuffing and account takeover.
Spot takeover attempts from new devices, unusual networks and bursts of attempts across accounts.
Burst of logins for one identity from a new device and network → REVIEW, with the reasons recorded.
type: account_update
Takeover follow-through: changed email, phone or payout details.
Treat changes to email, phone or payout details as the high-risk moments they are, with step-up when needed.
Payout details changed minutes after a login from a new device → step-up challenge before the change sticks.
type: payment
Stolen cards, card testing, mismatched geography.
Score a purchase by card fingerprint, BIN, device and velocity — never by card number, which is refused.
Card fingerprint on the organisation’s blocklist → terminal rule declines with no provider or Decision Core call.
type: payout
Cash-out of compromised or synthetic accounts.
Hold money movement that does not fit the identity’s history before it leaves the platform.
First payout to new details on a young identity → REVIEW and an alert for the analyst queue.
Design partners
We are working with a small number of teams who score payments, sign-ups, logins or payouts and want decisions they can explain line by line. Bring your rules and your edge cases.