Receive globally through one OPID
https://openpaymentaddress.org/examples/multi-currency publishes EUR,
GBP, USD, ISK and Bitcoin options for bank transfers, Monerium test
wallets and a Bitcoin wallet.
Reference records
OPID examples
Seven working examples show how one payment identity can span currencies, rails, providers, purposes and split recipients. Every page includes its exact public record and a link to resolve it in the Browser Payer.
Example index
Compare the routing shapes
Start with receiver choice, then compare purpose-specific addressing, delegation and an atomic split. The examples stay inside OPAP/1: mixed currencies can be alternatives, while each atomic split settles in one asset on one rail.
Let the payer choose bank or wallet
https://openpaymentaddress.org/examples/multi-rail accepts EUR through
either a bank transfer or a digital-euro test payment through
Monerium’s sandbox, without changing the receiver’s public
identity.
Keep the address, replace the setup
https://openpaymentaddress.org/examples/portable-business delegates to
the current multi-rail receiver. Both records remain visible and
verifiable during resolution.
Offer bank and wallet options
https://openpaymentaddress.org/ publishes more than one payment method
behind a single address. The payer can select a supported route without
the recipient publishing separate identities.
Give one page its own OPID
https://openpaymentaddress.org/music has its own direct payment record,
demonstrating how one path can identify a distinct purpose without
creating a new hostname or inheriting the root receiver’s methods.
Route one payment to four shares
https://openpaymentaddress.org/collaboration resolves to a fixed
on-chain execution plan with four equal recipients, keeping the split
visible to the payer before execution.
Point one OPID to another OPID
https://openpaymentaddress.org/protocol delegates to
https://openpaymentaddress.org/. The payer follows and verifies both
published records before showing the terminal payment methods.