The Maze: PayPal’s Honey built a checkout business on one valuable decision: which affiliate gets the last click. That decision is moving from browser code into court discovery. A new accounting puts Honey’s merchant roster just above 28,000, down from roughly 35,000 in December 2024, while its coupon database fell from about 90,000 codes to 50,000. The figures are third-party estimates. The harder fact: a federal judge let the creators’ amended case proceed, opening the door to engineering records and attribution logs.
The creators fixed the weakness that killed their first complaint. Affiliate links place an identifier in a cookie or tracking layer; the merchant reads it at checkout and assigns the commission. The first amended complaint had not tied the alleged diversion closely enough to the creators’ lost income. Their 101-page replacement added merchant contracts, test purchases and statistical evidence. On June 22, Judge Beth Labson Freeman denied PayPal’s second dismissal attempt. All seven pleaded claims survived. That does not make Honey liable. It makes the alleged mechanism and injury plausible enough to test with evidence.
The disputed feature is a traffic-allocation rule inside checkout convenience. Honey applies coupons and offers PayPal Rewards. Honey says it earns merchant commissions when members find savings or activate rewards. Creators allege Honey sometimes replaced the affiliate ID already attached to a session, taking last-click credit for demand another publisher originated. The complaint describes selective “stand-down” logic that allegedly checked account age, cashback points, merchant rules and visits to affiliate-network sites. A normal shopper could trigger an overwrite while a likely auditor saw compliant behavior. PayPal says the code predated its acquisition, affected less than 0.1% of traffic and was deactivated.
Network penalties landed, but enforcement stayed negotiable. Rakuten terminated Honey in January 2026, cutting access to roughly 2,000 merchants. Impact.com removed it from its Discovery Marketplace; Awin suspended payments and access to new advertisers. Honey later returned to Rakuten after implementing a stand-down software kit. Networks earn from the publishers they police, so sanctions can become remediation rather than exclusion. The scoreboard still moved: third-party tracking shows losses of more than 7,000 merchant relationships, seven million Chrome users and roughly 40,000 coupon codes. Those estimates still need discovery-quality proof.
Discovery could turn attribution from an argument into a ledger. The investigation says Honey recorded each stand-down decision, its triggering rule and the original affiliate link. If retained, those logs could trace disputed commissions transaction by transaction. Merchants often treat coupon extensions, cashback tools and creators as one performance channel, yet they do different jobs. A creator creates demand. An extension arrives near checkout. Paying the last participant as though it caused the sale can make a program look efficient while paying twice for one journey. Operators need machine-readable stand-down rules, retained logs and an incrementality test.
Why it matters: Honey’s risk comes from the control that made the product valuable: proximity to checkout. Last-click systems are simple to settle and easy to game because the final identifier can outrank the party that created demand. The U.S. case has not established misconduct, damages or a class. It has established that the allegations deserve evidence. Attribution is not neutral plumbing. It is a payment rule. If nobody can explain why a publisher received credit, discovery may explain it for them.
Sources: PPC Land | Federal court order | Second amended complaint | Honey Help Center
