OPERATIONS · operating reference

Noncustodial invoice integration guide

A reference for separating a payment request, independently observed settlement, and a payment processor's own invoice state.

Reference center

What this page establishes

A payment URI does not prove payment.

Self-hosted or third-party invoice infrastructure has separate security and availability boundaries.

CoinPork can request an invoice only through a member-configured BTCPay instance and never holds its wallet keys or funds.

BTCPay Server Greenfield API

Practical review sequence

1

Use a restricted store API key and protect the BTCPay host.

2

Verify destination, asset, amount, and signed webhook state.

3

Document which system is authoritative for invoice state, exchange rate, refund, and settlement.

Configure optional BTCPay checkout

Recheck primary sources before acting

Contracts, names, issuers, governance, bridges, providers, networks, fees, and access rules can change. CoinPork provides an operating checklist, not financial, legal, tax, accounting, or cybersecurity advice.