Automation
Set rules once — routine transfers approve themselves, unusual ones wait for your team.
Automation in Transvia is a set of rules you control. Money moves by the rules, 24/7 — and every decision is logged and reviewable.
The rules you can set
| Rule | Default | What it does |
|---|---|---|
| Auto-approve transfers below | $500 | Routine payments execute without a human |
| Only allow approved recipients | On | New recipients always get extra scrutiny |
| Require approval above | $5,000 | Large transfers wait for a team decision |
| Allowed routes | EUR, GBP, MXN | Restrict which corridors automation may use |
Change a rule and it takes effect on the next decision — rules are evaluated per transfer, not batched.
How team approvals work
When a transfer does not pass the rules, it lands in the approval queue as a request with the engine's own reasons attached:
- Raise — the request records the corridor, amount, recipient, FX drift, and liquidity, plus why it needs review ("Amount exceeds $5,000 autonomous limit", "Recipient not on approved list").
- Vote — three reviewer roles: Finance, Operations,
Compliance. Each role votes once,
approveorreject. - Resolve — a single reject ends it immediately; approvals resolve at the stored quorum — 2 of 3.
The reasons are recomputed server-side by the policy engine on every request — client-supplied reasons are never trusted, so every surface shows the same decision.
Programmatically, the queue is GET /api/approvals (newest first) and
votes are POST /api/approvals/{id} with a role and decision. Resolved
requests are closed to further votes. Request and response shapes are in
API.
What automation is not
It is not an AI improvising. The decision engine is a pure function over
four signals — amount, recipient trust, FX drift, liquidity — with
verdicts AUTO_EXECUTE or REQUIRES_REVIEW (hard blocks live onchain).
The same engine powers the agent sweeps, the simulator, and this approval
queue, so decisions can never disagree between surfaces. See
Policies for the vocabulary and
Automation Agents for the loop that enforces it.
Watch it work
Open transvia.xyz/automation to see the rules, the approval queue, and the agent decision log side by side. Every entry links back to the transfer and its onchain trail on transvia.xyz/transfers.