Skip to content

Private Payments / Enterprise design

Your payment history
can reveal your business.

Public transfers can expose customer relationships and payment patterns. We're developing an enterprise approach to reduce that linkage while preserving invoice records.

Not a self-serve feature. Production availability depends on provider validation and integration testing. This is not a guarantee of anonymity.

The exposure

A shared receiving address
connects the dots.

When every payment reaches the same public wallet, an observer can group its transfers. Amounts and timing can reveal patterns even when invoice details are encrypted.

Illustrative public payment pattern

  • Customer payment A→ Same recipient
  • Customer payment B→ Same recipient
  • Customer payment C→ Same recipient

Encrypting an invoice does not hide the transfers to its recipient.

The proposed approach

Separate recipients.
Retain the invoice record.

The current design uses a separate recipient for each invoice and a provider-managed transfer path. Coinbase Prime integration capabilities must be validated before this can be offered in production.

  1. Set up the enterprise integration

    Confirm the provider account, supported transaction flow, and approval policies with your team.

  2. Assign an invoice recipient

    A per-invoice wallet owns the invoice NFT and receives its payment. Reusing a recipient can link that customer's invoices.

  3. Approve onward transfers

    The design requires merchant approval through the provider. It is not an automatic sweep controlled by Cleared.

Privacy has limits.
They belong in the plan.

Linkage can remain possible
Timing, amounts, and gas funding may still let observers associate transfers. The design must be tested against these risks.
Records still matter
Your team needs invoice and payment records for accounting and review. Access and export requirements should be agreed during integration.
Approval and custody are explicit
The intended model does not give Cleared fund-moving key material. Provider arrangements and your approval responsibilities need to be reviewed before launch.

Bring your privacy requirements.

Talk to our team