Settlement APIs enable the allocation of settled funds across multiple recipients. A settlement allocation request specifies how a received amount should be distributed. Wise processes each allocation as an individual payment intent that can be tracked through completion.
Creates a new settlement allocation request with a Settlement Allocation Request (SAR) file containing payment intents.
This endpoint requires HMAC request signing in addition to a bearer token. See HMAC request signing for the full algorithm, a verified test vector, and troubleshooting.
Unix timestamp in seconds at which X-Signature was generated, as a decimal string.
This value is part of the signed canonical string, so it must exactly match the timestamp used to compute the signature. Requests more than 300 seconds from Wise server time are rejected in either direction.
Optional UUID for correlating requests across systems. If provided, Wise echoes it back in the response. Maximum 36 characters. Learn more.
- Production Environmenthttps://api.wise.com/2027Q1/settlement/allocations
- Sandbox Environmenthttps://api.wise-sandbox.com/2027Q1/settlement/allocations
curl -i -X POST \
https://api.wise.com/2027Q1/settlement/allocations \
-H 'Authorization: Bearer <YOUR_JWT_HERE>' \
-H 'Content-Type: multipart/form-data' \
-H 'X-External-Correlation-Id: f47ac10b-58cc-4372-a567-0e02b2c3d479' \
-H 'X-Signature: YOUR_API_KEY_HERE' \
-H 'X-Signature-Timestamp: YOUR_API_KEY_HERE' \
-F 'command={"paymentReference":"PAY-2024-001234","expectedTotalAmount":10000,"currency":"USD"}' \
-F file=stringSettlement allocation request accepted
Echoed back when X-External-Correlation-Id was included in the request. Learn more.
State of a funding allocation.
{ "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "expectedTotalAmount": 10000, "currency": "USD", "state": "NEW", "paymentReference": "PAY-2024-001234", "createdAt": "2019-08-24T14:15:22Z", "updatedAt": "2019-08-24T14:15:22Z" }