Create a settlement rule
A standing instruction on a customer’s incoming payments. When a
payment into one of the customer’s internal accounts completes and
matches the rule, Grid splits it by the rule’s shares and pays each
share from the account the payment credited, through a payout run.
Each share sends the usual OUTGOING_PAYMENT.* webhooks.
Matching: a payment matches when it is in the rule’s currency and
any selector in match matches it. A customer’s rules are tried in
ascending priority, which is unique among its rules that are not
DELETED. The first ACTIVE rule that matches wins, so a payment
pays out under at most one rule.
Shares: a PERCENT share is the payment times basisPoints over
10,000, rounded down. A FIXED share is amount. A REMAINDER share
is what every other share leaves, wherever its row is; there is at
most one. Without one, the customer keeps the rest. Shares are paid,
and listed, in row order. The percentages add
up to at most 10,000, and to less than 10,000 with a REMAINDER
share. When a payment is smaller than its fixed and percentage shares
together, nothing is paid.
Destinations: the payout run row destinations. An ACTIVE
external account of the platform or of one of its customers. A
contact, held for a claim as on a payout run. An internal account of
the platform (GRID_CUSTOMER), paid as a transfer between internal
accounts under the rules of a quote between them.
Limits: a customer has at most 50 rules that are not DELETED,
and a rule has at most 20 shares.
Requires an API token with the UMA_TRANSACT permission. The rule’s
shares are paid as that token. Once the token is deleted, expires or
loses the permission, the rule pays nothing more and is paused.
Authorizations
Headers
Body
Response
The rule this Idempotency-Key already created