NewCatches refunds that fail after they succeed

Your agent said it worked. Prove it.

AI 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.

  • Free plan, no card
  • Your keys stay in your network
  • Read-only checks
How Conseqa works: one refund, replayed
1 · acts
Your AI agent
Refunds $24.99 for ticket 4821Heard: succeeded
2 · replies
Stripe
The payment providerrefund: succeededrefund: failed
3 · checks
Conseqa
Reads Stripe itself, from your networkstill watching
4 · you seeChecking…A reply alone proves nothingVerifiedPaid, right amountFailedStripe undid it 3 min later Alert sent

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.

Checks outcomes in
  • Stripe
  • Razorpay
  • Shopify
  • Cashfree
  • RazorpayX
  • PostgreSQL
  • Any HTTP API
  • OpenTelemetry

The gap in every agent trace

The API says yes. The money doesn't always move.

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 heardWhat really happenedWhat Conseqa says
succeededStripe failed the refund three minutes laterFailedUndone after it was verified
connection resetThe refund had already gone throughVerifiedFound by its key. Nothing sent twice.
200 OKPaid, for the right amountVerified
timeoutThe provider can't be read yetUnknownRead again. Never guessed.

The dashboard

Every action, its verdict, and the evidence behind it.

conseqa.dev/appExample data
FailedUndone after verification

Refund for ticket 4821

Stripe · $24.99 · re_3UZF…8BoA

Stripe said this refund succeeded, and Conseqa verified it. Three minutes later Stripe marked it failed. The customer has not been refunded.

  1. Refund asked for $24.99 to the original card
  2. Stripe replied succeeded
  3. Verified 4 of 4 checks passed
  4. Read again still succeeded
  5. Failed Stripe now says failed. Issue opened, alert sent.

Evidence from Stripe

Statussucceeded → failed
Amount$24.99
Paymentpi_3Pja…
Keycq_8f21…
StatusActionWhat happenedAmountWhen
FailedRefund · ticket 4821Verified, then Stripe failed it$24.993 min ago
VerifiedRefund · ticket 4817Paid, right amount$12.006 min ago
VerifiedRefund · ticket 4812Reply lost; found by its key, sent once$89.0011 min ago
FailedRefund · ticket 4809Accepted, then the bank rejected it$45.5018 min ago
UnknownRefund · ticket 4801Stripe could not be read; checking again$9.9924 min ago
VerifiedRefund · ticket 4796Paid, right amount$30.0031 min ago
CriticalA refund was verified, then Stripe undid itRefund · ticket 4821 · 1 action · 3 min agoAlert sent to #payments
HighRefunds accepted, then rejected by the bank2 actions this week · last 18 min agoAlert sent by email

How it works

Wrap the call you already make.

  1. 1Say what should changeBefore the call, the SDK records the refund you expect and gives it a key Stripe will carry.
  2. 2Let the agent actYour code calls Stripe, your CRM or your database exactly as it does today. Nothing sits in between.
  3. 3Read what really happenedA runner in your network reads the record, read-only, and gives a verdict with the evidence.
refund.ts
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 keys never leave your network.

Your network

Your agent and the SDKRecords each expected change before the call, with a key the provider carries back.
The runnerHolds the provider keys. Reads, never writes. Keeps working if Conseqa is down.
Conseqa dashboardGets redacted events and only the evidence you allow. Issues, alerts, history.

Try it in a minute.

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 demo

On your machine

Or 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 start

Every plan has every feature.

Limits only inform. Nothing is ever blocked.

Free

$0 a month

1,000 protected actions a month

100,000 trace spans · For trying Conseqa on one workflow.

Growth

$199 a month

100,000 protected actions a month

10,000,000 trace spans · For several agents, or one at volume.

Questions

What people ask first.

Anything else: jhaladevrajsinh11@gmail.com.

Does Conseqa retry or fix failed actions?

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.

How can an API say yes and the refund still fail?

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.

Isn't an idempotency key enough?

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.

Can't my agent framework check its own actions?

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.

Is it only for refunds?

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.

Can it compare models or agents?

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.

Where do my provider credentials live?

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.

Which systems can it verify?

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.

How is this different from tracing?

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.

Know what your agent really did.