# What is a wallet address? How to check it before sending crypto

Published 17 November 2026 · Cessor

A wallet address identifies a destination on a blockchain. You give a sender the receiving address so they can direct a transfer to it. For example, an Ethereum account has a public address, while its private key controls the ability to sign transactions. The address and the signing key serve different purposes. [Read the official account documentation](https://ethereum.org/en/developers/docs/accounts/).

The practical question is whether the receiving details match the transfer you intend to make. Before sending, check the asset, network and instructions shown by the receiving service together. Copying an address alone leaves those questions unanswered.

## What does a wallet address tell you?

An address is a destination identifier. It does not tell you who controls the signing keys or whether a particular service will credit a deposit. Those are separate checks. Ethereum documentation distinguishes externally owned accounts, controlled by keys, from contract accounts, controlled by code. A wallet is the interface used to interact with an account. [See the account types and wallet distinction](https://ethereum.org/en/developers/docs/accounts/).

A useful way to organise the details is to keep three fields together.

| Detail | What to check |
| --- | --- |
| Asset | The exact asset you intend to send |
| Network | The network selected by both sender and recipient |
| Receiving instructions | The address and any additional information the recipient requires |

Complete this checklist from the receiving service’s current instructions.

## How do you find the right receiving details?

Open the receiving service through its usual trusted route and find its receive or deposit instructions for the intended asset. Read those instructions before copying the address. If the sending screen and receiving instructions describe different networks, stop and resolve the difference with the recipient.

Avoid treating a saved address as a permanent instruction for every future deposit. Reopen the current receiving instructions when preparing a transfer, particularly after a service changes its deposit flow. Rechecking keeps the transfer tied to the instructions for this deposit.

You can share the receiving destination when arranging a transfer. Keep the signing key and recovery material private. The official documentation explains that a private key is needed to sign and control an externally owned account. [Review the private-key explanation](https://ethereum.org/en/developers/docs/accounts/).

For the separate question of who controls the keys, read the [non-custodial wallet guide](https://www.cessor.com/resources/non-custodial-crypto-wallet).

## What should you check before sending?

Consider this invented example. A finance colleague asks you to send an asset to a receiving account. The message includes an address, but it leaves the network blank. The sending application offers more than one network.

The address is only one completed field. Ask the colleague to reopen the receiving instructions and confirm the exact asset and supported network through a trusted channel. Then compare those details with the sending screen. If any part remains unclear, leave the transfer unsubmitted and ask the receiving service for clarification.

The example shows why an incomplete payment instruction needs to be resolved before submission.

Before submitting, record the recipient's instructions, the selected asset and network, and the destination you checked. If the application presents additional recipient fields, resolve them using the receiving service's instructions. Do not guess a value to get past a form.

## What does a wallet address look like?

An Ethereum address is written as `0x` followed by 40 hexadecimal characters. Here is a shortened format illustration, `0x12ab…90ef`. The ellipsis stands for omitted characters, so this illustration cannot be used as a receiving address. [Ethereum address format](https://ethereum.org/en/developers/docs/accounts/).

Bitcoin mainnet addresses can begin with `1` for a legacy public-key-hash address, `3` for a script-hash address or `bc1` for a SegWit address. These are format prefixes rather than usable destinations. [Bitcoin transaction address types](https://developer.bitcoin.org/devguide/transactions.html) · [SegWit address specification](https://github.com/bitcoin/bips/blob/master/bip-0173.mediawiki).

When checking a real destination, use its complete address. A familiar prefix or a matching ending is insufficient evidence that you have the intended recipient. The network and the receiving service's instructions still need to match.

## When do you need a memo or destination tag?

Some receiving services use an extra identifier to credit the right customer. On the XRP Ledger, destination tags let a service distinguish payments to different customers using the same receiving address. The destination tag and the address therefore answer different questions. [Official destination-tag documentation](https://xrpl.org/docs/concepts/transactions/source-and-destination-tags).

If the recipient supplies a memo, tag or similar reference, confirm that your sending application includes it in the field the recipient requires. If the instructions require a value and your sending form has no corresponding field, ask for support before sending. Do not assume a number typed into a free-text message will be transmitted as the required identifier.

## How do you spot a swapped or look-alike address?

Address poisoning can place a look-alike destination in transaction history, hoping a user copies it into a later payment. The FBI describes this method in its token-impersonation warning. [FBI warning about address poisoning](https://www.fbi.gov/contact-us/field-offices/denver/news/fbi-warns-of-cryptocurrency-token-impersonation-scam).

Retrieve the destination through the recipient's trusted current instructions. After pasting it, compare the complete value against that source. If your signing device displays a destination, compare that value too. An unexpected change between the receiving instructions, sending form and confirmation screen is a reason to stop. Avoid copying a destination solely from a previous transaction or from an unsolicited message.

## Should you send a small test amount first?

For a new destination, consider a small test transfer before a larger payment. First ask the recipient whether that amount meets its minimum deposit and fee requirements. Confirm that the intended account receives the test, then recheck the complete destination and network before any further transfer.

Treat this as an additional operational precaution. A successful test confirms that particular transfer reached its destination; it does not establish that an unfamiliar recipient or investment offer is trustworthy. The FTC records scams in which small withdrawals helped persuade victims to commit more money. [FTC account of cryptocurrency investment scams](https://www.ftc.gov/news-events/data-visualizations/data-spotlight/2022/06/reports-show-scammers-cashing-crypto-craze).

## What records should you keep?

After submitting, retain the transaction reference supplied by the sender and any recipient-side deposit reference. A useful support request states the asset, network, transaction reference and time, and describes the problem without including private keys or recovery material.

Keep confirmation of submission separate from confirmation that the receiving service has credited the intended account. Ask the service which status or record establishes that credit for its particular flow. The wider [payment process guide](https://www.cessor.com/resources/payment-process) explains why individual events and final account records need to be matched.

## Discussing a receiving flow with Cessor

If you are evaluating Cessor, bring one intended deposit and withdrawal journey to the discussion. Ask which assets and networks are currently supported, which receiving details your integration must show, and what references your support team can use to investigate a transfer. Confirm the proposed flow against the current agreement before implementing it.

[Talk to Cessor](https://www.cessor.com/contact) with the payment journey you want to offer, or read the [crypto payment processing guide](https://www.cessor.com/resources/crypto-payments-for-platforms).

*General information only, not legal, financial or other professional advice. Information and service availability may change. Confirm current features and supported assets with Cessor before relying on this guide. Your applicable service agreement governs the services provided.*
