Partners hold · desks display · rails execute · we decide
Partners & integrations
Recourse is deliberately small at the waist: one judgment engine, many surfaces. Everything on this page follows the same three rules — the venue never holds funds, never takes a share of the disputed value, and never puts a partner it judges on its cap table. Status labels are literal.
Payments & settlement
The Stripe stack
Recourse is built rails-first for the Stripe ecosystem: judgment stays rail-agnostic, instructions execute wherever the funds already sit, and the venue never takes custody — so adjudication drops into a payments stack with near-zero integration surface.
Stripe Connect reference integration
Rulings execute as verbatim transfer + refund steps against delayed transfers on the platform's own Stripe account
Stripe Checkout & Billing live
How platforms pay Recourse: metered rulings, monthly invoices, card checkout
Tempo spec-stable
Stablecoin settlement on Stripe's payments L1 — transfer intents with the dispute id in the memo
Bridge planned
Stablecoin invoice payment (USDC) for annual-commitment accounts
Escrow & funds-holding
Escrow partners
Partners hold, we decide. Any funds-holder completes its product with the enforcement webhook: signed, idempotent, replay-protected instructions their rails execute.
Trustap in conversation
C2C transaction-hold escrow — default-resolver integration target
Tazapay in conversation
Cross-border B2B escrow — the corridor thesis
Shieldpay in conversation
Larger-deal escrow
Mangopay planned
Marketplace wallet infrastructure — rulings against held wallet balances
Open escrow templates spec-stable
Smart-contract escrow naming Recourse as resolver, published free for the agent era
Where the queue lives
Support desks & marketplace infrastructure
Draft verdicts inside the tools dispute-ops teams already use — the shadow-pilot on-ramp.
Zendesk app built
Ticket-sidebar app returning draft verdicts from the ticket thread
Intercom planned
Inbox app for conversation-native disputes
Mirakl in conversation
Enterprise marketplace platform — one integration, hundreds of operator platforms
The agent economy
Agent rails & protocols
Agent-to-agent commerce settles on rails that are final by design — their own docs tell developers to build a dispute layer. Recourse is the endpoint that sentence points to.
x402 spec-stable
HTTP 402 agent payments — facilitator settlement of rulings against held authorizations
Model Context Protocol in development
The venue as an agent tool: submit_dispute / get_ruling from any MCP-speaking agent
AP2 / agent payment protocols watching
Dispute clauses in machine-readable mandates naming the venue
AWS AgentCore watching
Venue integration for enterprise agent deployments
Standards & doctrine
Legal infrastructure
The venue adopts open standards for how terms attach to transactions, rather than inventing its own.
Legal Context Protocol (LCP) adopted
Terms-attachment standard — LCP-wrapped terms submit natively in the dispute bundle
DSA Article 21 (EU) certification in preparation
Out-of-court dispute settlement certification — the statutory channel
Hold funds, run a queue, or build a rail?
Escrow providers whose volume names Recourse as default resolver, desks that surface draft verdicts, and rails that point their dispute clause at the venue all grow the same corpus. The integration kit — webhook spec, reference receiver, rule-pack schema — ships on request.
Talk to us about partneringCompany and protocol names identify integration targets and formats; listing here does not imply endorsement by, or a commercial relationship with, the named organisations except where a status says so.