REPLAYRecorded planner outputs. Nothing on this page calls a model or PayPal; planning and running live are behind the judge passcode.

Step 2 of 3 · read exactly what it will do

A plan, read before it runs.

The model writes a plan. The schema, the spend caps and the event-target allowlist decide whether it may run. Nothing reaches PayPal until you press Run.

Open Dispute Awaiting Response

Dispute Rehearsal Merchant (US). Sandbox merchant with a pending dispute requiring a response

a dispute on a banked purchase

  1. Dispute openedDispute a banked purchase
Schema
passed
Hosted caps
within USD 0.00 of 400.00 per run; charges, invoices and recorded payments all count. Largest step USD 0.00 of 150.00. 1 of 8 steps, 1 of 1 dispute.
Event target
none declared by this plan; PayPal still delivers this account's events to every webhook registered on it
Purchase bank
needs 1, usable 0 as recorded on 2026-10-24
Details: the exact scenario and its fingerprint

Plan fingerprint, which a run must present unchanged: 36f192216e9dc26d5e12b4b4d5b6521f8c7a120c7bfce014c36799c324dd6cf1

{
  "version": 1,
  "name": "Open Dispute Awaiting Response",
  "profile": {
    "name": "Dispute Rehearsal Merchant",
    "description": "Sandbox merchant with a pending dispute requiring a response",
    "country": "US"
  },
  "currency": "USD",
  "steps": [
    {
      "id": "dispute-1",
      "needs": [],
      "label": "Pre-approved purchase disputed, awaiting merchant response",
      "kind": "open_dispute",
      "reason": "MERCHANDISE_OR_SERVICE_NOT_RECEIVED"
    }
  ]
}
Blocked: needs a banked purchase (run bank:add)Each banked purchase costs a human approval click, so the plan waits rather than guessing.Run this exact plan