Skip to main content
The public Trust Center at cbpayapp.com/trust lists public compliance records and explains how to request the gated N2 room. The gated documents are provider-agnostic compliance evidence; bytes are released only after the external contact signs the NDA. No CBPay account is required.

Flow

1

Request access

Send the company, contact and purpose. The same company plus email while pending is idempotent.
Response (202, or 200 with idempotency_hit: true on replay):
2

List available document metadata

Metadata is public; document bytes are not.
Response (200):
3

Review and sign from the email

Open the personal link. The page is public and no CBPay session is needed. Submit the signer identity, company registration, address and accept: true. The response contains the raw download token once.
Response (200):
4

Check status and download

Use the download Bearer token. Each PDF response includes X-Checksum-Sha256 and Cache-Control: no-store; every delivery is audit-recorded.
Status response (200):

States and errors

See the error catalog for counsel_pending, invalid_token, unknown_document, already_decided, accept_required, email_unavailable, entitlement_revoked and entitlement_expired.

FAQ

No. The contact uses the personal signing and download tokens from email.
Yes. Reusing the same company and contact email while pending returns the existing request and does not send a duplicate envelope.
true means delivery was handed to the configured email service; false means the request exists but delivery failed. Do not log or expose raw tokens.
Five years after signing, unless compliance revokes the entitlement sooner.
Last modified on October 20, 2026