3. Handling Internal Marketplace Transactions (Transfers & Retirements)

Internal Transfer:

Marketplace Action: User A sells/transfers their internally tokenized VCU representation to User B within the Marketplace platform. The Marketplace updates its internal ledger.

Notification to Tero: The Marketplace calls reportTransaction with operation: Transfer, detailing the quantity, units (tCO2e or kgCO2e), source issuance, internal sender/receiver IDs.

Tero Action: Receives notification (202 Accepted). Admin reviews. If approved, Tero updates its internal records/metadata associated with the externalized VCU (e.g., noting the last known internal movement via the reporting marketplace), potentially updating the original operational NFT's metadata (set token URI). Sends confirmation/rejection [Webhook].

Internal Retirement:

Marketplace Action: A user requests to retire VCUs purchased on the Marketplace. The Marketplace executes this retirement within its system (e.g., burns its internal token representation, records the retirement details).

Notification to Tero: The Marketplace calls reportTransaction with operation: Retire, detailing the quantity, units (tCO2e or kgCO2e), source issuance, retirement reason/beneficiary.

Tero Action: Receives notification (202 Accepted). Admin reviews. If approved, Tero:

Updates the status of the corresponding native VCU in its registry to "Retired".

May update the original operational NFT's metadata (set token URI).

Reports the retirement to CAD Trust.

Sends confirmation/rejection [Webhook].