Understand the flow
How your checkout works, who takes the payment, what formats your records are in, and where a decision is made today.
WHAT IT COSTS
Priced by what
you screen.
A screened transaction is one decision returned by the engine, counted at the moment the decision is stored. Volume is measured per calendar month in UTC, and you can read the count yourself at any time from your workspace — the same number the invoice is based on.
| What you get | PilotUp to 1,000 screened transactions a month€290 / monthReference €600 · held 12 monthsRequest a proposal | StandardUp to 10,000 screened transactions a month€950 / monthReference €2,000 · held 12 monthsRequest a proposal | VolumeUp to 100,000 screened transactions a month€2,900 / monthReference €6,000 · held 12 monthsRequest a proposal |
|---|---|---|---|
| What is counted | |||
| Screened transactions a monthOne decision returned by the engine, counted when the decision is stored. | 1,000 | 10,000 | 100,000 |
| Usage you can read yourselfThe same figure the invoice is based on, visible in your workspace at any time. | ✓ | ✓ | ✓ |
| Exceeding the volumeA commercial conversation, never an interruption of your payments. | Never blocks | Never blocks | Never blocks |
| What comes back | |||
| Policy evaluation on every requestYour limits, your accepted merchants, your thresholds — applied to each decision. | ✓ | ✓ | ✓ |
| Evidence packageYour engineers can recompute the result offline, without a key and without us. | ✓ | ✓ | ✓ |
| Human review queueHeld decisions land in a queue a person resolves, with the reason attached. | — | ✓ | ✓ |
| Policy versioningEvery change to a rule recorded, with what it was before and who changed it. | — | ✓ | ✓ |
| Decision qualityWhat you reported back about outcomes, measured against what was recommended. | — | ✓ | ✓ |
| How it connects | |||
| EnvironmentsSeparate configurations, for example test and production. | 1 | 1 | Agreed |
| PoliciesOne set of rules, or several for different flows or markets. | 1 | Multiple | Multiple |
| Webhook deliverySigned events pushed to your endpoint, retried until you acknowledge them. | — | — | ✓ |
| Full data exportEverything held about you, in a format you can read without our software. | — | — | ✓ |
| Retention you configureHow long your records are kept, set by you rather than by us. | — | — | ✓ |
| Working with us | |||
| Email supportA person answering, not a ticket queue. | 2 working days | 1 working day | Agreed |
| Monthly read of your decisionsWhat the engine decided, what it held, and what that says about your rules. | — | ✓ | ✓ |
| Response times in writingAn availability commitment agreed before the engagement starts, not implied. | — | — | ✓ |
Above 100,000 transactions a month, or where your records need handling we have not described here, the work is scoped and quoted. Prices exclude VAT.
LAUNCH PRICING
These are the first ten prices.
The rates above apply to the first ten clients and are held for twelve months from the start of the engagement. They reflect the stage this service is at, not the work involved. The eleventh client pays the reference price, and nobody who started earlier is moved onto it.
BEFORE THE FIRST DECISION
The integration,
and what it involves.
The monthly package pays for the service running. Getting your system to the point where it can use one is separate work, done with your team, and charged for the days it takes.
€600 per day. A typical integration is five days, laid out below. If yours needs more, you are told before it starts, not afterwards.
Wire it up
Access tokens, your signing keys loaded, the call placed from your system, the webhook configured and verified with a test event.
Write the policy
Per-transaction and daily limits, accepted and excluded merchants, the amount above which a person must be involved, the currency you settle in.
Run your own cases
Your real situations put through the engine, and every outcome compared against what you expected to happen.
Leave it with your team
Who watches what, how to read an evidence package, and what to do when a decision comes back held.
The third day is the one that matters.
Connecting a system is ordinary engineering and any competent team could do it. Deciding the amount below which a purchase proceeds without a person, which merchants are acceptable, and when to stop and ask — that is a risk decision, not a technical one, and it is what thirty years of building financial software is for.
STATED PLAINLY
What these prices
do not include.
A price list that only lists what you get is half a price list. These are the limits as they stand today, written here rather than discovered later.
- Exceeding your volume does not stop anything. The meter records it and we talk about it. Your payments are never interrupted because of a commercial threshold.
- There is no availability commitment unless we agree one in writing. On the Volume package that agreement is part of the engagement; on the others it is not implied.
- Billing is by invoice, not by card. There is no self-service checkout, no automatic renewal and nothing stored that could charge you without an agreement.
- TrustedPAI sits beside your payment flow, never inside it. Funds never pass through us, so nothing here can delay a settlement or widen the scope of your card-data obligations.
- A recommendation is not an execution. Your integration decides what to do with a decision; we answer the question and return it to you.
NO PRICE FITS EVERY FLOW
Tell us what you run.
Leave with a real number.
Describe your checkout, your volumes and the records you hold. You get a scope, a deliverable and a price before any work starts — or an honest answer that this is not the right fit.