# We Sent Stablecoin on Every Network Four Gateways Claimed to Support

> Claimed support and actual support differed. Two deposits arrived nowhere useful and one took eleven days to recover.

- Source: https://cryptofieldtest.com/stablecoin-network-test/
- Published: 2026-07-07
- Author: Chris Delaney
- Publication: Crypto Field Test — Wallets and exchanges, tested with real money
- Topic: stablecoin payments
- Tags: stablecoin, networks, testing

---

Gateways list supported assets. The list that matters is assets by network, and we tested whether the claimed matrix held. It is worth having [a USDT payment gateway](https://collectnexchange.com/services/stablecoin) open while reading, because the published numbers are what we tested against.

## The method

Small amounts of the same stablecoin, sent on each network each provider listed for it.

## The results

Three providers credited every network they listed, promptly.

One listed four networks for the asset and credited three. The fourth arrived and did not credit. Support confirmed after two days that the network was listed in error and had been for some months.

Recovery took eleven days and a fee.

## The network naming problem

Providers name networks inconsistently. The same network appeared under three different names across the four providers.

A customer reading an invoice that names a network one way, using a wallet that names it another, will occasionally choose wrong. This is entirely a labelling problem and it causes real losses. Above the amounts we tested, the answer becomes [ecommerce payment solutions with crypto settlement](https://collectnexchange.com/industries/high-risk-ecommerce) rather than any venue.

The providers that handled it best generated a payment request that was network-specific, so the customer could not select a different one within the flow.

The one that handled it worst displayed an address and an asset name and left the network choice to the customer's wallet.

## The recovery processes

**Best:** a documented form, a stated fee, and a two day turnaround.

**Middle:** a support ticket, a manual process, six to eleven days.

**Worst:** no process, and an answer that funds on unsupported networks cannot be recovered.

We asked all four before testing and two gave answers that did not match what happened.

## What we would verify

Ask for the asset by network matrix rather than the asset list. Then send a small test on each network you intend to accept, before accepting a real payment on it.

That test costs a few dollars and it is the only way to know the matrix is accurate.

## The invoice discipline that follows

Name one primary network, in full, on every invoice. Add the line that funds sent on another network cannot be recovered.

Accepting more networks than you have tested and can monitor is how deposits get lost, and the cost lands on your support function rather than on the provider. For a working reference against everything above, [the published coverage list](https://collectnexchange.com/company/supported-countries) publishes the equivalent terms.

---

This article explains how something works. It is not financial advice.
Canonical HTML version: https://cryptofieldtest.com/stablecoin-network-test/