Ethereum payment support is a combination of chain access, supported assets, receiving wallets and verification rules. A merchant should treat Ethereum mainnet as a specific payment route rather than a generic label for everything with a hexadecimal address.
Understand the supported asset menu
Coinvay’s current Ethereum configuration includes native ETH plus configured USDC, USDT, DAI and PYUSD contracts. The merchant can choose which supported options to offer. That list does not include arbitrary ERC-20 tokens, wrapped assets or every token a customer’s wallet can display.
For a supplier collecting several invoice types, keep the network constant where that simplifies support, but let the asset choice reflect actual customer balances. A quote for DAI cannot be paid with USDC simply because both use the Ethereum network.
Separate transaction cost from order value
Token senders generally need ETH for Ethereum gas. Native ETH senders need both the payment amount and a fee reserve. During periods of high fees, customers may abandon small-value orders or choose a different enabled route. Display current wallet estimates instead of promising a permanent gas cost.
The gateway should verify chain identity as well as receipt data. Ethereum mainnet uses chain ID 1; an RPC endpoint connected to a different EVM network must not be treated as equivalent. Provider health affects the checkout’s ability to observe payments, not whether a customer intended to pay.
Keep confirmation and fulfillment reliable
Coinvay’s current Ethereum policy requires twelve confirmations and checks the canonical receipt, successful result, amount, recipient and time window. This product threshold should not be advertised as Ethereum protocol finality or as a fixed clock duration.
Suppose a customer’s wallet shows a successful transaction while the invoice remains pending. Check the exact asset and destination first, then the confirmation state and provider response. Do not bypass the invoice verifier just because a block explorer displays a familiar address.
Practical checklist
- Keep Ethereum mainnet distinct from Base and other EVM chains.
- Explain ETH gas requirements for token buyers.
- Monitor provider availability without weakening receipt checks.
Common questions
Does EVM compatibility make payment networks interchangeable?+
No. Compatible transaction formats do not merge their ledgers, contracts or balances. A transfer must occur on the network specified by the invoice quote.
Can the gateway guarantee a transaction will be included quickly?+
No. Sending wallets, fee choices, network conditions and provider availability can affect the journey. Give customers a waiting state and a transaction-hash support path rather than a guaranteed completion time.
Sources and further reading
Primary references and Coinvay product documentation. Check the linked pages for current details.
AI-assisted drafting, published by Coinvay. Examples are illustrative. Read our editorial approach.