Integrations

Plug BTR Prime’s Article 6 operations into your systems — readiness, evidence, allocation, and escrow — with clean guardrails and lightweight onboarding.

View API & webhooks See data model

LoA → CA → AEF → BTR · evidence-led

What we integrate

Readiness signals (country “green-lane” status and cadence)
Evidence vault (LoA refs, validator acceptance, CA docs, BTR drafts/citations)
Allocation ledger (RFO/RFR priority & buyer windows — single source of truth)
Pre-BTR confirmation — AEF parity memo for host × acquiring before BTR publication
Escrow events (releases & refunds/rolls; 80/20 buyer escrow logic)
Insurer analytics (loss-avoidance telemetry, corridor memos)

Operating model (simple, guarded, auditable)

Single-ledger allocation: prevents double-selling and channel conflict; documents RFO/RFR priority and buyer RFR windows.
Evidence-first workflow: every state change is backed by files and timestamps.
Alliance-aware: plays nicely with exchanges, brokers, registries, funds, and carriers via clear SLAs.
Sovereign-first: governments never pay; success payments are programme-funded and visible as events.
UNFCCC-consistent claims: we enable recognition/reporting — we don’t promise policy outcomes.

Core data model (entities)

Country

Readiness score, DNA contacts, BTR schedule, registry status.

Project

Type/method, owner, estimated volume (t CO₂eq), MRV posture.

Milestone

M1 Initiation → (optional) Pre-BTR confirmation → M2 BTR published.

EvidenceFile

Hash, source, version, reviewer, link.

AllocationWindow

Trader priority band; buyer acceptance window (RFR inside).

EscrowRelease

Buyer escrow: 80% creditable; 20% reservation/admin at M1. Releases: 50% at M1, 50% at M2.

Extended objects include LoA, CADocument, AnnualInformation (AEF), AIParityMemo (optional), and BTRCitation.

{
  "projectId": "PRJ-2025-0042",
  "country": "XX",
  "milestones": [
    {"code":"initiation","status":"Completed","date":"2026-02-14","evidence":["workplan.pdf"]},
    {"code":"pre_btr_parity","status":"Matched","date":"2026-11-28","evidence":["aef_parity_memo.pdf"]},
    {"code":"btr_published","status":"Published","date":"2027-01-15","evidence":["btr_citation.txt","registry_link.txt"]}
  ],
  "allocation": {"rfoRfrBandMt": 2.5, "buyerWindow": {"opens":"2026-12-01","acceptDays":10}},
  "escrow": {
    "total": 250000,
    "creditablePct": 0.80,
    "reservationFeePct": 0.20,
    "releases": {"M1_initiation":0.50,"M2_btr_published":0.50}
  }
}

APIs & webhooks

Use the REST API for reads/writes and webhooks for milestone and allocation events. CSV uploads and portal UI are always available as a fallback.

Endpoint	Method	Purpose
/v1/countries	GET	Readiness signals & BTR schedules
/v1/projects	GET/POST	Register & query projects
/v1/milestones	GET/POST	Advance milestones (codes: initiation, pre_btr_parity, btr_published) with evidence
/v1/evidence	POST	Upload files (hashing + versioning)
/v1/allocations	GET/POST	Trader bands & buyer RFR windows
/v1/escrow	GET	Release/refund/roll events (80/20 model; M1/M2 releases)
/v1/a6/ca-docs	GET/POST	Record & fetch corresponding adjustment basis/docs
/v1/a6/annual-info	GET/POST	Host/acquiring Annual Information (AEF) entries
/v1/a6/ai-parity	POST	Compute & store AEF parity memo for given year(s)
/v1/reports	GET	Portfolio, KPIs, audit extracts

Webhooks

milestone.reached — includes evidence list and reviewer
allocation.opened — window dates and acceptance period
escrow.released — milestone (M1/M2), % released, balance remaining
a6.ca.documented — CA basis filed + registry reference
a6.aef.parity_confirmed — host × acquiring entries match for year(s)
btr.published — citations and annex refs attached

Auth: API key or OAuth2; IP allowlists available. Rate limits sized for portfolio operations, burstable for cutovers.

Security & compliance

SSO: SAML/OIDC; RBAC with least-privilege roles (Gov, Trader, Buyer, Developer, Insurer, Partner)
Encryption: TLS 1.2+ in transit; AES-256 at rest; file hashes (SHA-256) with version history
Privacy: minimal PII; DPAs available; EU data residency options
Audit: immutable event log; evidence linkbacks; exportable trails for insurers/auditors

Implementation timeline

Week 1 — Sandbox keys, object mapping, sample data

Weeks 2–3 — Wire events (milestones, allocations, escrow, CA/AEF parity)

Week 4 — Production cutover; first audit extract

CSV/portal can launch in days; APIs add automation and scale.

Integration tiers

Tier	Interfaces	Who it suits
Basic	Portal + CSV	Pilot programmes; minimal IT lift
Standard	API + Webhooks + CSV	Desks & registries with portfolio flow
Enterprise	SSO, custom mappings, DPA	Carriers, exchanges, global buyers

Example workflows

Buyer Allocation Notice → webhook to your OMS → auto-create purchase task with evidence pack link
Trader band consumption → decrement RFO/RFR band as projects hit initiation and btr_published → ledger export nightly
Ministry success payment → M1/M2 events trigger escrow release → mirrored in donor/trader reporting
Insurer analytics → milestone telemetry feeds corridor repricing memo each quarter

Governance & guardrails

Conflict-free routing: single ledger; documented priorities; no double-selling
Claims discipline: UNFCCC-consistent wording; we enable recognition/reporting—no policy guarantees
No government payers: ministries receive success payments from programme funds only

Support & SLAs

Response targets: Sev1 4h, Sev2 1 business day, Sev3 2 business days
Environments: Sandbox & Production; change windows with rollback plan
Reporting: quarterly KPI pack (on-time milestone rate, variance, allocation utilization)

Request sandbox access

We’ll provision API keys, webhook endpoints, and sample objects — then align your first country lane.

Request access See Readiness Tracker