Skip to main content

Finalize Secondary Transaction

POST 

/v1alpha1/issuers/:issuerId/secondaryTransactions/:secondaryTransactionId:finalize

Scope(s): readwrite_issuer_secondarytransactions

Confirms that you have completed all money movement for the secondary 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 secondary transaction is identified by the path, and the request body is empty. The response returns the full secondary transaction as it now stands, nested under secondaryTransaction.

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, wait for the issuer to approve option cost. You'll be emailed when it's approved, or you can poll Get Secondary Transaction. Carta settles with the withholding the issuer approved there, which you read on each option grant's taxReference from Get Secondary Transaction.

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 TRANSACTION_CREATED and then 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.

After you finalize, if settlement fails or is deferred, the transaction returns to PENDING_SETTLEMENT; see that state. Calling Finalize Secondary Transaction again is safe and has no effect.

Retrying. This call is safe to retry. Once a Finalize Secondary Transaction has succeeded, calling it again returns the secondary transaction in whatever state it has since reached, including SETTLED, and does not notify the issuer a second time. A secondary transaction that was never finalized can only be finalized from PENDING_SETTLEMENT; from any other state, for example one still awaiting option cost review or one CANCELED, the call fails with 400.

Request​

Responses​

The full secondary transaction as it stands, nested under secondaryTransaction. Finalizing does not change state: the transaction stays PENDING_SETTLEMENT until the issuer approves the cap-table update. A retry after that returns whatever state it has since reached.