IMO, no, those endpoints don't qualify. That's just RPC over HTTP. Nothing wrong with it, but not REST (REpresentational State Transfer), since it's not transferring representations of state.

Search is probably not worth shoehorning into a REST paradigm (don't be a purist!). The others are easy enough though, something like

  PATCH /v1/payouts/:id
  {state: canceled}

  PATCH /v1/disputes/:id
  {state: closed}

Or an equivalent PUT with the whole object.

Or if you want to be json-patch standards-compliant:

  PATCH /v1/payouts/:id
  {op: "replace", path: "/state", value: "closed"}

FWIW this is why I think it's not really productive to be persnickety about a "REST API" being 100% always REST. A CRUD app is still a CRUD app if you do some occasional other operations, and a REST API can still be a REST API with some endpoints that are not REST.