A working guide to operating a carbon registry account for an ocean project: onboarding, issuance workflows, serial numbers, transfers and pitfalls.
Somewhere between a verified monitoring report and a company announcing "we have retired 10,000 tonnes of blue carbon," a small, unglamorous administrative reality takes place: someone with registry login credentials submits an issuance request, receives a block of serial numbers, moves some of them to a buffer account, transfers some to a buyer and retires others. This article is about that desk — the operational layer where ocean carbon projects actually touch the market.
We have two companion pieces for context. What Is a Carbon Registry? covers the conceptual plumbing — what a registry guarantees and what it cannot — and Ocean Credit Registries maps the landscape through a buyer's diligence lens. This article is for the project team and the operational buyer: the workflows, the account structures, the serials, and the quiet discipline that keeps double counting, wrong retirements and audit findings from happening.
A registry account is not self-service like a bank app. Before a project team can hold credits, the organisation typically goes through a know-your-customer process — corporate identity, beneficial ownership, sanctions checks — and designates authorised account managers. The details sound pedestrian until a team's only authorised signatory leaves in the middle of a delivery window; account-governance hygiene is a real project risk.
Parallel to account setup runs the project listing. The developer submits a project design document, the applied methodology, the validation report from an approved auditor, tenure and consent evidence, and stakeholder consultation records. Once listed, the project has a public page: boundaries, expected issuance, documents and status. "Listed" is not "issuing" — the page announces intent, and the market can now watch.
Think careful thought about who acts for the project: the registry will want to know who may submit monitoring reports, request issuance, transfer credits and retire. The strongest practice is split authority — at least two people required for value-moving actions — for the same reason any financial system demands it.
Issuance is where measurement becomes a tradable unit. The sequence, in practice:
Timing is worth respecting. A monitoring cycle that closes in March may not yield issued credits until months later. Buyers planning retirements for reporting-year-end often schedule purchases against issued stock for exactly this reason — or contract forward and accept the timing risk, as our offtake and project-cycle articles unpack.
A serial is not decoration — it is the credit's identity. A typical structure (format varies by registry) encodes the registry, the project identifier, the vintage or monitoring period, and the numeric block range, something like REG1-KL-0231-2026-0001-0500, meaning: this registry's kelp project 231, 2026 vintage, units 1 through 500. From a single serial you can look up: which project, which standard's methodology, which vintage, which block, and the credit's current status (issued, transferred, retired, cancelled).
Operational rules worth enforcing internally:
Every credit operation reduces to three verbs, and teams blur them at their peril.
Transfer moves credits from the project's account to another account — the buyer's. Ownership changes; the credit remains live and tradable. Transfers settle like a depository system: both accounts updated, public record updated.
Retirement permanently freezes a credit to support a climate claim. The retiring party's name, the beneficiary (if retired on behalf of a client), and the purpose are recorded. Retirement is what the company's report, the marketing claim and the net-zero disclosure all ultimately stand on — and it is irreversible, which makes the checking step before retirement the one that matters.
Cancellation retires a credit without an associated claim — the buffer pool deposit is the standard case. Buffer cancellations insure the whole system against reversal events; if a storm wipes out a marsh, buffer credits are cancelled to compensate, keeping total claims matched to total surviving carbon.
A subtle distinction that trips teams: retiring on behalf of. A broker or developer may retire in its own account for a buyer's benefit — but the beneficiary field must name the claimant correctly, or the audit trail between the buyer's report and the registry record breaks. Sloppy beneficiary fields are among the most common findings in carbon-claim audits.
A professional project keeps three books and reconciles them monthly:
The three must tell one story. When a journalist or auditor checks the public registry record against the company's disclosure, any discrepancy is a finding. The discipline is mundane: monthly serial-block reconciliations, documented approvals for retirements, an owner for the registry relationship, and an exportable audit trail. Tidewright's fictional Canopy Ledger platform automates this consistency; real projects still lean on registries' public exports and their own spreadsheets — and either way, the discipline, not the software, is what protects the claim.
Where credits are authorised for international transfer under the Paris Agreement's Article 6, an additional record exists: the host country's registry or tracking system must apply a corresponding adjustment so the tonne is not claimed by both the buyer and the host nation's NDC. Operationally this means the serial's status in the carbon registry and the accounting entry in the national system must match. Early movers document both explicitly; late movers discover the mismatch in an audit. Good registry practice today is: if Article 6 applies, record which national system tracks the adjustment, and carry that reference on the serial-level file.
Generally, organisations that complete the registry's onboarding and KYC process: developers, buyers, brokers and financial institutions. Account access is governed by the registry's terms, and authorisations (who can transfer, retire, submit reports) are configured at setup — and should be reviewed as staff change.
Weeks to months is honest. The registry reviews the request against the standard's requirements before minting serials, and verification itself has its own timeline. Projects building a delivery schedule for buyers should plan against a conservative issuance calendar, not a hopeful one.
Both permanently freeze the credit. Retirement associates the freeze with a claim — a company's offset, a neutralisation narrative, a purpose field in the public record. Cancellation freezes the credit with no claim attached, which is what buffer-pool deposits are.
Serialisation plus the registry's single-owner ledger: each unit lives in exactly one account at a time, and any transfer or retirement is public. Within a well-run registry, double selling is structurally impossible; across registries it's prevented by transfer rules and increasing meta-tracking — our double-counting explainer maps the wider picture.
Yes — credible registries publish project pages, issuance and retirement records publicly. A buyer can verify, without any login, whether a serial exists, who retired it and when. If a seller can't produce the public record, the simplest response is to walk away.
Every carbon credit lives or dies by its registry — the database that issues, tracks and retires it. Here's what registries do and why serial numbers matter.
Priya Raman ·
How carbon registries issue, serialise, track and retire blue carbon credits — and what buyers should check before trusting a listing.
Priya Raman ·
A carbon credit only becomes a climate claim when it's retired on a registry. Here's what retirement means, how to check it, and why the details matter.
Priya Raman ·