Update a settlement rule
Change a rule the authenticated agent created. Send only the fields to change.
At once: name, status (ACTIVE or PAUSED), holdSeconds and achHoldSeconds apply when the request is made.
Changes that can move more money: match, splits and limits are checked as on create, on the rule as they would make it. When that rule is within the agent’s policy, as POST /agents/me/settlement-rules decides, the change applies at once. Otherwise it waits for the customer’s approval as an UPDATE_SETTLEMENT_RULE agent action, named by pendingChangeActionId, and the AGENT_ACTION.PENDING_APPROVAL webhook fires. Until the action is decided the rule keeps its current match, splits and limits. The fields that apply at once still do, so a request that also sets status to PAUSED pauses the rule straight away. Approving the action checks the change again and applies it; rejecting it, or letting it expire after seven days, drops it. A rule has at most one change waiting.
splits replaces every share and limits replaces both limits, as on PATCH /settlement-rules/{settlementRuleId}. An agent cannot change priority.
Requires the MANAGE_SETTLEMENT_RULES permission.
Authorizations
Bearer token authentication for agent-scoped endpoints. The token is the accessToken returned when redeeming a device code via POST /agents/device-codes/redeem. Agent credentials are user-scoped: all requests are automatically bound to the agent's associated customer and subject to the agent's policy.
Body
The fields to change. A field left out is unchanged.
Response
The rule, with any change that waits for approval named by pendingChangeActionId