Skerry/ Reference/ Customer controls
Customer controls11
Controls set on one customer that apply to every caller, whatever its mandate: holding the first payout to a destination the customer has never paid, a cooling-off period, velocity and anomaly rules, a withdrawal allow-list, and the people who approve held operations by email. Every control is off until it is set, and an agent's own credential cannot change one.
- How a new destination is treatedget/customers/{id}/payee-controls
- Customers payee controls replaceput/customers/{id}/payee-controls
- Customers trusted payees listget/customers/{id}/trusted-payees
- Trust a destination before it is first paid, so that payout is not heldpost/customers/{id}/trusted-payees
- The customer's velocity and anomaly rules. A rule that is null is offget/customers/{id}/risk-rules
- Replace the customer's risk rulesput/customers/{id}/risk-rules
- The destinations this customer's payouts may go toget/customers/{id}/withdrawal-allow-list
- Replace the withdrawal allow-listput/customers/{id}/withdrawal-allow-list
- The customer's approvers, and whether this deployment sends mailget/customers/{id}/approvers
- Customers approvers createpost/customers/{id}/approvers
- Remove an approver. `?email=`delete/customers/{id}/approvers