Ask the receiving-account owner one precise question
- Identify the account intended for this HBAR credit
Obtain the receiving instruction from the wallet or platform that should hold the result. If the account is managed by an organization, ask its legitimate administrator about the current receiving policy rather than relying on an old screenshot or a general wallet description.
- Establish whether receiver signing is required
Hedera supports a receiverSigRequired setting. For a CryptoTransfer credit to an account using that setting, the receiving account must also sign. Ask whether that requirement applies to the intended account; it is not a general requirement for every person buying HBAR.
- Resolve payout compatibility before the BTC payment
If a receiving signature is needed, ask how the intended transfer can be accepted through the actual service workflow. Do not assume this exchange provides a recipient co-signing flow merely because the Hedera protocol supports one. An unresolved signing question belongs before funding.
A receiving signature is an account policy, not another address field
The Hedera transfer specification describes signatures from accounts being debited and also from credited accounts whose receiverSigRequired flag is set. This is a rule about authorization of the transfer. It does not become satisfied by entering an account identifier correctly or by adding a note to a different part of the exchange.
Keep the account’s controls under its owner’s management. This page does not ask you to turn off receiver signing, replace keys or give support a private key. If your account uses an approval process, its owner should review any proposed transaction through that legitimate process. Do not sign an unfamiliar operation just because someone labels it a receiving verification.
Record the unanswered condition without exposing account control
| Detail | What to confirm | What it cannot replace |
|---|---|---|
| HBAR receiving account | The account that should be credited | Its current incoming-transfer policy |
| Receiver-signature setting | Whether the account requires a receiving signature | The actual supported co-signing workflow |
| Compatibility answer | How this particular payout can be accepted | A confirmed Bitcoin funding payment |
| Payout result | Whether the intended HBAR credit completed | The recipient’s own later use of the balance |
If a restricted recipient was discovered after funding
- Keep the existing order and payment references together
- Explain that the intended Hedera account has a receiving-signature requirement. Ask for the actual payout state to be reviewed. Do not infer successful HBAR receipt from a Bitcoin confirmation, and do not create another BTC payment simply to retry an unresolved payout.
- Describe the condition without sending secrets
- The public account reference, order reference and known transfer status help identify the case. Wallet recovery material and private signing credentials do not belong in that explanation. Only the legitimate account owner should decide how its receiving policy is managed.
- Verify the final credit against the intended account
- If a payout result is supplied, compare it with the intended recipient and the account’s receiving record. An earlier answer about supported address syntax does not prove that a signature-restricted transfer completed.
Questions about a signature-restricted HBAR recipient
- Does every HBAR recipient have to co-sign an incoming transfer?
- No. The discussed requirement applies to an account using the receiverSigRequired setting. Establish the intended account’s actual policy.
- Does a valid account identifier prove that a restricted payout can complete?
- No. Address syntax and the receiving account’s required signatures are different conditions. Clarify the supported process before paying BTC.
- Should I give the exchange my receiving account’s private key?
- No. Keep control material private. Ask about compatibility using the public account reference and the known order details.
Hedera receiving-policy references
Reviewed: