Set this affiliate's commission rate, in whole percent (spec 3.7).

The per-affiliate commission rate, in whole percent (spec 3.7).

Deliberately UNTYPED here. The rule (a whole number from 1 to 100) lives in the route and the service, so every refusal comes back as this module's {code, error} shape. Declared as int the endpoint had TWO error contracts: 0 and 101 answered invalid_rate while 50.5 and "abc" answered a raw Pydantic array, and only one of the two was the product's (round 14 walkthrough, finding 7).

json_schema_extra still documents the real shape, so Swagger and a generated client know it is an integer from 1 to 100. Documentation, not validation: that is what keeps the refusal in the handler.

The default=None is what keeps a MISSING key out of Pydantic's array too, so it has to stay, but a default publishes the field as OPTIONAL and it is not (Task 15 review, finding 7). The description says so, since that is the only half of "required" this shape can carry: omitting percent answers invalid_rate, the same refusal every other bad value gets.

One affiliate as the admin queue sees it.

Wider than the affiliate's own AffiliateView: it carries user_id and decided_by_user_id so the queue can link to the account and show who decided. payout_details is masked here exactly as it is everywhere else.