How it works
One rule never bends: no certificate shows green until the removal is verified and custody is proven. Not promised. Proven. Below: what enters the record at each stage, what proves it, and what an auditor can read back — for every credit you hold, whichever registry issued it.
Follow one 1,250-tonne certificate from filing to retirement. Chapter four is the one where a hand-off goes missing, and the record says so.
Select a chapter
Delivered and proven. Not promised. Proven.
| Stage | What enters the record | What proves it | What the auditor reads |
|---|---|---|---|
| 01 Register | Issuer, methodology, project, vintage, tonnage — recorded as filed, with the filing date and the recording date. | Nothing yet. A registered certificate is a claim on file, and the record says so. | Intake reference, unmodified source documents, and who recorded them. |
| 02 Verify | Verification body, statement, scope and date — attached to the certificate, not to a summary. | A document hash on file. Only here may a record turn green. | The statement itself, its SHA-256, and the date it was checked. |
| 03 Transfer | Both parties, the serial range, and both dates: when custody moved and when we recorded it. | Registry confirmation, reconciled at serial level where an adapter exists. | A custody chain with no gaps — or a stated gap where none was recorded. |
| 04 Retire | Retirement reference, beneficiary, date — final and not editable afterwards. | The registry’s own retirement record, referenced by ID. | An export that follows one tonne from filing to retirement, hashes included. |
This is the view a sustainability manager opens before a reporting call: four exclusive stages that sum to the portfolio, technology within each, and nothing green until it is proven.
Dates as published. Where a date is not yet fixed, it says so.
Compiled 28 July 2026. CDR Hub is CRCF-ready; CRCF certification is issued by certification bodies, not by us.