Finalize Settlement
POST/v1alpha1/issuers/:issuerId/secondaryTransactions/:secondaryTransactionId:finalize
Scope(s): readwrite_issuer_secondarytransactions
Confirms that you have completed all money movement for the transaction — on the option path the exercise cost and taxes to the issuer plus the sale proceeds, on the certificate path the sale proceeds. Required on both paths. The transaction is identified entirely by the path; send an empty body.
On the certificate path you may move money any time before calling this, as there is no withholding to wait for. On the option path you cannot compute what to move until the issuer has approved option cost and Carta has released the withholding figures, so call this after that.
Finalizing does not itself commit the cap table. Carta emails the issuer, who approves or edits the proposed cap-table update and provides the transfer agreement for the trade; on approval the transaction moves to SETTLING, and Carta then creates the exercise for option grants, transfers the certificate, and commits the update, reaching SETTLED.
By this point your money movement is complete and irreversible, so the settled notification is a reconciliation signal, not a payment trigger.
Request
Responses
- 200
- 202
- 400
- 401
- 403
- 500
- default
A successful response.
Your money movement was accepted and the transaction was advanced for settlement. Settlement completes asynchronously — read the transaction to observe it reach SETTLED.
Returned if required fields are omitted or if provided fields fail validation.
Returned if a valid Authorization header has not been included with the request.
Returned when the user does not have permission to access the resource.
Returned if an unexpected internal server error is encountered.
An unexpected error response.