Issue and Accept Stock

Acceptance is an optional, standalone event. Use it when the stakeholder confirms receipt of an existing issuance and you want that confirmation to land as its own history row — typical for regulatory or audit signal. If acceptance is implicit at issuance time, skip this page.

For the issuance itself, use Issue Stock.

Inputs

Field	Source
`issuerId`	`POST /issuer/create` or `POST /issuer/register`
`stakeholderId`	`POST /stakeholder/create`
`stockClassId`	`POST /stock-class/create`
`security_id`	Canonical issuance/history row written from the onchain event

Accept stock

POST /transactions/accept/stock

{
    "issuerId": "<YOUR_ISSUER_ID>",
    "data": {
        "stakeholderId": "<YOUR_STAKEHOLDER_ID>",
        "stockClassId": "<YOUR_STOCK_CLASS_ID>",
        "security_id": "<YOUR_SECURITY_ID>",
        "comments": ["Accepted by stakeholder"]
    }
}

Response:

{
    "stockAcceptance": {
        "id": "<GENERATED_ACCEPTANCE_ID>",
        "object_type": "TX_STOCK_ACCEPTANCE",
        "security_id": "<YOUR_SECURITY_ID>",
        "date": "2026-01-01",
        "comments": ["Accepted by stakeholder"]
    }
}

Reuse the same security_id for accept, cancel, retract, reissue, and repurchase. Acceptance does not change holdings; it only records the event.

Verify

Holdings: GET /cap-table/holdings/stock?issuerId=<YOUR_ISSUER_ID>
History: GET /historical-transactions/issuer-id/<YOUR_ISSUER_ID> — expect a new TX_STOCK_ACCEPTANCE row after polling (~20 s on Plume Mainnet).

Next: View Cap Table or Transfer, Cancel, and Reissue Stock.

Add Supporting Records View Cap Table