Resources
Read how it works before you take our word for it.
Everything public about FRAPE, in one place: guides, reference material, the cost model and plain answers.
Library
Guides and reference
- GuideThe decision flow, gate by gateWhat runs, in which order, and when each stage ends the work early.
- ReferenceScoring API exampleRequest, response fields, short-circuits and problem+json errors.
- ModelEngineering cost modelTables, sensitivity grid, calculator and every assumption with its source.
- ControlsSecurity & privacyCard-data refusal, tenant isolation, minimised inputs and credential handling.
- OverviewPlatform modulesRules and policy, Decision Core, enrichment, identity, cases and operations.
- Use casesBy industry and by momentHow the same engine applies from sign-up to payout.
FAQ
Frequently asked questions
What is the Decision Core?
FRAPE’s advisory scoring component. It is consulted only for events that rules cannot settle, receives a minimised state without card data or raw contact details, and returns an advisory score. The deterministic policy decides what that score means.
Can the Decision Core approve a transaction on its own?
No. The policy engine makes every final decision. If the Decision Core is unavailable, the organisation’s configured fallback applies, and that fallback can never be an automatic approval.
Do you accept card numbers?
No. Any request containing a card number or CVV is rejected. Cards are identified by a fingerprint, the BIN and the last four digits.
How are tenants kept apart?
Every tenant-scoped table is protected by database row-level security keyed on the organisation, and the application checks the organisation on every request as well.
What happens when an enrichment provider is slow or down?
Each provider call has its own timeout and circuit breaker. A failure marks that capability unavailable and scoring continues; rules never treat unavailable data as a match.
Are the numbers on the Economics page prices?
No. They are engineering cost estimates for running the platform, generated from a versioned cost model. They are not commercial pricing, quotes or offers.
Does this website track me?
No. It is a static site with no cookies, no analytics and no third-party requests. Fonts are served from the site itself.
Design partners
Help shape what FRAPE decides next.
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.