PRICES & SCOPE
Start with a project.
Scale what proves useful.
Fixed-scope analysis and testing for immediate questions. Monthly packages for ongoing AI payment screening. All prices exclude VAT.
PROJECTS · PAID ONCE
A question answered,
for a fee agreed first.
A defined piece of work with a fixed scope and a fixed price. It ends with something in your hands. Nothing recurs, and nothing is committed to.
01 / INVESTIGATE A DISCREPANCY
Reconciliation diagnostic
Get a clear picture of where your order and payment records disagree.
From €1,200 / project
- One purchase flow, up to two sources
- Up to 10,000 records over 30 days
- One currency; supplied CSV/JSON
- Findings, evidence and a review session
Scope my analysis ↗
Final fixed fee after reviewing formats. Data cleanup and custom connectors quoted separately.
02 / CHECK BEFORE RELEASE
Integration validation
Find reproducible failures in a defined checkout or payment flow.
From €1,800 / project
- One integration in your test environment
- Up to ten agreed test scenarios
- Findings linked to reproducible evidence
- One retest of the agreed fixes
Scope my testing ↗
Test coverage, access and retest window agreed before work starts. Remediation quoted separately.
What “from” means
The starting fees cover the scope listed above when the supplied data or test environment is ready. We review formats, access and required work before issuing a fixed-fee proposal. Cleanup, custom connectors, remediation and additional sources are quoted separately. Recurring reconciliation is scoped after the initial analysis.
Example screening budget: five integration days at €600 plus twelve Pilot months at €290 totals €6,480 excluding VAT. This is an illustration, not a required annual commitment.
SUBSCRIPTION · PAID EVERY MONTH
An ongoing control,
priced by what it decides.
Not a project: this runs for as long as your integration calls it, and is billed every month on the decisions it returned.
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.
Start on pay as you go and you commit to nothing: you are billed for the decisions you actually asked for, with a floor of €90 a month. Past roughly 650 transactions a month the Pilot package costs less than the same usage would, and you can move across at any point.
| What you get |
Pay as you goNo commitment, billed on what you use€0.45 / transactionMinimum €90 a month · cancel any timeRequest a proposal |
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. | Billed per use | 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. | No volume to exceed | 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 | 1 | Agreed |
| PoliciesOne set of rules, or several for different flows or markets. | 1 | 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 | 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. | — | — | — | ✓ |
These prices are also published as JSON at api.trustedpai.com/v1/pricing, for integrations that need a machine-readable price list.
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. The monthly minimum covers account operation and the support described above.
LAUNCH PRICING
Launch terms, in writing.
The rates above apply to the first ten clients and are held for twelve months from the start of the engagement. The eleventh client pays the reference price, and nobody who started earlier is moved onto it.
Discuss your integration →
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.
01 / DISCOVER
Understand the flow
How your checkout works, who takes the payment, what formats your records are in, and where a decision is made today.
02 / CONNECT
Wire it up
Access tokens, your signing keys loaded, the call placed from your system, the webhook configured and verified with a test event.
03 / DECIDE
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.
04 / VALIDATE
Run your own cases
Your real situations put through the engine, and every outcome compared against what you expected to happen.
05 / HAND OVER
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.
Your team owns the spending policy. We help translate it into explicit limits and test the expected decisions before the integration goes live.
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. Your integration must handle API latency, unavailable dependencies and held decisions before executing a payment.
- A recommendation is not an execution. Your integration decides what to do with a decision; we answer the question and return it to you.