Skip to main content
This page is a comprehensive reference for every privacy setting and control available in Monaris.

Privacy defaults

Data typeDefaultUser can change to
Payment amountsPrivatePublic (opt-in)
Counterparty identitiesPrivatePublic (opt-in)
Invoice detailsPrivate to partiesShareable with specific parties
Monaris ScorePrivateShareable (Score Card, Profile, or API)
Cashflow summaryPrivateSelective disclosure
Transaction historyPrivateVerifiable proof without raw data

Privacy features by plan

FeatureFreePay UserBusiness
Private payments by default
Custom privacy per transaction
Private invoicing (hidden amount)
Selective disclosure proof
Privacy audit log
Team-level privacy policy
Programmable privacy rules
Compliance disclosure mode

Programmable privacy rules (Business plan)

Rules you can define that execute automatically:
  • Amount threshold: “All payments above $5,000 are always private”
  • Counterparty-based: “All payments to Vendor A are private”
  • Category-based: “Payroll payments are private — but generate a verifiable receipt”
  • Time-based: “Payments between 9pm–6am are private”
  • Default override: “Public by default, except when paying category = personal”
  • Score carve-out: “All payments private — but Score data is shareable”

Selective disclosure options

What you can proveWithout revealing
Payment happenedAmount or counterparty
Amount within a rangeExact amount
On-time paymentFull transaction details
Income above a thresholdExact income
Score above a thresholdExact Score

Compliance mode

Available to Pay User and Business plans:
  • Targeted disclosure to a named regulatory authority
  • Does not make data public
  • Full audit log of every disclosure
  • User notified before any disclosure
  • Privacy preserved for all other purposes

What is never exposed

  • Raw transaction data to third parties without user consent
  • Private payment details on the public blockchain
  • Off-chain data to anyone other than user and authorized connections
  • Score factors at individual transaction level

Proofs

  • Cryptographic proofs verify claims without revealing underlying data
  • Proofs are generated on user behalf and stored in their account
  • Users control which proofs are shared with which parties
  • Proofs can have expiry dates and can be revoked