Govern a Stripe mutation only where the owning application routes it through ORBIT.

A reviewed enforcing integration submits the exact request before calling Stripe. A dashboard, receipt, or ORBIT’s own subscription billing does not intercept a customer application’s Stripe calls.

Scope the integration Return to Action Control

Illustrative scenario · not live Stripe activity

The authority contract is reusable; the enforcement seam belongs in integration code.

Held

Payment integration pattern

payout.create · USD 8,000 · connected account

Why held: The illustrative request exceeds the workspace’s configured approval threshold.
Proof boundary: No Stripe execution is claimed. The application has not received execution permission while the request is held.

Four separate facts

Authorization is not execution, and verification does not bridge the gap.

Request

The integration submits the exact actor, Stripe operation, target, amount, and relevant typed scope.

Authorization

ORBIT returns Allowed, Held, or Blocked under the current policy and proof gates.

Execution report

After Allowed, the owning application calls Stripe and separately reports succeeded, failed, or unknown.

Verification

An .orbitproof check validates its stated artifact boundary; it does not prove that Stripe executed the mutation.

See integration boundaries