Protect account numbers when sharing a bill

The key point

Settlemont can encrypt provider account references and compare keyed fingerprints without publishing the original number or even the last four digits.

What to do

1. Enter account references only in the private workflow.
2. Never repeat the number in the public summary.
3. Use the verification result as the public signal.

What to avoid

What happens next

The privacy goal is not to hide whether a bill is real; it is to avoid publishing information that is unnecessary to understand it. A reviewer can work from the private statement while the public profile uses a smaller set of approved facts. That reduces exposure of addresses, account references, IDs, and sensitive context.

How funding can work

Funding does not change the privacy boundary. A sponsor can define program rules and receive aggregate or permitted reporting, but that does not give the sponsor access to private source documents or the ability to buy a verification label.

Before you submit or help

An account number is evidence for private verification, not a public trust badge. Settlemont can encrypt provider account references and compare keyed fingerprints without publishing the original number or even the last four digits. The original bill should stay private; the public page, when approved, is built from a smaller reviewed set of facts. Posting or verification does not guarantee payment, and live payment availability depends on a supported biller or payment rail.

Related resources