At a glance
| Decision | Practical answer |
|---|---|
| Start here | Match the reference currency and usable redemption/conversion route to your business. |
| Choose deliberately | Add another token only when customer demand justifies another supported asset/network combination. |
| Main tradeoff | A peg, reserve report and usable bank payout are different checks. |
Two tokens can both be called stablecoins while exposing a business to different currencies, redemption routes and technical dependencies. The question is not only whether the price is intended to stay stable. It is stable against what, through which mechanism, and usable where?
This is the asset-design branch of the merchant payment series. For a direct comparison of two dollar tokens, read USDT versus USDC.
Start with the currency your business needs
A dollar stablecoin does not stabilize revenue in euros. A merchant selling a EUR 200 service needs to decide whether the invoice remains EUR 200 until payment or becomes a fixed dollar-token amount when quoted. That agreement determines who bears exchange-rate changes before the customer pays.
Circle's EURC description identifies a euro-backed token with its own supported networks. It is an example of a different reference currency, not a claim that PayIn accepts EURC or that all EURC holders have identical conversion access.
Compare mechanisms, not only names
| Design or asset form | Merchant question | What the label alone cannot prove |
|---|---|---|
| Fiat reserve-backed token, such as USDC or USDT | Who issues it, what backs it, and how can this business redeem or exchange it? | Guaranteed market price, bank insurance or universal redemption access |
| Protocol-based stablecoin, such as USDS or DAI | Which collateral, governance and smart contracts support the design? | Absence of issuer-like dependencies or automatic checkout support |
| Bridged representation | What original asset, bridge and redemption path does it depend on? | Identity with native issuance on that destination chain |
| Savings or yield-bearing wrapper | Is this still the exact asset the invoice and payment system request? | Identical units, withdrawal timing or risk to the underlying payment token |
Sky's protocol documentation distinguishes USDS, DAI and savings-related contracts. A merchant should not assume that similar naming makes these balances interchangeable at checkout. This article does not rank their investment merits or recommend a yield product for operating cash.
Read reserve information with the right question
An issuer's reserve statement addresses backing at a specified time and under a stated methodology. It does not establish every aspect of your wallet security, merchant eligibility or the availability of an exchange deposit route.
For each candidate, record the issuer or protocol, report date, asset backing, applicable redemption terms and network. Keep the source beside your notes so a later operational review can distinguish a current statement from an old screenshot. Circle's USDC terms and Tether's transparency material are starting points, not substitutes for checking your business's actual service arrangement.
Add a token only if the sale benefits
A merchant accepting a second stablecoin also adds another asset/network combination to customer instructions, support and reconciliation. A USDT payment to a USDC-only request is not automatically an acceptable substitute merely because both target a dollar value.
Before adding an asset, ask:
- Do customers already hold it on the network you can accept?
- Does the exact checkout product and wallet support it?
- Can you identify its official contract or mint?
- Can your receiving and conversion routes handle it?
- How will you record and refund a sale made in that asset?
A business might answer yes for a particular USDT route and no for a less familiar stablecoin. Another business might prefer a local-currency token. Neither decision follows from the word stablecoin alone.
Avoid treating a peg as the entire safety model
A stablecoin can trade away from its intended reference price. Access can also fail while the market price looks stable: an exchange can reject a deposit route, a wallet can be compromised, or a contract can restrict a transfer. Distinguish price, redemption, custody and technical risks rather than collapsing them into one score.
Read payment security and native versus bridged USDC for concrete checks. Then use the fee worksheet to include conversion and withdrawal in your comparison.
PayIn currently receives supported USDC on Base, Polygon and Solana. This broader asset taxonomy describes merchant choices; it does not expand PayIn's accepted assets.