Ethereum is the only network that accepts all five payment assets

Paymos lets a business accept USDT, USDC, USD1, DAI, and XAUT payments on Ethereum. Each invoice receives a dedicated address, and the confirmed payment is credited in the same accepted asset without forced conversion.

Accept supported payment assets on Ethereum

Ethereum is the only Paymos network that supports all five settlement assets:

• USDT
• USDC
• USD1
• DAI
• XAUT

USDT, USDC, USD1 and DAI are stablecoins. XAUT is a separate gold-backed real-world asset and must not be described as a stablecoin. Native ETH is not an invoice payment asset.

The merchant enables Ethereum and the required assets for a project. Paymos assigns a dedicated deterministic address to each invoice, monitors Ethereum, applies the relevant confirmation policy and updates the payment status.

This page owns the product question: how Paymos accepts payments on Ethereum. For asset selection, use the tokens hub. For USDT route choice, read TRC20 vs ERC20 vs BEP20 and Tron vs Ethereum fees.

What must match on an Ethereum invoice?

The token and Ethereum network must both match the route displayed at checkout. USDT on Ethereum is not interchangeable with USDT on Tron, BSC, TON or another network. The same rule applies to every multi-network asset.

The payer should select the Ethereum withdrawal route in the wallet or exchange and use the address assigned to the invoice. ETH is not accepted as the payment asset, but the payer's wallet may require ETH to cover the Ethereum network fee for sending an ERC20 token.

How do Ethereum confirmations work in Paymos?

Paymos uses an amount-aware confirmation policy. The required finality threshold depends on both Ethereum and the payment amount: smaller payments can require fewer confirmations, while larger payments can require a stronger threshold.

Current blockchain conditions affect observed timing, so Paymos does not promise one fixed confirmation time for every Ethereum payment. A transfer can be detected before it reaches the finality threshold required for settlement. Payment status updates as the transaction moves through detection, confirmation and settlement.

Who pays Ethereum gas?

The payer's wallet pays the network fee required to send the selected token on Ethereum. Paymos does not publish one permanent gas amount because blockchain costs vary. The wallet or exchange used by the payer determines the fee required for that transaction.

Paymos covers the network cost of accepting and consolidating the payment. The standard processing fee is 1.0% per settled invoice; Enterprise pricing is 0.3% on request. There is no setup fee, monthly platform fee, monthly minimum, reserve or rolling reserve. An unpaid, expired or cancelled invoice has no Paymos processing fee. See pricing.

Settlement stays in the accepted asset

A payment received on Ethereum contributes to the merchant balance for that asset. Payments in the same asset from other supported networks contribute to the same asset balance rather than creating a separate Ethereum-only balance.

USDT remains USDT, USDC remains USDC, USD1 remains USD1, DAI remains DAI and XAUT remains XAUT. Paymos does not force conversion to fiat, BTC, ETH or another intermediary asset and does not add a hidden markup to the rate.

When creating a withdrawal, the merchant chooses an available payout network for the asset. Withdrawal goes to a merchant-controlled address from the whitelist; availability, minimum and network fee are shown for the selected route, and that fee sits below what Ethereum charges to move the token.

Ethereum integration options

Ethereum assets can be enabled through the standard Paymos surfaces:

• Hosted Checkout for a Paymos-hosted payment page.
• Embedded Checkout for an iframe inside a website.
• Payment Links for sending invoices without custom checkout code.
• Low-Code SDK for a browser integration.
• POS Terminal for browser-based in-person collection.
• Host-to-Host REST API for a server-controlled payment flow.
• Official CMS plugins for supported commerce platforms.

Sandbox and Production use separate credentials with the same API surface. Merchant API requests use HMAC-SHA256 authentication. Follow the quick-start guide, then enable Ethereum and only the assets needed by the project.

Payment status and security

Merchants receive status changes through the API and authenticated webhooks. Webhook requests use timestamped HMAC-SHA256 authentication in the X-Webhook-Signature header. Failed events can be replayed manually, and up to ten webhook endpoints can be configured per merchant environment. Read webhook verification before trusting an event.

Outgoing Paymos transactions are signed on isolated infrastructure. Withdrawals can go only to destination addresses that were added to the merchant's whitelist.

Frequently asked questions

Which assets does Paymos accept on Ethereum?

Paymos accepts USDT, USDC, USD1, DAI and XAUT on Ethereum.

Can a customer pay an Ethereum invoice with ETH?

No. ETH is not an invoice payment asset in Paymos. The payer's wallet can still require ETH to cover the network fee for sending an ERC20 token.

Can a customer send TRC20 or BEP20 USDT to an Ethereum invoice?

No. The payer must send the token on Ethereum using the route displayed at checkout. A token on another network is a different payment route.

How many confirmations does an Ethereum payment require?

There is no single count for every invoice. The policy depends on the network and payment amount, with stronger finality thresholds available for larger payments.

Does Paymos split a token balance by network?

No. Payments received in the same asset across different supported networks contribute to one merchant balance for that asset.

Who pays Ethereum gas?

The payer's wallet pays the fee required to send the token. Paymos covers the network cost of accepting and consolidating the payment.