Settlement rule execution finished webhook
Fired once when a settlement rule’s execution on an incoming payment finishes, with the execution:
SETTLEMENT_RULE.EXECUTED: its payout run finishedCOMPLETEDorPARTIALLY_FAILED.payoutRunIdnames the run, whose ownPAYOUT_RUN.*webhook carries the row counts.SETTLEMENT_RULE.FAILED: its payout run finishedFAILED, or was cancelled withPOST /payout-runs/{payoutRunId}/cancel. The customer keeps what the run did not pay. A cancelled run still pays the shares whose payments had started; its rows say which.SETTLEMENT_RULE.SKIPPED: nothing was paid;skipReasonsays why.
Each share’s transaction sends its own OUTGOING_PAYMENT.* webhooks.
This endpoint should be implemented by clients of the Grid API.
Authentication
The webhook includes a signature in the X-Grid-Signature header that allows you to verify that the webhook was sent by Grid.
To verify the signature:
- Get the Grid public key provided to you during integration
- Decode the base64 signature from the header
- Create a SHA-256 hash of the request body
- Verify the signature using the public key and the hash
If the signature verification succeeds, the webhook is authentic. If not, it should be rejected.
Authorizations
Secp256r1 (P-256) asymmetric signature of the webhook payload, which can be used to verify that the webhook was sent by Grid. To verify the signature:
- Get the Grid public key provided to you during integration
- Decode the base64 signature from the header
- Create a SHA-256 hash of the request body
- Verify the signature using the public key and the hash
If the signature verification succeeds, the webhook is authentic. If not, it should be rejected.
Body
Response
Webhook received successfully