ERC-7856 Per-chain payment request URI standard (Chain-Specific Payment Requests)

Draft · Tokens · created 2025-01-01

A standard that clearly specifies in a single URI which chain, which token, and how much should be sent, eliminating confusion in payment requests in a multi-chain environment.

Why it is needed

As Ethereum has scaled out to mainnet and multiple layer 2s, it has become common for the same token to exist simultaneously on several chains. However, there was previously no standard way to specify in a payment request which chain the payment should be processed on. As a result, users or wallets could mistakenly guess the wrong chain and send funds to the wrong network, or send an asset different from the one the requester intended. This ambiguity poses a risk of direct fund loss, especially in peer-to-peer payments or situations where a merchant or app requests payment. Without a standard to pin down the chain, token, and amount clearly within a single URI, this kind of confusion is bound to become more frequent as the multi-chain environment grows.

In depth

URI format structure

The basic format is cspr://<recipient>/<amount>/<token-address>?on-success=<success-callback-url>&on-error=<error-callback-url>. The cspr:// prefix, recipient, amount, and token-address are all REQUIRED, while the on-success and on-error callback URLs are OPTIONAL.

Recipient as a CAIP-10 account identifier

recipient is expressed as a CAIP-10 account identifier. For example, eip155:8453:0x1111111111111111111111111111111111111111 includes the chain together with the address, allowing the recipient's network and address to be specified simultaneously even across chains with different address notation rules.

Token address and native currency

token-address is a base64-encoded string of the ERC-20 token contract address. If the chain in question supports a native currency, the special value native can be used to request that chain's base currency. Base64 is used because every address notation scheme that currently exists is a subset of base64, allowing both EVM and non-EVM chains to be supported.

Amount notation

amount is expressed as an integer or a decimal. This is designed so that users can clearly verify the amount before sending, with the aim of preventing mistakes or fraud.

Callback URLs

on-success is the URL to redirect the user to after the transaction is confirmed, and on-error is the URL to redirect to after the transaction fails. Both are optional and serve to send the user back to the app or website.

Error handling

A wallet or app parsing the URI MUST validate the format of the recipient account. If any component of the URI does not match the required format, an error MUST be displayed to the user.

Differences from ERC-681 and ERC-831

ERC-681 includes additional transaction detail parameters such as gas limit, but this standard narrows its scope to focus on simplicity and clarity, leaving such details to be handled by the wallet. ERC-831 is limited to Ethereum and its rollups, but this standard is designed to cover non-EVM chains as well, as shown by the Bitcoin example. Because the URI prefixes differ, it is not backward compatible with either standard.

A proposal still under review

This EIP is currently in Draft status, has not yet been finalized, and its details may change or discussion may stall going forward.

Things to watch out for

Original ERC · ← ERCs