Private payments need a whole-journey view
Compare payment privacy models across the whole journey. Monero is educational here and is not accepted by OmbraHost.
Content revised · English
- Series
- The Ombra Journal
- Perspective
- Practical decisions, explicit boundaries
- Language
- English
Keep these in view.
- Follow account, device and ledger records together.
- Monero is discussed for education; OmbraHost does not accept it.
- Use only the supported asset/network route in checkout.
Follow the information, not just the coin
An account alias, browser session, domain record, wallet source and support conversation can all identify a project. Payment privacy belongs in a complete threat model. Decide what you need to protect and from whom before choosing a protocol.
Bitcoin has a public transaction history
An on-chain BTC transfer exposes ledger activity even when the hosting account uses a pseudonym. A wallet address and an identity-verified purchase can be linked through records or analysis. Avoid describing BTC as automatically anonymous.
Monero changes the protocol layer
Monero is designed to conceal transaction amounts and linkages on the public chain. That is a meaningful protocol difference, but it does not secure a compromised endpoint or erase an exchange’s customer record. Keep keys private and verify the receiving instructions. OmbraHost does not accept XMR; this protocol comparison is educational.
An invoice makes the transfer specific
OmbraHost’s authenticated checkout displays an exact cryptocurrency amount, selected network, fixed receiving address and server quote expiry. BTC has a two-confirmation backend rule, with an indicative wait around 20 minutes. No blockchain monitor supplies automatic updates. Monero is not accepted and has no OmbraHost invoice or confirmation flow; USDC is Ethereum-only.
Keep the refund value rule visible
The proposed refund uses the original asset and converts the initial USD payment value at the current refund rate, so the resulting coin quantity can differ. Fixed-address checkout is implemented, but a trusted server integration must verify transactions before any refund reconciliation or fulfilment. The commercial refund rules remain a launch draft.