What is a hosted wallet transaction?¶

A hosted wallet transaction is activity carried out through a wallet account where a provider holds and manages the cryptocurrency on the customer’s behalf.

Avoid the dangerous assumption¶

The dangerous assumption is that every hosted-wallet transfer appears as a separate transaction on the public blockchain.

The provider controls the private keys and may record customer balances on an internal ledger. It may combine customer assets within pooled operational wallets.

Transfers between customers of the same service may therefore occur entirely within the provider’s systems.

Deposits from an external wallet and withdrawals to an external address normally create blockchain transactions.

Internal trades, conversions and transfers may not.

Relevant provider records may include customer account IDs, sender and recipient accounts, asset, amount, fee, status, timestamps, devices, sessions and authentication events.

Blockchain records may show only the provider’s pooled wallet movement rather than the individual customer transaction.

Preserve the hosted-wallet provider, account identifier, internal transaction reference, deposit or withdrawal address, transaction hash, asset, network and timestamps.

Ask the provider to distinguish internal ledger activity from on-chain movement and explain which identifiers link the two.

Do not assume that a provider-controlled blockchain address belongs to one customer.

Likewise, an internal recipient name does not prove the person who operated the receiving account.

Compare provider transaction records with account access, devices, communications and any later withdrawal.

When reporting, distinguish the customer instruction, provider ledger entry, provider custody and any external blockchain transaction.

Operational takeaway¶

Treat hosted-wallet transactions as provider-recorded account activity and obtain internal ledger and access records alongside any related blockchain deposits or withdrawals.