Stripe integration

How Axiru works with Stripe

Axiru is a third-party app published on the Stripe App Marketplace. We install onto your existing Stripe account via Stripe Apps OAuth and consume Stripe webhooks. This page exists so you know exactly what we touch, when, and why.

What Axiru does

Axiru is a pre-execution governance layer for refunds, disputes, payouts, and transfers. When your agents or staff want to move money, Axiru evaluates the request against your policies and either allows, requires approval, or blocks — before the money moves.

By default Axiru runs in shadow mode. It observes Stripe events and simulates decisions without ever interfering with live payments. You explicitly toggle enforcement on, plan by plan, when ready.

Test mode vs live mode

Axiru supports both. During onboarding you'll choose which account mode to connect. Decisions in test mode never affect real Stripe traffic; decisions in live mode follow the policy mode you set (shadow or enforce). Both modes generate identical audit entries.

You can connect both — Axiru keeps test and live accounts segregated and labels every decision with its mode.

How we connect

  1. You start at /stripe/install and click "Connect with Stripe." We send you to the Stripe Apps OAuth consent screen.
  2. You review the exact OAuth scopes Axiru is requesting — listed on /permissions — and approve them in Stripe.
  3. Stripe redirects you back to Axiru and we exchange the authorization code for a connected-account access token. Token is encrypted at rest and only used server-side.
  4. We register webhooks for refund, dispute, payout, and transfer events on your account. These webhooks are how shadow-mode observation works.
  5. You can revoke access at any time from your Stripe dashboard. Revocation invalidates the access token and stops all ingest.

Data we read

  • Refund, dispute, payout, and transfer events
  • Charge, customer, and balance-transaction metadata referenced by those events
  • Account profile (display name, country, default currency) for identification

Data we do NOT read

  • Raw card numbers, CVCs, or any PCI cardholder data
  • Bank account numbers or payout destination details
  • Personal identity verification documents
  • Payment links or product catalog data

Actions Axiru takes

In shadow mode Axiru takes no action on your Stripe account — it only records what it would have done.

In enforce mode Axiru may, depending on your policies and only when an authenticated decision requires it:

  • Cancel or refuse a refund/dispute/payout in flight (via Stripe API)
  • Hold a request for human approval (no Stripe call until approved)
  • Mark a connected account for review (no balance impact)

Every action writes to an immutable audit ledger you can export at any time.

We use cookies for product analytics and marketing measurement. Nothing non-essential runs until you choose.

Privacy policy