The shared pool model
Every payment link you create points to the same shared pool address rather than a wallet you control directly. When your client pays, their transaction lands in that pool alongside payments from other businesses’ clients. Because all inflows go to one address, an outside observer watching the Stellar blockchain cannot determine who paid whom — the pool looks like a collection of unrelated inflows. Attribution happens through a unique memo attached to each transaction. When you generate a payment link, Hypertron assigns it a memo in the formathpl_[timestamp]_[random]. Your client’s wallet software includes this memo automatically when sending payment. Hypertron’s backend reads the memo on arrival, matches it to your workflow, and credits your virtual balance — without ever recording which wallet sent the funds.
The memo is what links a payment to your account and workflow stage. Hypertron never stores or logs the payer’s Stellar address.
What each party can and cannot see
Hypertron’s privacy model is designed to protect both your clients and your business from unnecessary exposure. The table below summarizes the visibility each actor has in the system.| Actor | Can see | Cannot see |
|---|---|---|
| Business (you) | Payment confirmed, amount, workflow stage | Payer wallet address, pool outflows |
| Client | Their own payment sent | Your balances, your withdrawals |
| On-chain observer | Pool inflow and outflow transactions | The mapping between them |
| Soroban contract | Commitments and nullifiers | Identities or balances |
You will see a “Paid” confirmation in your dashboard with the payment amount and the workflow stage it belongs to. You will not see the Stellar address of the wallet that sent the funds.
What you can see as a business
Your dashboard gives you accurate, real-time payment information:- Confirmed payments — Each payment that successfully lands in the pool and matches one of your memos appears as a confirmed event in your dashboard.
- Amount received — The exact XLM amount credited to your virtual balance.
- Workflow stage — Which payment link and onboarding stage the payment is associated with.
- Withdrawal history — Records of funds you have withdrawn, including status and payout transaction hashes.
What your clients can see
Your clients see only their side of the transaction:- The payment page at
/pay/[linkId], which shows the amount and purpose you configured. - A confirmation from their Freighter wallet after they sign and submit the transaction.
- Their own Stellar transaction history, which will show a payment to the pool address with the memo you assigned.
Why this matters
The shared pool model has practical benefits beyond privacy. Because client wallet addresses are never collected, you have no personal data to protect under financial privacy regulations — Hypertron does not create a record linking an identity to a balance. Commitments recorded on-chain prove that payments happened without revealing who made them. Withdrawals are routed through the Privacy Relay Layer so that outflows from the pool cannot be correlated with inflows, even by sophisticated blockchain graph analysis.Payment links
Learn how payment links work and how clients use them to pay you.
ZK commitments
Understand how cryptographic commitments prove payment without revealing identity.