URI to send invoice number back to reciever.

[kalon]

Hi all,

I'm wondering if someone can explain something for me.

I know there has been efforts to make a standard URI scheme to in Bitcoin transactions. There is a field for label and message which can be fill by the person creating the URI and QR code but it's my understanding that those fields are just to help the sender keep track of payments and are not transmitted back to the receiver in any way.

It seems to me that having a short field in the URI for an invoice number which could be passed to the sender's client and then sent back with the payment would be helpful for merchants who wish to keep track of customers.

I'd think this would be an easier method than generating new addresses for each transaction and should already be possible since I've heard about other  additional text getting in the blockchain.

Is there some reason that this isn't a standard part of the client or am I wrong about how the system works in some way?

[franky1]

i think gavin mentioned something happening in version 0.9 that will eleviate the multi-address issue, and it sounded something like the idea you suggested

[tgerring]

It seems to me that having a short field in the URI for an invoice number which could be passed to the sender's client and then sent back with the payment would be helpful for merchants who wish to keep track of customers.

The blockchain doesn't store arbitrary data, so if I understand the 0.9 changes correctly, it involves the client establishing a direct connection with the merchant to pass additional details such as invoice number.