Skip to content
DeAlgoOpen workspace
Stripe test-mode pilot

Give agents a refund tool you can control.

Your agent requests an exact refund. An administrator approves it. DeAlgo submits it through the governed execution path and records the outcome.

JavaScript · HTTP · MCP. For payments already recorded in DeAlgo.

Try the approval flow

Simulated
Customer refund · example payment
$25.00 USD
Waiting for approval

An agent wants to refund $25.00.

Illustration only. No API call, Stripe action, or real evidence is produced here.

01 / Request

One stable request

Repeated submissions with the same key resolve to the same request. Changed parameters are refused.

02 / Approve

A human holds approval

Agent credentials can propose and read. An authenticated administrator reviews the exact amount.

03 / Observe

Keep uncertainty visible

A pending provider response stays pending. An unknown outcome does not authorize another refund.

Start small

One connection. Three tools.

The MCP adapter lists recorded payments, requests a refund, and reads its status. It has no approval tool and holds no Stripe key.

  1. Use your pilot Portal URL and a workspace API key.
  2. Install the pilot package, then run the read-only connection check.
  3. Connect MCP or request a refund from your application. Open the returned approval URL.

JavaScript · request, then review

import { DeAlgo } from "@dealgo/middleware";

const dealgo = new DeAlgo({
  url: process.env.DEALGO_URL,
  apiKey: process.env.DEALGO_API_KEY,
});

const request = await dealgo.requestRefund({
  decisionId: recordedPayment.decisionId,
  amountMinor: 2500,
  requestKey: "support-case-1042-refund",
});

// Open as a signed-in administrator.
console.log(request.approvalUrl);

// Later: read evidence without resubmitting.
await dealgo.getRefund(request.id);

Pilot scope, clearly stated

This release connects to a configured DeAlgo test environment and payments already recorded there. It does not import an entire Stripe account, enable live-money refunds, or replace your existing payment system. Provider-response exports are unsigned. The signed-receipt prototype is separate. Start with one workflow and measure whether it reduces your integration and investigation work.