<p>Usually, when people want to pay each other, they are already communicating as they have been arranging some form of transaction. Just like with other settlement methods, the receiver communicates to the sender how they would like to receive payment.</p>
<p>The receiver may do so e.g. by sending an invoice, displaying payment instructions on the checkout page of their merchant website, copying their address into chat, or displaying a QR-code to be scanned with a handheld device.</p>

CC BY-SA 4.0
2021-10-26T15:52:24.800Z
2021-10-26T15:52:24.800Z
Murch
<blockquote>
<p><strong>Person A wants to send some Bitcoins to person B. How will person A come to know about the person B's address?</strong></p>
</blockquote>
<p>Person B shows Person A a QR-code displayed on B's smartphone wallet. Person A uses their phone's wallet to capture an image of the QR-code and extract the address.</p>
<p>or</p>
<p>Person B spells out the address over the phone, and A enters into A's wallet as the receiving address.</p>
<p>or</p>
<p>Person B sends the address in a Facebook message</p>
<p>or</p>
<p>any of a thousand other ways people communicate information with one another.</p>
<hr />
<blockquote>
<p><strong>And for every transaction Person B's address (as well as Person A's) changes. How will Person A keep track of these changes?</strong></p>
</blockquote>
<p>Person A and B do one of the above each time A needs to send B money.</p>

CC BY-SA 4.0
2021-10-26T11:17:19.240Z
2021-10-26T11:17:19.240Z
RedGrittyBrick
<blockquote>
<p>And for every transaction Person B's address (as well as Person A's) changes. How will Person A keep track of these changes?</p>
</blockquote>
<p>In addition to what Murch and RedGrittyBrick wrote, it is also possible for Person B to give Person A an '<a href="https://bitcoin.stackexchange.com/questions/78295/what-makes-an-extended-public-or-private-key">extended public key</a>', which is a piece of information that will allow Person A to derive new addresses that belong to Person B. By using the extended public key, Person A can make many payments to Person B, without having to contact Person B for new addresses each time (and without reusing an old address).</p>
<p>Note though, that giving someone an extended public key gives them a full view of your wallet history at that account level (a serious privacy concern), so it is only something that should be done in certain cases, for trusted individuals. Additionally, if any of the (non-hardened) child private keys are compromised, someone that has the extended public key <a href="https://bitcoin.stackexchange.com/questions/61478/determining-xprv-from-xpub-and-child-private-key">will be able to derive the extended private key</a> (thus compromising all other child private keys)</p>

CC BY-SA 4.0
2021-10-29T05:13:45.073Z
2021-10-29T05:13:45.073Z
chytrik
<p>Person A wants to send some bitcoins to Person B. How will Person A come to know about the Person B's address? And for every transaction Person B's address (as well as Person A's) changes. How will Person A keep track of these changes?</p>

<address><receiving>
How does a recipient share his/her address with a sender?
Mukesh Kumar
# How does a recipient share his/her address with a sender?

(Asked by: username_0 on 2021-10-26)

Person A wants to send some bitcoins to Person B. How will Person A come to know about the Person B's address? And for every transaction Person B's address (as well as Person A's) changes. How will Person A keep track of these changes?

**Tags:** address, receiving


---

## 3 answers

### Answer by username_1 on 2021-10-26. Score: 2 | Accepted answer

Usually, when people want to pay each other, they are already communicating as they have been arranging some form of transaction. Just like with other settlement methods, the receiver communicates to the sender how they would like to receive payment.

The receiver may do so e.g. by sending an invoice, displaying payment instructions on the checkout page of their merchant website, copying their address into chat, or displaying a QR-code to be scanned with a handheld device.


---

### Answer by username_2 on 2021-10-26. Score: 2

> **Person A wants to send some Bitcoins to person B. How will person A come to know about the person B's address?**

Person B shows Person A a QR-code displayed on B's smartphone wallet. Person A uses their phone's wallet to capture an image of the QR-code and extract the address.

or

Person B spells out the address over the phone, and A enters into A's wallet as the receiving address.

or

Person B sends the address in a Facebook message

or

any of a thousand other ways people communicate information with one another.

---

> **And for every transaction Person B's address (as well as Person A's) changes. How will Person A keep track of these changes?**

Person A and B do one of the above each time A needs to send B money.


---

### Answer by username_3 on 2021-10-29. Score: 0

> And for every transaction Person B's address (as well as Person A's) changes. How will Person A keep track of these changes?

In addition to what username_1 and username_2 wrote, it is also possible for Person B to give Person A an '[extended public key](https://bitcoin.stackexchange.com/questions/78295/what-makes-an-extended-public-or-private-key)', which is a piece of information that will allow Person A to derive new addresses that belong to Person B. By using the extended public key, Person A can make many payments to Person B, without having to contact Person B for new addresses each time (and without reusing an old address).

Note though, that giving someone an extended public key gives them a full view of your wallet history at that account level (a serious privacy concern), so it is only something that should be done in certain cases, for trusted individuals. Additionally, if any of the (non-hardened) child private keys are compromised, someone that has the extended public key [will be able to derive the extended private key](https://bitcoin.stackexchange.com/questions/61478/determining-xprv-from-xpub-and-child-private-key) (thus compromising all other child private keys)


---

