Optional cookies require your permission.Privacy & cookies

Who controls a payment between your wallet and its final recipient?

A wallet can confirm that the payer sent the funds. A different document may establish whether the government or commercial recipient credited the intended obligation.

Adam Juchniewicz, CEO, Bitcoin Lawyer9 min read
Sources cited in this essay (3)
A money-transfer office displays Western Union signs and exchange rates beside its open door.
In this essay10 sections
  1. Name the recipient before inspecting the address.
  2. Distinguish instructions, control, and acceptance.
  3. Check the actual custody arrangement.
  4. Follow a fictional payment through two recipients.
  5. Authenticate the instruction as a complete package.
  6. A changed destination is a new decision.
  7. Keep token controls and refund rights separate.
  8. Close the file with both technical and commercial evidence.
  9. Plan exceptions before the transfer becomes an incident.
  10. The Bitcoin Lawyer take

Name the recipient before inspecting the address.

A citizenship contribution or professional invoice can involve an advisor, an authorized agent, a settlement service, a bank, and a government recipient. Their names may appear in the same email. That does not make them the same payee or mean that a transfer to the first party reaches the last party directly.

Identify the person or entity to whom the obligation is owed. Then identify who is authorized to receive payment on its behalf, if anyone. Ask for the contractual or official basis of that authority. A familiar logo, a working QR code, and a past successful payment do not establish the current recipient for a new obligation.

If an intermediary will remit the money onward, describe that as a separate step. Record who controls the balance in the meantime, what requires its release, and which evidence will confirm onward payment. The applicant should know whether the first receipt acknowledges an intermediary deposit, a service fee, or satisfaction of the government obligation.

Distinguish instructions, control, and acceptance.

A wallet can show a signed transaction before it has been broadcast. A network can show a transaction before the recipient’s confirmation policy is satisfied. A recipient can see value arrive before matching it to an invoice. Keep these events distinct rather than reporting each as “paid”.

The Bitcoin developer guide explains that broadcast alone does not establish receipt and that confirmations increase confidence against competing transaction history. The commercial acceptance threshold belongs in the recipient’s instructions. Do not promise a universal confirmation count or elapsed time for every transaction, and do not treat a wallet’s success screen as the final contractual acknowledgment.

For an exchange withdrawal, approval within the exchange is another event. The platform may still need to sign and broadcast. For a bank payment, the sender’s debit is different from the beneficiary’s credited and usable balance. At each stage, retain the evidence that establishes that stage rather than stretching one screenshot to cover the whole route.

Check the actual custody arrangement.

A processor can observe an address and match an incoming transfer without holding the spending keys. Other arrangements put the signing capability on a server or with a third party. The product name alone does not establish which arrangement is in use or who can change the receiving instructions.

BTCPay Server’s documentation distinguishes hardware-wallet and partially signed transaction workflows from a hot wallet whose seed is stored on the server. That difference is why a general statement about software architecture should not become a blanket custody guarantee for every installation, asset, or plugin. Verify the particular configuration and responsibilities relevant to the payment.

Where someone holds funds under an escrow arrangement, obtain the agreement identifying the holder, assets, release conditions, dispute process, and applicable law. A provider describing its ordinary balance as escrow does not supply those terms. Questions about beneficial ownership, creditor claims, and legal discharge require the relevant qualified professional, not assumptions based on key possession.

Follow a fictional payment through two recipients.

Imagine that Priya receives an approved instruction to pay a service provider, which must then make a separate statutory payment. The provider supplies a Bitcoin invoice. Priya controls her wallet before signing. Once her transaction spends to the provider’s address, the provider controls the received value under whatever agreement governs that first payment. The government has not necessarily received anything at this stage.

The provider’s invoice system marks the transfer confirmed after its stated threshold. That tells Priya how the system treated the on-chain payment. The provider then issues a receipt identifying her file and the obligation covered. If this receipt concerns only the provider’s fee, it says nothing about the statutory contribution. If it acknowledges funds held for onward remittance, the release terms and next receipt still matter.

Suppose the provider later sells the received Bitcoin and sends fiat to the authorized government account. That is a second settlement sequence with its own counterparty, exchange rate, bank route, and acknowledgment. Priya needs evidence that connects the remittance to her file. A copy of her first transaction remains useful, but cannot prove an onward bank credit that happened later.

The arrangement may be appropriate if authorized, disclosed, and properly documented. Its complexity should appear before payment, while Priya can compare alternatives and obtain advice. Calling it direct government settlement would conceal a material dependency. A provider’s promise to remit also raises different questions from a government’s confirmation that the required contribution was received.

If the provider becomes unavailable between the two events, the relevant agreement and legal rights become central. Key control identifies who can move the coins; it does not by itself determine whether Priya has an ownership interest, a debt claim, or another remedy. Those legal questions require the applicable contract and jurisdiction. Avoid assuming that an attractive payment interface answers them.

Authenticate the instruction as a complete package.

