Secure payment flow
Complete this payment, step by step.
Start by confirming the selected web address. This browser then resolves, verifies and reviews every stage before payment can continue.
Confirm the payment address
This is the exact public URL selected on the homepage.
Selected URL
Preparing address…
Resolution and verification run locally in this browser. No payment controls are enabled yet.
Discovery and verification
Resolve first. Payment controls remain unavailable until a valid terminal record exists.
Preparing the selected payment address for secure resolution.
Payment details
Choose how much the recipient receives, then select one of their accepted settlement currencies and methods.
This is the exact amount and currency the recipient should receive.
Wallet and readiness
Wallet connection is requested only for an on-chain method.
No wallet connected.
Final review
Check the recipient and amount before continuing with the selected payment method.
Handoff or receipt
The result names exactly what the browser can prove.
Local histories
Opt-in payment history stores only OPID, chain, transaction hash, timestamp and outcome. Separate OPID and page-association verification histories remember downgrade protection. Full IBANs, records, descriptions and signatures are never stored. Clearing removes all three histories, including downgrade-protection memory.
Security and privacy boundaries
- Publishers must support credential-free CORS; there is no proxy fallback.
- DNSSEC hash conflicts, changed plans and contract mismatches block execution.
- Monerium onboarding and APIs remain outside this application.
- All four Gnosis production assets are blocked in this release registry.