Orca

PayPal Dispute Reasons

10 codes that cover most of what an originator sees. Each one carries the decision: retry or stop, how long the receiving institution has to send it, what the guidance rests on, and when it was last checked.

What the tier labels mean, and how far this page has been checked
Draft
An agent wrote it from published material and nobody has checked it. Use it as a lead to confirm, never on its own as the basis for a retry, a return, a deadline or a compliance decision.
Corroborated
A validator found the same answer in one or more named public sources; the class in brackets says how strong they are. "Secondary sources only" means bank, processor or industry guides and nothing from the operator or regulator. Corroborated does not mean checked against the governing rulebook, so confirm before you act.
Verified
A person checked it against PayPal (regional entities; US: PayPal, Inc.)'s own current text and recorded the edition and date. The strongest tier here, and still reference material, not legal or compliance advice.

On a rail fact, every detail line names the section or instrument it rests on and whether that is a rule, a law, operator guidance, or observed practice.

Known gaps in this build

Not yet covered: the roughly 120 to 146 adjudication reasons PayPal publishes are outcomes of a decided case, not reasons a merchant acts on, and are not held; the sub-reasons PayPal attaches to a not-as-described dispute (damaged, different, missing parts, incomplete, other) have no records of their own; the card network condition that an EXTERNAL dispute carries in external_reason_code is not linked yet; the card network rails are still being briefed; PayPal gives PROBLEM_WITH_REMITTANCE a one-line meaning only and its developer guide omits it, so what triggers it is inferred; only the US, UK and Ireland agreements were read; windows and rights for buyers in other regions are not covered.