Integrations · where the money sits, and how a determination moves it
Integrations
Judgment is rail-agnostic. The bundle names where the disputed funds are held; the ruling comes back with a ready-to-execute instruction for that rail, signed by the venue. Recourse never holds funds, keys or balances anywhere — it decides, and the holder executes. Pick where your money lives.
Platforms · fiat
Stripe Connect sandbox-proven
Marketplaces, delivery and gig platforms holding funds on Stripe. Rulings become transfer / refund / transfer_reversal calls the platform runs with its own key — held funds, transfers already made, and destination charges all covered.
rail stripe_connect · guide →
Agents · smart accounts
Safe (and other ERC-7579 accounts) live on Tempo testnet
A Safe puts its agent under the Recourse Protocol: install our ERC-7579 module and cap the agent, or scope a Zodiac Roles policy to our escrow contract. Funds the agent commits go into a Recourse transaction against hashed terms.
rail recourse_escrow · guide → · live demo
Agents · HTTP payments
x402 case fees live
Agents pay case fees with the request over x402 (USDC on Base) and sign in with their wallet — no account. Disputes over an x402 payment authorization held by a facilitator settle as splits on the same rail.
rail x402 · guide → · live demo
Stripe's payments L1
Tempo live on Moderato
Stablecoin settlement on Tempo (chain 4217; testnet 42431): transfer intents for custodial holders, or the Recourse Protocol contracts deployed on Tempo for non-custodial escrow with fees paid in USD stablecoins.
rail tempo · recourse_escrow · guide → · live demo
Fiat escrow
Escrow.com executor ready · partner approval pending
Escrow.com has no dispute API, but an approved partner may act As-Customer. A determination is executed as the parties' own accept / return actions; milestone transactions approximate a split.
rail escrowcom · guide →
On-chain escrow · retained
Kleros escrow supported
For funds already in Kleros's EscrowUniversal: name RecourseArbitrator as the ERC-792 arbitrator and the venue's signed ruling pays out. Rulings are binary there; new integrations should use the Recourse Protocol.
rail kleros_escrow · guide →
Trustap / Tazapay / Shieldpay class
Fiat escrow partners (webhook) spec + reference receiver
Any escrow provider holding fiat: a signed webhook carries the money instruction; the partner executes the split from held funds. Reference receiver and spec in the repo.
rail escrow_webhook · guide →
Underneath the on-chain ones: the Recourse Protocol
Safe, Tempo and x402 are ways into our own contracts, not separate escrows. The Recourse Protocol is Recourse's escrow and enforcement layer — the transaction contract that holds the funds and executes the venue-signed ruling, plus an optional ERC-7579 module for smart accounts. Read about the protocol →
Common to every integration
- One request.
POST /disputeswith the record and asettlementspec naming the rail. Platforms use an API key; agents sign in with a wallet and pay the case fee with the request (x402). - One instruction. The ruling's
money_instruction(claimant / respondent split in minor units) is translated into the rail's own operations and returned on the record asrail_instruction— and, for platforms, delivered to the enforcement webhook set on the dashboard, HMAC-signed. - Escalation holds. An instruction marked
escalated: trueis never executed; the bench's final ruling supersedes it. On-chain rails carry no venue signature until the determination is final. - Appeals supersede. Set
appeal_window_hoursand enforcement waits; an appeal ruling replaces the first. On the Recourse Protocol the window is enforced by the contract itself.
Wire format: settlement rails in the API docs · spec: integrations/escrow/WEBHOOK-SPEC.md in the repo. Business-side partner listing: Partners.
Logos and names identify integration targets and formats and belong to their owners; listing here does not imply endorsement by, or a commercial relationship with, the named organisations.