Integrity and AccountabilityPUBLICLY ACCESSIBLE CDR REGISTRIES
Lever last updated: 10 September 2026
Public registries tracking every credit's issuance, ownership, transfers and retirement.
Cost
Very low to Medium
Programme owners pay for software, account administration, data checks, security and support. Existing services cost less than building and maintaining large systems connecting several programmes or countries.
Complexity
Medium to High
Operators must define authoritative records, account permissions and correction procedures alongside the software. Connecting several public programmes adds legal coordination, data migration and reconciliation of transactions across systems with different rules.
Timeline
Very short to Medium
Prepared programmes using existing services can record live transactions within a year. Developing and testing a bespoke system connecting several programmes may take two to five years before reliable transactions.
Integrity, Transparency & MRV
Innovation & Cost Reduction
Social & Environmental Safeguards
Energy, Transport & Storage Infrastructure
Inputs & Capacity
Demand Formation
Bankability and Cost of Capital
Policy Architecture & Coordination
Overview
Governments and crediting-programme owners can establish or require publicly accessible registries of CDR projects and credits. Each credit receives a unique identifier, with records of issuance, holdings, transfers and final use or cancellation. This replaces fragmented or private information with a common record that buyers, regulators and the public can check. Buyers can check recorded issuance, holdings and retirement, while operators can block further transfers after a recorded unit has been used. CDR transactions and claims therefore become more traceable. The registry implements certification decisions without independently establishing removal quality; whether its entries establish legal ownership depends on applicable law.
Key Considerations
The programme owner must establish which record is authoritative and who authorises account access and changes. Retirement takes a unit out of circulation for a specified use; cancellation may remove it for other reasons, which should remain visible. Each unit needs links to its project, method, removal period, storage duration and certification evidence. Disclosure must support scrutiny while protecting justified confidentiality. Checks between registries are needed to detect the same project being credited elsewhere, since unique serial numbers within one system are insufficient. Records must also remain accessible if the operator changes or fails.
Opportunities
Public records let purchasers check a unit's recorded status and others examine whether a company's stated retirement occurred. Project documents and status histories make misleading claims and undisclosed changes easier to identify. Suppliers gain a standard source of transaction evidence; regulators can reconcile issuance and use; and authorised lenders can verify relevant holdings. Shared identifiers and data formats reduce manual reconciliation between programmes. These benefits depend on complete, current records connected to supporting evidence, making disclosure rules as important as the software.
Risks
Incorrect entries or unauthorised transfers can cause buyers to pay for units the seller cannot deliver. A transferable unit may also be promised or pledged elsewhere, so buyers must check rights and commitments beyond the public record. Users may mistake registration for proof of quality, while undisclosed information prevents scrutiny and excessive disclosure exposes sensitive data. Linking systems without preserving unit differences may imply that temporary and permanent storage are interchangeable. Operator failure can also strand records. Correction procedures, security checks and arrangements to preserve or transfer records are therefore necessary alongside public access.
Monitoring and Evaluation
Evaluation should test whether users can trace units from certification to their current status and recorded use. Missing fields, duplicate records, disputed transfers, publication delays and unresolved differences between systems reveal weaknesses. Outages and recovery tests assess reliability. Public users need a way to report errors and see their resolution, informing improvements to disclosure and account controls.
Stakeholder Engagement
Certification-scheme owners and verifiers should specify evidence for issuance and status changes. Developers, buyers and intermediaries should test transactions, while regulators check compatibility with their reporting systems. Civil-society users should test public scrutiny, supported by cybersecurity and privacy expertise. Landowners and communities can identify information needed for accountability and disclosure that would expose them unnecessarily.
Governance Levels
International mechanisms, public authorities and private programme owners can establish or require registries for schemes they govern. Regional and municipal programmes may use shared services instead of building separate systems. Companies, industry standard-setters and philanthropic organisations can operate or commission public registries where they govern a crediting programme. Providing funding or publishing a list of purchases is insufficient on its own. The programme owner must assign authority over records and remain accountable for their operation.
Implementation Strategies
Programme owners should define the transactions and public checks the registry must support before selecting software. They should identify the authoritative record, responsible administrator and rules for correcting errors or resolving disputes.
Operators should require evidence of certification before issuance and preserve each unit's link to its project, method and removal period. Account permissions and status controls should prevent transfers of retired, cancelled or suspended units.
Public interfaces should make unit status, certification evidence and recorded retirement uses searchable. Disclosure rules should identify legitimate confidentiality exceptions and publication deadlines so that withheld information does not make claims impossible to check.
Operators should test security, identity checks, backups and recovery before live use. Contracts should guarantee access to records and their transfer to a replacement operator if the service closes or fails.
Programmes that exchange units or data should agree common identifiers, retain the original unit history and reconcile records regularly. Checks should cover duplicate project registration as well as duplicate serial numbers, with clear action when inconsistencies are found.
Case Studies

