Docs · Cross-rail

Cross-rail governance

Axiru is the policy layer that sits in front of every agent-initiated payment, regardless of the rail. One decision endpoint evaluates every transfer before money moves, returns a signed authorization when the policy allows it, and records every outcome in a tamper-evident ledger. This section covers the rail-by-rail integration guides for the active rails.

Integration guides

Start with a rail integration guide.

Each guide walks through prerequisites, connecting the rail, authoring policies, wiring your agent runtime, verifying signed authorizations, and rolling from shadow mode to enforcing.

Stripe DAA

Governing agent payments on Stripe DAA

Wire the pre-authorization hook, author DAA policies from the T-048 templates, verify the signed AuthorizationToken JWS, and roll out from shadow to enforcing.

Read the Stripe DAA guide →
x402

Governing HTTP-native agent payments on x402

Provision the Privy wallet signer, configure the policy hook, verify AuthorizationTokenClaims JWS, understand the fail-closed contract, and roll out to enforcing.

Read the x402 guide →
Active rails

Rails live today.

x402 pre-authorization is live: policy evaluates the payment before it executes and issues a signed allow token, fail closed; the payee verifies the token via the middleware. Stripe DAA runs in shadow mode. The legacy Stripe surface keeps running in enforcing mode on the v1 policy path while the cross-rail engine runs alongside it.

Stripe (legacy)GA (refunds enforcing)

Refund enforcement pre-execution; payouts, transfers, disputes, and application-fee refunds governed from webhooks. The existing Stripe governance surface keeps running on the v1 policy path while the cross-rail engine runs in parallel shadow mode.

Stripe DAALive in shadow mode

Direct-Account-Authorized agent payments. Axiru evaluates every agent_payment, agent_payout, and agent_authorization in shadow mode today: decisions recorded and auditable. Signed enforcement mirrors the live x402 path and flips on per-org.

Integration guide →
x402Live, enforcing

HTTP 402 Payment Required flows for agent-to-agent and human-to-agent commerce. Axiru evaluates every x402 authorization request fail-closed and issues an authorization token signed by the Axiru JWKS. No token, no payment.

Integration guide →
USDC (Solana)Live, enabled per organization

USDC stablecoin transfers on Solana. Pre-execution transfer decisions are live via the public API, enabled per organization; wallet-address counterparty matching supported.

How it works

One decision endpoint for every rail.

The governance contract is the same across all rails. The OVT shape, the decision outcomes, the signed authorization, and the audit ledger are rail-agnostic. Rail-specific bits live only in the adapter.

  1. Agent POSTs to /api/v1/authorizations

    Your agent (or the rail host) sends the proposed OutboundValueTransfer: rail, rail action, amount, currency, initiator kind, agent scopes, counterparty.

  2. Decision Engine evaluates policies

    Policies run in priority order against ten v2 rule kinds: rail, rail_action, amount, initiator_kind, initiator_id, agent_scope, counterparty, rolling_window, time_of_day, custom_expression.

  3. Signed AuthorizationToken or deny/quarantine

    On allow, the route mints a JWS signed by the rotating Axiru JWKS and returns it to the agent. On deny or quarantine, no token is issued: the fail-closed contract from spec §11.4.

  4. Rail verifies and settles

    The rail (Stripe DAA, x402) verifies the JWS against the published JWKS before executing. No valid signature, no settlement. Every outcome lands in the tamper-evident audit ledger.

Next step

Wire one endpoint. Govern every agentic payment.

Start in shadow mode: Axiru records every decision without gating a single rail. Enforcement expands rail by rail as your team is ready.

Start with a free replay. Turn on live enforcement later.

We use cookies for analytics and marketing measurement. You can reject non-essential cookies at any time.

Privacy policy