Check the legal payee, file reference, amount, asset, network, destination, expiry, and required memo together. An address can be technically valid but belong to the wrong recipient or unsupported network. A changed instruction should be verified through a known independent contact route, not only by replying to the message that introduced the change.

Confirm how fees affect the amount received. An exchange may deduct a withdrawal charge; a wallet may require a network fee separately. The invoice governs the required receipt. For a token transfer, identify the supported token, and network rather than relying on a matching ticker or familiar address format.

Do not improvise a small test payment against a fixed invoice. Ask whether a test is permitted, how it will be credited, and whether the balance requires a new instruction. An unexpected partial payment can create an exception. A successful test also cannot certify future liquidity, an intermediary’s solvency, or acceptance of a different high-value transaction.

A changed destination is a new decision.

Consider a separate fictional event: an email announces that the receiving wallet has changed shortly before Priya plans to send. The new address is syntactically valid and the email includes the correct invoice number. Neither fact authenticates the change. Information copied from an existing correspondence thread can make a false instruction appear credible.

Use the independently established contact or portal to verify the replacement instruction. Confirm the complete package, including payee, amount, asset, network, and file reference. Record who authorized the change and whether the prior instruction is canceled. If the verification channel itself is uncertain, pause the payment until the responsible party can establish it. Urgency is not evidence of authority.

The signer should review the transaction that will actually be authorized, not just the earlier invoice. Where a company uses more than one signer, each needs the approved instruction and enough information to identify an unexpected destination or amount. This is a governance step, not a request to expose recovery words or combine independent keys in one place.

If the instruction expires during verification, obtain a current instruction. Reusing a stale exchange-rate quote may produce an underpayment or disagreement even when the destination is legitimate. A correct address does not cure an expired commercial offer. The payer should know which event must occur within the validity window and who decides exceptions.

Keep token controls and refund rights separate.

Holding keys to an address does not mean controlling every rule of an issued token. Tether’s terms reserve powers to freeze tokens in specified legal and risk circumstances and impose eligibility restrictions. A USDT transfer therefore deserves an issuer-and-permitted-use review as well as a network check. This article does not determine a particular payer’s eligibility.

Payment reversibility and a contractual refund are also different questions. A promise to refund, if one exists, identifies an obligation and a responsible party. It does not give the sender a technical ability to reverse a confirmed Bitcoin transaction. Ask how a permitted refund would be authorized, valued and returned, including fees, and recipient verification.

Do not import a government contribution’s treatment into a professional fee, or one provider’s policy into another’s contract. An incorrect transfer, application withdrawal, and refusal can trigger different provisions. Preserve the terms actually accepted for each payment. Nothing in this educational article alters Bitcoin Lawyer’s approved engagement or refund terms.

Close the file with both technical and commercial evidence.

Retain the authenticated invoice, any authorized changes, payer approval, transaction identifier, relevant asset and network, amount, fees, and recipient acknowledgment. Where a processor assigns a payment status, preserve what that status means and when it changed. Keep a later onward remittance separate from the initial payment.

If the receiving wallet differs from the one previously cleared, or an exchange replaces the proposed self-custody route, obtain the necessary updated instructions before sending. If an underpayment, duplicate or wrong-network transfer occurs, stop improvising and use the recipient’s verified exception process. A support response should remain attached to the affected transaction.

The finished record should answer who paid, who received, who controlled the value between those points and which obligation was acknowledged. Private keys, recovery words, and unrestricted signing access do not belong in that record. Clear documentation can reduce confusion without requiring the applicant to surrender control merely to demonstrate it.

Plan exceptions before the transfer becomes an incident.

An exception process is most useful when its owner is already identified. Ask who handles an underpayment, delayed confirmation, duplicate transfer, or payment from a different approved wallet. The answer should include a verified communication channel and the records needed to investigate. It should not depend on finding an unfamiliar support account in a public chat after the money moves.

For example, if an exchange deducts a withdrawal fee from the invoice amount, the recipient may receive less than required. Preserve the original instruction and the exchange’s fee record. Ask whether a supplementary payment is permitted and how it will be credited. Do not assume that several partial transfers will be treated as one completed payment or send an extra amount to an address copied from an old invoice.

Where a refund is contractually due, confirm the authorized recipient of that refund and the valuation basis. The original sending address may belong to an exchange or shared service rather than a wallet that can safely receive a return. A refund should therefore follow authenticated instructions and the applicable agreement. It is another payment event to evidence, not a reversal button attached to the first transaction.

The whole picture

The Bitcoin Lawyer take

Verify the recipient and instructions independently before sending. At the end of the transaction, retain both the transfer evidence and the acknowledgment of what the payment settled.

Bitcoin makes a transfer observable without making every commercial fact visible. A transaction hash cannot establish a recipient’s authority, an intermediary’s release duty, or a government’s acceptance of the payment. Resolve those facts while the decision to send still belongs to you.

Cite this essay

Adam Juchniewicz, CEO, Bitcoin Lawyer. “Who controls a payment between your wallet and its final recipient?” https://www.bitcoinlawyer.com/journal/custody-between-wallet-and-recipient