Puro Registry
Puro.earth, a private provider of standards and certification for durable carbon removal, operates the Puro Registry. Its public interface links certified projects with credit issuances and retirements, including the organisations for which credits have been retired. Buyers and other users can therefore inspect recorded activity rather than rely solely on a supplier's statement that credits exist or have been used. The operator updates data daily, but records before January 2022 require both parties' consent for publication, and beneficiaries may request publication delays of up to twelve months. The case provides operational CDR-specific evidence of the registry mechanism and shows why disclosure rules matter alongside unique unit identifiers. An undisclosed retirement is harder for an outside observer to verify.

The Paris Agreement’s Article 6.4 interim registry
The UN climate convention's secretariat developed an interim registry for Article 6.4, the Paris Agreement's UN-supervised crediting mechanism. Its September 2025 user guide describes account opening, issuance, transfers and public information. Users submit forms and administrators process transactions manually, allowing core recordkeeping to begin while the final digital system is developed. Different unit types record permitted uses, while authorisation conditions and some international-accounting information require separate manual records. The guide states that the interim system is not interoperable with other relevant registries. The implementation lesson is that a registry needs governed transaction procedures before sophisticated automation, with explicit controls for functions the interim service cannot perform. The guide does not establish issuance of removal-specific credits.

The European Union’s carbon-removal certification registries
The EU's 2024 Carbon Removals and Carbon Farming Certification Regulation requires the European Commission to establish a Union registry by 27 December 2028. Until then, recognised certification schemes must maintain public, interoperable registries. Units may be issued only after the relevant net benefit has occurred and a valid certificate confirms it; permanent removals, carbon farming, carbon stored in products and soil emission reductions must remain distinct. The mechanism combines a legal duty to publish certification information with records that trace issuance and use across schemes. It gives programme owners a common destination for their records while permitting interim infrastructure. The statutory deadline is a planned delivery requirement, not evidence that the Union registry already operates.
More Integrity and Accountability

Measurement, Reporting and Verification Protocols
A common rulebook specifying how projects must measure, report and verify their removals.
Cost
Very low to Low
Complexity
Low to High
Timeline
Short to Medium
Integrity, Transparency & MRV
3–5Innovation & Cost Reduction
1–2Social & Environmental Safeguards
1–2Energy, Transport & Storage Infrastructure
N/AInputs & Capacity
1–2Demand Formation
1–2Bankability and Cost of Capital
1–2Policy Architecture & Coordination
2–4
Certification schemes
Independent assurance that a removal project and its results meet defined quality standards.
Cost
Very low to Medium
Complexity
Low to High
Timeline
Short to Medium
Integrity, Transparency & MRV
3–4Innovation & Cost Reduction
1–2Social & Environmental Safeguards
2–4Energy, Transport & Storage Infrastructure
N/AInputs & Capacity
1–2Demand Formation
1–2Bankability and Cost of Capital
1–3Policy Architecture & Coordination
2–4
Carbon credit legal status
Legislation or guidance clarifying what legal rights a carbon credit holder actually has.
Cost
Very low to Low
Complexity
Low to High
Timeline
Short to Medium
Integrity, Transparency & MRV
2–3Innovation & Cost Reduction
N/ASocial & Environmental Safeguards
N/AEnergy, Transport & Storage Infrastructure
N/AInputs & Capacity
N/ADemand Formation
1–3Bankability and Cost of Capital
2–3Policy Architecture & Coordination
3–4©2026 Alexander Mäkelä and Carbon Gap.
Except where otherwise indicated, this work is licensed under the Creative Commons Attribution–NonCommercial–ShareAlike 4.0 International Licence.
Headline and barrier scores based on Carbon Gap analysis.