Tether issues USD₮, commonly displayed as USDT, on multiple blockchain protocols. Its supported-protocols page identifies deployments and protocol-specific asset information.
For a business payment, the stablecoin name and the network belong together in the instructions.
Start with the exact asset
Agree the asset, network and destination with the recipient before transferring funds. A familiar ticker does not establish that the receiving service supports that token on every network, or that two different representations are interchangeable.
Use current instructions from the receiving service, and check the issuer’s official information when verifying an asset. Keep those details with the payment record.
Where Holyheld fits
Holyheld supports stablecoins alongside named USD and EUR accounts and global payments. The asset and network combinations available in your account determine the route for a particular payment.
For a stablecoin-to-fiat payment, the workflow includes conversion and delivery through the selected fiat route. For a fiat-to-stablecoin payment, confirm the destination network and asset before conversion and delivery.
Example: agree the settlement details first
A company invoices for work and agrees to receive a supported stablecoin. Before the customer sends, the two teams confirm the payment asset, network and reference. On receipt, the finance team matches the transfer to the invoice and retains the transaction hash. Any subsequent conversion or supplier payment gets its own record. This is an illustrative workflow.
The invoice currency also matters. If the invoice is denominated in a different currency from the asset being sent, agree how the settlement amount is determined.
Follow the payment through to receipt
Review Business pricing and the transaction’s conversion details, then reconcile the actual amounts and fees. Read Moving between stablecoins and bank payments for the complete process.