Do not translate a receiving name into a different account by guesswork
NEAR’s account-ID documentation describes named accounts, implicit accounts and other supported address forms. The familiar named and ED25519 implicit forms are different ways accounts can be identified, not permission to replace the receiver’s supplied ID with an unrelated value. A name that looks readable still needs to be the actual account intended for this payment.
The integration guide describes an ED25519 implicit ID as the lowercase hexadecimal encoding of a public key’s bytes. A wallet can derive it locally before on-chain creation. This is different from pasting an encoded public-key field or choosing a saved human-readable account name. Do not assemble the recipient manually from whichever identity detail is visible.
Which record should supply the payout recipient?
| Record | What to establish | Unsafe assumption |
|---|---|---|
| Named NEAR account ID | The exact registered account intended by the receiver | Any similar readable name reaches the same owner |
| ED25519 implicit ID | The actual receiving ID and supported first-funding context | A locally displayed ID proves every receiving step is ready |
| Wallet account label | Which real account ID this label represents | Renaming a local label changes the on-chain recipient |
| Access-key details | Their permission and identity role | An encoded key field is a copy-ready deposit instruction |
| Another address form | The receiver’s explicit supported instruction | A familiar prefix determines the network or account relationship |
Get one confirmed instruction before paying USDT
- Choose the receiving account in its wallet
A wallet can manage several accounts, and its sign-in identity may not be the account selected for this purchase. Open the receive view of the intended one. If a platform manages it, obtain that platform’s current NEAR deposit details instead of copying a general profile name.
- Keep the complete account ID
Do not remove suffixes, shorten a long identifier or replace it with a name that seems easier to read. If the offered payout does not accept the original instruction, clarify supported formats with the receiver and service before sending the input. Acceptance of a different string does not prove it identifies the same account.
- Clarify a new implicit account’s state
The NEAR integration guide separates local derivation from on-chain account creation. If this is a new recipient, determine what first-funding process is supported. Do not turn a developer example or a remembered creation cost into a guaranteed exchange feature or a permanent minimum purchase amount.
Read the account that was actually selected
- Compare the payout recipient with the saved instruction
- Use the actual NEAR receiving event and the exact account ID, not only a friendly label in an application. If another account is open, its balance may answer a different question even when both are controlled through the same wallet interface.
- Keep the two network events separate
- The USDT payment funds the exchange; the NEAR payout has its own destination and transaction record. Retain the exchange reference so support can connect the two when a status is unclear. Do not use an unrelated transfer under a similar account name as proof of this payout.
- Explain a mismatch without changing identity settings
- State which account was intended, which ID was submitted and which balance was checked. Do not edit access keys or sign an account-creation operation merely to make a guessed identifier work. Resolve the actual receiving instruction through the appropriate support process.
Questions about the NEAR receiving identifier
- Can I replace a long implicit ID with a name that looks like mine?
- Do not assume the two identify the same account. Obtain the exact intended receiving instruction and clarify any supported alternative before funding.
- Does a local wallet label establish the on-chain recipient?
- Use the actual account ID behind the label. A friendly description is not enough to compare the submitted destination with the intended account.
- Does a locally derived implicit ID prove on-chain creation is complete?
- Derivation and creation are separate observations. Check the recipient state and supported first-funding process instead of inferring readiness from the displayed ID.
NEAR account documentation
Reviewed: