422
fees.invalid_planfeesRule R9The fee plan version is not valid
One rule validates a whole plan version: at least one component, unique component refs, percent_bps within 0–10000, vat_bps within 0–2000, no negative fixed_minor, min_minor or max_minor, and min_minor not above max_minor when both are set. The offending field is named in errors.
Why the API refuses
WHEN a plan version is created or updated, THE SYSTEM SHALL reject it unless it has at least one component, every component ref is unique, every percent_bps is between 0 and 10000, vat_bps is between 0 and 2000, every fixed_minor, min_minor and max_minor is not negative, and min_minor is not greater than max_minor where both are greater than zero, naming the offending field in errors.
What to do
Read errors[].field. The basis-point units are the usual trip: 2.9% is 290, not 2.9 and not 29.