Automate
Operations that run themselves, and explain themselves. Early access.
A copilot that answers from your own ledger and cites the rows. Playbooks that act on alerts and ask first. A sentinel tuned for twenty payments a day. Nothing moves money on its own.
Grounded in your data, scoped to your merchant
Payments, attempts, traces, disputes, payouts and settings. The tenant scope the API enforces is the scope the Copilot sees. Card data is structurally absent.
Proposes, never executes
Actions are buttons with their consequences stated. Set policy to prefer, expected effect plus 36 points on SCA-zone buyers under 50 euro. Your click is the audit row.
Playbooks ask first
Every playbook starts in ask-me mode. After a clean month you can graduate it to auto, per playbook. Nothing fails over silently.
A sentinel for small volumes
Slow bleed, sibling gap, concentration, refusal share and settings changes, compared against trends and siblings so it fires on twenty payments a day without crying wolf.
Copilot
Why did approvals drop on Tuesday is a question an analyst answers in an afternoon with SQL. The Copilot answers it in seconds, from the same tables, and shows the rows it used.
Cites rows
Every answer links the payments, attempts and settings it read.
Explain this payment
Which terminals were eligible, the scores, the policy, the hops, what the rail said, and what to do about it.
Bounded actions
Shift a share, pause a terminal, set a policy, refund an early alert, draft a pack, notify a channel. Never a payout.
Runs as audit rows
What fired, what it saw, what it did or proposed, and who confirmed.
Our take on a
dashboard
or
For the two-person team
The sentinel watches, the Copilot explains, the playbook drafts. You click. That is the whole operating model.
For the ten-person team
Graduate the boring playbooks to auto, keep the interesting ones on ask, and read the runs like a log.
Got questions?
We’ve got answers.
Straight ones,
in writing
Can an automation move my money?
No. The Copilot proposes; a person confirms. Playbooks are bounded to traffic shares, pauses, policies, refunds of early alerts, drafts and notifications. No automation can create a payout or change a destination.
What does "early access" mean on this site?
It means a feature exists and runs for design partners but is not yet available to every account, usually because a partner contract is still landing. We never write "coming soon". The honest scope page lists what is live, planned and never.
What does the routing trace contain?
Which terminals were eligible, the scores it used, the policy, whether the payment explored, every hop with its outcome and latency, and a link to the Explain panel. It is on every payment, in the API and in the dashboard.
Nine rails, one contract
Ready to
hand it off?
Join early access. Ask-first from day one, auto when it has earned it.