Financial Decision Control Layer for Stripe · pre-execution governance

Decisions before money moves.

Axiru is the policy, approval, and audit layer for Stripe refunds. Define your policy once. Enforce it on every refund — from a support rep, an AI chatbot, or an automated workflow — before the Stripe API call goes out.

Pre-execution control, not after-the-fact reconciliation — see your last 90 days.

Non-custodialShadow mode firstPolicy enforcementApproval queueImmutable audit
curl -X POST https://www.axiru.com/api/decision \
  -H "content-type: application/json" \
  -d '{
    "org_api_key": "sk_live_…",
    "source": "support_tool",
    "action": "refund",
    "stripe_charge_id": "ch_3PLs9k…",
    "amount_cents": 22000,
    "customer_tenure_days": 9,
    "reason": "duplicate_charge"
  }'
# → {
#     "decision": {
#       "outcome": "pending_approval",
#       "reason": "Refunds over $150 require approval",
#       "policy_version": "v3",
#       "matched_rule": "high_value_refund_review",
#       "approver_role": "finance_manager"
#     },
#     "intent_id": "5f3c…",
#     "received_at": "2026-04-28T14:32:11.061Z"
#   }

Live endpoint. Wire the same call against your tenant via /docs.

Sealed when the refund is decided

Every approval, override, and block is sealed at decision time with policy version, approver identity, and timestamp. The audit record is immutable — you can replay why a refund moved, but you can't rewrite it after the fact.

See every refund. Approve the leakage. Lock it down.

Axiru turns scattered refund events into one operational control plane that finance, support, and risk teams use together — before the money moves and after, when it's time to explain why.

See every refund

Every refund request — from a support tool, AI chatbot, automation, or direct Stripe API call — is observed in one place. Live ledger, not a downstream reconciliation report.

Approve the leakage

Edge cases above your threshold route to the right approver with the policy reason and full context attached. Routine cases auto-allow and stay fast.

Lock it down

Hold a single refund. Freeze a merchant. Or hit the kill switch on the entire refund bot. Authority is always revocable, scoped, and logged.

Four numbers your CFO will start asking about.

Last 30 days from a connected Stripe account in shadow mode. Replace the numbers with yours — Axiru replays your real history during onboarding.

Open the dashboard preview →
Protected revenue
$186,240
+12.4% vs prior 30d
Refunds reviewed
2,431
312 routed to approval
Pending approvals
312
4.7% require human judgment
Leakage caught
$18,420
22.4% from one pricing-exception pattern

Hold a refund. Freeze a merchant. Hit the kill switch.

Three control surfaces, one click each. None of them require a code deploy or a Stripe dashboard hunt — and every action is logged with actor, scope, and reason.

Hold a refund

Pause an in-flight request before Stripe executes. The original decision and reason stay intact in the ledger; the refund stays on the queue.

Freeze a merchant

Stop refunds from a single sub-account or merchant connected via Stripe Connect while you investigate. Everything else keeps moving.

Kill the refund bot

Org-wide kill switch — every source-of-refund stops at intake until a human flips it back. Use it like a circuit breaker, not a button you avoid.

Route → Policy → Approvals → Audit

One enforcement path for every refund, regardless of where it originates. The same four steps run in shadow mode and in live enforcement.

1

Route

Every refund attempt — support tool, AI agent, automation, direct API — passes through Axiru before it reaches Stripe.

2

Policy

Plain-language rules compile to deterministic enforcement. Same input, same outcome, every time. Versioned, no LLM in the decision path.

3

Approvals

Anything above threshold routes to a human — in-app, Slack, or signed webhook — with the full diff of what would have executed.

4

Audit

Every decision is sealed and hash-chained at execution time. Replayable, exportable, regulator-ready.

Shadow mode

Not just onboarding. A permanent second opinion.

Most teams flip shadow on to de-risk the first rollout. The strongest ones keep it on — running every proposed policy change against real refund traffic before it goes live. Live and shadow can run side by side, forever.

  • Observe. Shadow policies log decisions without changing the Stripe outcome.
  • Diff. Every refund shows the live decision next to the shadow decision.
  • Tune. Adjust thresholds in the policy editor; every diff stays in the ledger.
  • Promote. When the numbers hold, flip shadow: false.
Last 7 days · refunds-over-150
Shadow
Approvals queued
82
Blocked refunds
17
Allowed refunds
312
Next step: flip shadow: false — 82 would-be approvals will start going to the approvals queue.

An audit log a regulator already trusts.

Every decision is hash-chained at seal time and signed against the policy version that ran. Exports are SIEM-ready (Splunk, Datadog, S3) with one line of config — no separate compliance pipeline.

Audit & exports →
14:32:08.214Zrefund.allowed · charge ch_3PLs9k · $42.00 · policy v3 · rep: ali@acme.iosha256:9f2e…1c4a
14:32:11.061Zrefund.pending_approval · charge ch_3PLs9z · $220.00 · reason: over_150 · approver_role: finance_managersha256:71b3…ef02
14:32:11.412Zrefund.blocked · charge ch_3PLs9d · $1,200.00 · reason: velocity_window · actor: ai_chatbotsha256:c4d5…aa10
14:32:14.782Zpolicy.promoted · v3 → v4 · approver: cfo@acme.io · diff: 3 thresholds, 1 new rulesha256:3a91…77d2
New · Free 90-day replay

Upload your Stripe refund history. See what we'd have caught.

Connect Stripe in read-only mode, or drop a CSV of the last 90 days. Axiru replays every refund through a curated policy pack and shows exactly which ones would have been blocked, paused for approval, or flagged as policy drift. No enforcement. Auto-deletes in 30 days.

How replay works
Sample replay
2,119
Allowed
312
Approval
17
Blocked
$18,420 leakage flagged · top driver: pricing-exception overrides at 22.4%

Simple pricing. Start in shadow mode.

Free shadow mode covers the audit. Upgrade when you flip enforcement on.

Full pricing →

Free shadow

$0
For your first 90-day replay
  • Connect Stripe in read-only mode
  • Replay last 90 days against policy
  • Decision ledger + dashboards
  • Single workspace

Enterprise

Custom
For regulated finance teams
  • SOC 2 / ISO artifacts
  • Custom policy packs
  • Dedicated review channel
  • Quarterly policy reviews
  • VPC + on-prem gateway option

A category of one for refunds.

Manual overrides scale with headcount. Stripe Radar fires after the charge. LLM observability watches but doesn't enforce. Axiru is the control plane — and it runs before the refund executes.

CapabilityAxiruRefund decision control layerManual support overridesReps + ticket queueStripe Radar / vendor-nativePer-charge rulesLLM observability / logsTraces & logs
Deterministic policy enforcement before refund executes
Amount, tenure, and pattern rules evaluated at intake — not after Stripe has moved funds.
××
Human approval on exceptions
Edge cases route to the right approver with the policy reason and full diff attached.
××
Cross-team view (finance + support + risk)
One surface for ticket exceptions, CFO reviews, and risk audits.
×
Instant kill switch for the entire refund flow
×××
Shadow mode before enforcement
Replay the last 90 days against a candidate policy before flipping it on.
××
Immutable + exportable audit log
Hash-chained decision records, SIEM-ready exports.
×
Non-custodial — no Stripe key custody
Runs in under an hour

Partial means it is possible but not turnkey. Our take, based on what teams tell us during onboarding.

Ship a refund flow you can actually govern.

Connect Stripe in read-only mode, replay your last 90 days, and watch the decision ledger fill in. Free shadow mode covers everything below the enforcement line.

No card. No commit. Non-custodial by default — Axiru never holds your Stripe keys.