Compliance, in plain terms.
How PurserPay is built, who holds what, and why moving your own money to your own team stays your decision from first click to last. No jargon, no fine-print games — the same posture we describe to prospects, written down.
Non-custodial architecture & disintermediation
PurserPay is software, not a financial intermediary. Our disperse contract is ownerless and immutable — there are no admin keys, no pause switch, and no upgrade path that could let anyone, ourselves included, reach your capital or alter a transaction. Every payout is directed entirely by you and settles atomically: the full batch clears in a single transaction from your wallet straight to your recipients, or none of it does. PurserPay never holds, pools, or intermediates your funds at any point in the flow.
B2B corporate billing framework
To issue standard commercial software invoices and license PurserPay to a business, we collect only what corporate billing genuinely requires:
- ✓Legal name / entity — the business being invoiced.
- ✓Country of incorporation — for jurisdiction and tax treatment.
- ✓Tax ID — the VAT / tax registration number.
That is the entire list. We do not request passports, government-ID scans, selfies, liveness checks, or any biometric data. This is B2B billing information — not identity surveillance.
Data dissociation & GDPR compliance
Two tiers of data, two rules — so your identity is never tied to your payout activity:
- ✓Your roster stays on your device. Payee names, wallet addresses and amounts live only in your browser’s local storage (IndexedDB). The roster is never uploaded to our servers in readable form — the only thing that ever leaves your browser is a transaction you sign yourself.
- ✓Your billing PII is encrypted at rest. Legal name, country and tax ID are stored server-side, encrypted with AES-256 (pgcrypto) at the database layer, and dissociated by design from any payout data.
Right to erasure (GDPR Art. 17): a deletion request wipes your billing PII from our database. Your roster is already under your sole control, on your own device, from the very first click.
Automated on-chain risk mitigation
Before any batch can be signed, every recipient address is screened server-side against OFAC and international sanctions lists. Addresses are never stored in the clear: each is transformed into an irreversible salted SHA-256 hash before it is processed or persisted. If a screened address matches a restriction list, the batch is blocked automatically on the backend — before your wallet is ever touched. There is no partial workaround: a flagged batch does not proceed.
This page explains how PurserPay is built; it is not legal, tax, or financial advice. For guidance on your specific situation, consult your own qualified advisor.