Change banks
Update your destination once. The people paying you change nothing.
OPAP demonstrator
The internet has URLs.
Now money does too.
OPAP makes you payable through a URL.
You choose where your money arrives—and can change bank, wallet or payment rail without changing where they pay.
This prevents any single provider from controlling how you receive money.
01 / What it is
A protocol above payment systems.
OPAP is an open protocol that connects a URL or OPID to the way someone wants to receive money. It works on top of banks, wallets and other payment systems. All of them. It decouples you from your bank.
Your address
pay@yourdomain.org
OPAP finds the payment method you chose.
Bank
Wallet
Other system
OPAP does not hold or move money. The selected payment system does.
02 / Why it is needed
Your payment address should belong to you.
Today, your account number or wallet address ties you to one provider. Change provider, and every person or organisation paying you needs new details.
OPAP separates your permanent address from the destination behind it. Everyone keeps paying the same address while you remain free to change how the money reaches you.
Choose freely
Use a bank, wallet or another payment system without changing your public address.
Avoid lock-in
A government, employer or platform can pay your address without choosing the system behind it.
03 / How it works
One address in. A verified destination out.
01
Enter an address
Use an OPID, domain or public URL.
02
OPAP looks it up
The browser reads the recipient's published preferences.
03
Review the result
See the recipient and available payment methods before continuing.
04
Pay normally
Your bank or wallet completes the payment. OPAP never handles it.
Live browser demonstrator
Follow an address all the way to the payment.
Resolve an address, inspect its destination and confirm the exact plan. Everything happens in this browser.
Discovery and verification
Resolve first. Payment controls remain unavailable until a valid terminal record exists.
Waiting for an OPID or URL.
Amount and method
Choose one supported route. On-chain identity is exact chain plus token contract.
Payment method
Wallet and readiness
Wallet connection is requested only for an on-chain method.
No wallet connected.
Final review
This is the immutable plan that will be compared again before submission.
Handoff or receipt
The result names exactly what the browser can prove.
Local history
Only OPID, chain, transaction hash, timestamp and outcome are kept. Full IBANs, records and signatures are never stored.
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.
- Production Gnosis execution is blocked in this release registry.
04 / Create your own
Publish your own OPID.
An OPID is a name on a domain you control, such as pay@yourdomain.org. Control the domain, and you control the payment address.
Create your OPID →The creator runs locally in your browser. It validates the record and gives you the exact file and publication location; nothing is uploaded for you.
-
01
Choose a name
Enter a label and a domain you control. The creator normalizes both into a canonical OPID.
-
02
Publish a record
Choose a SEPA account, ERC-20 wallet or another OPID as the payment destination.
-
03
Download the record
Copy or download protocol-valid JSON generated entirely in your browser.
-
04
Publish and test
Place it at the supplied HTTPS path, then enter the OPID above to verify what payers will see.
Technical publishing location
For this OPID:
pay@yourdomain.org
Publish the record at:
https://yourdomain.org/.well-known/open-payment/pay.json
The record lists your payment handlers. Publishers also enable public browser access; DNSSEC verification can add stronger trust.