Accepting Ethereum Payments as a Merchant

Why does Ethereum matter to merchants?

Less for ETH itself than for what runs on it. Ethereum is where most stablecoin value was issued and where institutional balances sit, so a provider without Ethereum support is missing the network a large share of business counterparties actually use.

Accepting ETH as an asset is a smaller case. A business selling goods for a fixed price rarely wants a volatile asset on its balance sheet, which is why most merchant volume on this network is stablecoin volume.

What does the transfer cost do?

It decides the ticket size at which this works. The gas fee on Ethereum is paid per transaction and varies with congestion, so the same payment can cost cents at a quiet hour and several dollars at a busy one.

On a large invoice that is irrelevant. On a small one it is the difference between a completed sale and an abandoned checkout, and the customer sees the fee before they see your product.

What changed with layer two?

Layer two networks carry the same assets at a fraction of the transfer cost while settling back to Ethereum. Base, Arbitrum and Polygon are the ones payment providers support most often, and Coinbase Commerce settles on Base specifically.

For a merchant this is simply a cheaper version of the same thing, and it removes the main objection to Ethereum for retail sized payments. The catch is support: a customer holding funds on the base network cannot pay you on a layer two without bridging first, so offering both matters more than picking the better one.

What should you check with a provider?

Which Ethereum networks are live, named individually. Whether the provider accepts ETH, stablecoins on Ethereum, or both, since these are separate switches at several providers.

What happens when a customer sends on a network you do not support. This is the most expensive routine mistake in the category and the network guide covers how to handle it before it reaches a support ticket.

What the merchant actually decides here

Which networks to display at checkout, and that is a smaller question than it sounds only until a customer gets it wrong. Offering the base network alone prices out small payments. Offering four layer twos multiplies the ways a customer can send to a chain you are not watching.

Two is usually right: the base network for counterparties who hold there and expect it, plus one cheap network your market actually uses. Adding a third because a provider supports it adds a failure mode without adding volume.

The ERC-20 detail worth knowing

Tokens on Ethereum are not the native asset, and moving them requires the native asset to pay the fee. A customer holding stablecoins but no ETH cannot send them, and this surprises people regularly.

It matters to you because it is a silent conversion killer. The customer sees a payment request, opens a wallet holding enough of the token, and cannot complete the transaction. Nothing in your checkout reports this, and the abandoned payment looks identical to any other. Networks where the fee is negligible make the problem correspondingly rare, which is a further argument for offering one.

Where to go next

The catalogue records the networks each provider publishes, which is the field to check before assuming layer two support. The fees guide covers how conversion spread interacts with the network choice, since a cheap network with an expensive spread is not the saving it appears to be.