Ethereum payment URIs and chain-qualified addresses
A payment URI can carry an address together with network and operation parameters. The entire URI is not the same thing as the recipient’s bare address.
Worked example
| Illustrative fragment | Role | Check |
|---|---|---|
| ethereum: | URI scheme | Application supports the scheme |
| target@chain_id | Target and optional chain context | Resolve target and chain explicitly |
| /function?parameters | Optional operation and arguments | Understand the requested call |
Worked parsing distinction
In an ERC-20 transfer request, the target can be the token contract while a separate address argument identifies the recipient. Copying just the target into a receive field would select the wrong role. EIP-681 defines structured requests; applications must interpret them correctly.
Network qualification is separate
EIP-3770 proposes short chain prefixes for EVM address display. That notation is different from an EIP-681 request. Check the receiving application’s supported input format instead of assuming any address field accepts either notation.
Common pitfalls
- These fragments are placeholders, not executable requests.
- A URI can request more than a simple payment. Read the full preview.
Related references
Primary sources
Examples explain identifiers. They are not investment recommendations.