In your browser
The browser demo writes a synthetic store credit to PostgreSQL, drops the reply, and recovers the row without retrying the write. No money moves.
Run the live demoAI agents issue refunds, payouts and orders, then trust the API's reply. Conseqa checks the payment provider or database itself, and tells you what really happened.
Your AI agent asks Stripe for a refund, and Stripe replies that it succeeded. Conseqa reads the refund from Stripe itself and reports it Verified, then keeps watching. Three minutes later Stripe fails the refund; Conseqa reports it Failed and sends an alert.
The gap in every agent trace
Refunds, payouts and orders settle after the API answers. Banks reject them, payouts bounce days later, and replies get lost on the way back. Your agent only ever sees the reply.
| What the agent heard | What really happened | What Conseqa says |
|---|---|---|
succeeded | Stripe failed the refund three minutes later | FailedUndone after it was verified |
connection reset | The refund had already gone through | VerifiedFound by its key. Nothing sent twice. |
200 OK | Paid, for the right amount | Verified |
timeout | The provider can't be read yet | UnknownRead again. Never guessed. |
The dashboard
Stripe said this refund succeeded, and Conseqa verified it. Three minutes later Stripe marked it failed. The customer has not been refunded.
Evidence from Stripe
succeeded → failed$24.99pi_3Pja…cq_8f21…| Status | Action | What happened | Amount | When |
|---|---|---|---|---|
| Failed | Refund · ticket 4821 | Verified, then Stripe failed it | $24.99 | 3 min ago |
| Verified | Refund · ticket 4817 | Paid, right amount | $12.00 | 6 min ago |
| Verified | Refund · ticket 4812 | Reply lost; found by its key, sent once | $89.00 | 11 min ago |
| Failed | Refund · ticket 4809 | Accepted, then the bank rejected it | $45.50 | 18 min ago |
| Unknown | Refund · ticket 4801 | Stripe could not be read; checking again | $9.99 | 24 min ago |
| Verified | Refund · ticket 4796 | Paid, right amount | $30.00 | 31 min ago |
How it works
import { decorateStripeRefundRequest, stripeRefundSucceeded } from "@conseqa/connector-stripe";
const refund = await conseqa.protect(stripeRefundSucceeded, {
actionKey: `ticket_${ticketId}_refund`,
protectionMode: "required",
intent: { paymentIntentId, amountMinor, currency: "USD" }, execute: ({ providerCorrelationKey }) => {
const { body, headers } = decorateStripeRefundRequest(
{ paymentIntentId, amountMinor },
providerCorrelationKey,
);
return stripe.refunds.create(body, { idempotencyKey: headers["Idempotency-Key"] });
},
});// The runner now reads the refund from Stripe, and keeps reading it
// for 72 hours, because a Stripe refund can still fail after it succeeds. Security
Your network
The browser demo writes a synthetic store credit to PostgreSQL, drops the reply, and recovers the row without retrying the write. No money moves.
Run the live demoOr run three simulated refund examples on your own machine, with Node.js and nothing else. One is verified, one is recovered after its reply is lost, and one is caught failing.
npx --yes @conseqa/cli@0.1.12 quickstart
cd conseqa-quickstart
npm install
npm startThe quickstart guide The database demo, against your own PostgreSQL
Limits only inform. Nothing is ever blocked.
$0 a month
1,000 protected actions a month
100,000 trace spans · For trying Conseqa on one workflow.
$49 a month
10,000 protected actions a month
1,000,000 trace spans · For one agent in production.
$199 a month
100,000 protected actions a month
10,000,000 trace spans · For several agents, or one at volume.
No. It is read-only: it checks the system of record and reports a verdict with its evidence. Your agent, or a person, decides what to do. Conseqa never issues a refund and never retries an action.
A refund is not one transaction. The provider records it and answers at once, then sends it through the card network and the customer's bank, which can reject it minutes or days later. The 200 meant the request was accepted, not that the money arrived.
It solves a different problem. The key stops a retry from refunding twice; it does not tell you whether the first refund worked. Retrying with it returns the first reply again, which may be pending, or a success that fails later, and providers forget keys after a while (Stripe after 24 hours). Conseqa uses the same kind of key to find the action after a lost reply, then reads what actually happened.
It can check, but inside the run: with the agent's own assumptions, and only while the run lasts. A refund that fails tomorrow arrives after the run has ended, and a loop that retries money movements by itself is the risky part. Conseqa's runner checks independently, on its own schedule, with read-only credentials, and keeps the evidence.
No. It fits any action that changes another system you can read back: payouts, orders, bookings, CRM records, tickets, emails with a delivery status, database rows. The guide has recipes for a CRM update and for an email that must be delivered, not just accepted.
Yes. Compare groups the same verdicts by model, by agent or by action, so you can see which one actually gets the work done. Your own router can read those numbers with an environment key; Conseqa still stays out of the request path.
In the runner, inside your own network. The dashboard receives redacted lifecycle events and only the evidence fields you allow. Capture of prompts, responses and tool arguments is off by default.
Refunds on Stripe, Razorpay, Shopify and Cashfree, RazorpayX payouts, PostgreSQL, and any HTTP API with a way to read the result. Contracts are code, so your own systems work too.
A trace records what your process saw: the call and its reply. Conseqa checks what changed in the external system afterwards, and links that verdict back to the trace.