Praesia - Give your AI agents the ability to pay safely
Praesia Early access

European payment infrastructure for AI agents

Give your AI agents the ability to pay safely

Request early access

Bank transfers (incl. SEPA) · Card payments · Stablecoins · via MCP, SDK, CLI or API

console.praesia.eu

Mandate · Suppliersactive

€41,220 / €90,000 per month

agent-suppliers-03 verified badge

{{ cAmount }} {{ cBenef }}

{{ icon1 }} Identity

verified agent badge

{{ ms1 }}
{{ icon2 }} Mandate

{{ det2 }}

{{ ms2 }}
{{ icon3 }} Intent

consistent with the mission

{{ ms3 }}
✓ Executed · 38 ms ✗ Denied · nothing is executed

The problem

Your agents can already pay. Nothing governs them.

/01

No caps

They spend with the company's card or keys: no limit of their own.

/02

No identity

At payment time, nothing distinguishes a legitimate agent from a compromised one.

/03

No accountability

Which agent, which instruction, which rule? Nothing is recorded. Nobody answers for it.

When an incident occurs, nobody bears the loss today. Praesia is built to hold that role.

How it works

One mandate signed once. Agents that pay on their own.

01

Sign the mandate

Caps, beneficiaries, duration. One strong signature, one time.

02

Badge your agents

Each agent gets its own identity, tied to a human owner.

03

Let them pay

Every payment is checked before execution. Any overrun is refused. One click revokes everything.

Your agents Claude · GPT · your frameworks
PRAESIA Mandates · KYA badge · Checks · Audit
Rails Bank transfer (incl. SEPA) · Cards · Stablecoins

Operational in a day: one transfer funds the wallet, your agents connect. No integration with your banking systems.

The product

Authority delegated, exercised, then cut off.

01

Root mandate

A root mandate is created and signed with SCA. Every mandate is a contract.

02

Delegations

Sub-mandates per team. Rights can only shrink going down.

03

The agent pays

Badged and connected over MCP, the agent settles an invoice. Identity, mandate, intent: checked before execution.

04

Sealed audit

Every decision traced: agent, prompt, rule, mandate version, owner, outcome.

05

Kill switch

One click cuts a branch: instant, cascading revocation. The monitoring engine can also cut on its own.

console.praesia.eu/mandates/new

New mandate

signed · v1
Cap
€150,000 / month
Beneficiaries
IBAN allowlist (12)
Duration
12 months, renewable
Revocation
Immediate, cascading
Sign with SCA C. Moreau (CFO) · Jul 12, 2026, 09:41
console.praesia.eu/mandates

Main mandate

€150,000 / month

active

Marketing

€20,000 / month · card

active

Suppliers

€90,000 / month · transfer · €5,000 max

active

rule: a sub-mandate cannot exceed its parent

console.praesia.eu/payments/pay_8x2k
agent-suppliers-03 verified badge via MCP

€980.00 Supplier A · Invoice #1042

Identityverified agent badge12 ms
Mandatecap, beneficiary, period9 ms
Intentconsistent with the mission17 ms
Executed 14:02:12 · total check 38 ms
console.praesia.eu/audit
Time Agent Decision Owner
14:02:12 suppliers-03 Executed · €980.00 C. Moreau
13:47:05 marketing-01 Executed · €249.00 A. Diallo
13:12:44 suppliers-02 Denied · cap C. Moreau
11:58:03 procurement-04 Suspended · splitting R. Lenoir

page 4,812 sealed · sha256:9f2c…e41a · each page seals the previous one

console.praesia.eu/mandates
Branch revoked in cascade 3 badges invalidated · 240 ms

Main mandate

€150,000 / month

active

Marketing

active

Suppliers

revoked

└ suppliers-01 · -02 · -03 · badges invalidated

the monitoring engine can suspend a branch on its own

Developers

One connection. Checks before every payment.

Your agents connect over MCP, natively from Claude, GPT and agent frameworks, or through the SDK, CLI and API, with no integration with your banking systems. You configure mandates in the console. Praesia checks every payment before execution.

MCP SDK CLI API
{{ codeEl }}

Guarantee

Outside the mandate = reimbursed.

Any payment executed outside the mandate engages our liability: we reimburse it. Inside the mandate, your exposure is capped by construction.

Funds ring-fenced with a licensed partner Designed for PSD2, the AI Act and AML

FAQ

Frequently asked questions.

Why use Praesia?

Praesia lets your AI agents pay autonomously, within a framework you control: a mandate signed once sets caps, beneficiaries and duration. Your maximum loss is known in advance, any overrun is blocked before execution, and any payment outside the mandate is reimbursed. Deployed in a day, without touching your banking systems.

Is Praesia a bank?

No. Praesia is the governance and execution infrastructure for agent payments. Funds are ring-fenced with a licensed partner.

What happens if an agent is hijacked?

Its maximum loss is bounded by its mandate, known in advance. The monitoring engine detects and suspends abnormal behaviour. If an out-of-mandate payment were executed, it would be reimbursed.

Which payment rails?

Bank transfers (incl. SEPA), per-agent cards and stablecoins for machine-to-machine. Praesia plugs into all existing payment rails.

How do my agents integrate?

Over MCP, SDK, CLI or API. The badge signs every request.

How long to get operational?

One day. Praesia does not integrate with your banking systems: you fund your wallet with a simple transfer, and your agents connect over MCP, SDK, CLI or API.

How is this different from spend-management software?

Software that does not hold the funds issues an opinion, which can be bypassed. Praesia attaches the rule to the funds themselves: it applies before every execution, and an identified counterparty answers for it.

Let your agents pay safely

Early access, founder pricing, direct influence on the roadmap.

Request early access
contact@praesia.eu