Which account detail are you looking at?
| Displayed detail | Its role in the check | Do not assume |
|---|---|---|
| Numbered Hedera account ID | Identifies an account using shard, realm and account number | An example number in a guide belongs to you |
| EVM-style address or alias | A different account representation to clarify with the recipient | A 0x shape makes this an Ethereum-network payment |
| Public key | Key information in account details | Every hex-looking key is a receiving address |
| Wallet account label | A local description for a user | The same label identifies the same recipient in another application |
Network support and identifier support are different questions
Hedera’s account-properties reference documents account IDs in shard.realm.account form. Its auto-account-creation documentation also describes EVM-address aliases and explicitly distinguishes an EVM address from the ECDSA public key used to derive it. A copied public-key field is therefore not a substitute for a verified receiving instruction.
The same documentation describes particular transfer flows that can create an account through an alias. This does not establish that every exchange payout implements every alias representation or creation path. Check the format actually offered for the intended payment; do not turn a protocol capability into a promise about a particular form.
Obtain a complete receiving instruction without manual conversion
- Start in the intended Hedera account
Open its receive or deposit screen, not a general page of keys and account metadata. If a hosted platform manages the account, use that platform’s current HBAR deposit instruction, including any additional field it requests. Keep the entire instruction associated with that account.
- Describe the original format if it is rejected
Ask whether the proposed payout accepts the recipient format you were actually given. Do not add a shard-and-realm prefix to a string by guesswork, strip an alias, or replace it with a number found in an old transaction. An accepted substitute must come from a verified receiving process.
- Confirm the network independently of the string shape
A Hedera workflow may display an EVM-style address. That shape alone does not authorize sending on Ethereum or another EVM chain. Compare the selected HBAR network and the recipient’s account instructions before paying USDT for the exchange.
Record the receiver you meant to fund
For a useful record, keep the original receiving instruction, the account or platform it belongs to, and the exchange reference together. If the same wallet shows several identifiers, note which one was submitted. This is more useful during a crediting investigation than a screenshot of a general account page with no indication of the chosen field.
After a payout, inspect the relevant Hedera transfer and the recipient’s account history. Keep those observations separate from the USDT funding transaction. If the receiving state or account creation remains unclear, ask about that specific event rather than creating a second payment to test a guessed format. Do not disclose recovery phrases or private keys when explaining which public receiving details were used.
Questions about the HBAR recipient format
- Can I use a public key as the HBAR payout address?
- Do not substitute a key field for the receiver’s instruction. Obtain the supported receiving format from the intended wallet or hosted platform.
- Does a 0x address mean I should choose Ethereum?
- Not by itself. Hedera also has EVM-style account representations. Establish the receiving network from the actual HBAR instructions.
- Does a protocol auto-creation feature guarantee an exchange accepts any alias?
- No. Check the offered route’s supported receiving process rather than assuming every protocol capability is implemented in that interface.
Hedera account documentation
Reviewed: