OpenChainGraph Suite · ART-776

PayPal Dispute Deadline & Evidence

Seller-response deadlines for a PayPal dispute (the default psp), computed from PayPal's own stated rules or a seller_response_due_date passthrough, with days remaining against a time you supply; the evidence the reason requires, what is missing, and the bundle to submit, CE3.0-shaped only when a card network is actually in the loop. A psp input also selects the Stripe, Adyen and Square deadline tables, each quoting its own snapshot.

Payments DisputesPayPal Disputes API v1.12Stripe · Adyen · Square tablesCE3.0 ProducerZero PIIClient-side only
🔒 All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.
Scope & reliance
Deadline rules are exactly what PayPal states, quoted from the dated clause snapshot research/clause-snapshots/paypal-disputes-2026-10/SNAPSHOT.md (fetch 2026-10-25T03Z): at the inquiry stage, respond within the first 10 days following dispute creation (S8) and the inquiry stage lasts up to 20 days unless escalated to a claim (S1); disputes are closed automatically after 20 days unless escalated (S8); a supplied seller_response_due_date is the date and time by when the merchant must respond (S5). The chargeback-stage response window and the appeal period length are NOT STATED by PayPal (S9 names issuer-based strict deadlines without a number; S2 names the appeal period without a number): both come back as null with a reason, and you can pass PayPal's own timestamp through instead. Stage scoping: most PayPal disputes run through PayPal's own buyer-protection process (inquiry, then claim), outside the card-network rails; only a chargeback on a card-funded transaction is a network dispute, and the CE3.0-shaped bundle (field names kept verbatim for art-297, the terminal Visa CE3.0 linter) is emitted for that case alone, with null where PayPal has a counterpart missing. Per-PSP deadline tables: a psp input (default paypal) also selects the Stripe, Adyen or Square table (snapshots stripe-disputes-2026-10, adyen-disputes-2026-10, square-disputes-2026-10, each fetch 2026-10-26T12Z), each with its own stage vocabulary and stated numbers, every rule citing its own snapshot's clause; those paths take no funding_source (a PayPal-path input, refused there) and return required_evidence null with a reason, because their snapshots publish no re-typed per-reason evidence table. This node is deadline arithmetic and evidence assembly only, standing apart from any dispute-outcome prediction or claim of Visa or PayPal acceptance. Reason and evidence vocabulary is reused verbatim from the estate's PayPal dispute-evidence map (four reasons). This node ships compute_proof_ready: deferred.
Dispute
Evidence on hand
Synthetic values only. Blank fields count as missing evidence.
Result
Bundle decision
Cited clauses (SNAPSHOT.md)
Execution Hash & §4 Artifact
SHA-256 execution hash (JCS canonical, RFC 8785):