<p>There isn't any such thing as a "BIP70 URI" as I understand it.  To use BIP70, the client fetches a payment request from somewhere, typically an ordinary https url (which can also be embedded in a bitcoin: uri, see BIP72).  The payment request is passed to their Bitcoin wallet client, which generates the transaction as well as a Payment message which is sent back to the server at a given URL.  There is a <code>memo</code> field in the Payment message which you could use, but filling it in would be up to the user's wallet client.  I don't see any way for your payment request to instruct the software how to fill this in.</p>

<p>So you would have to tell the user how to fill in the <code>memo</code> field of the Payment message using their particular software (assuming their software supports it at all).  And if they should fail to do so, too bad - by the time you receive their Payment message the transaction has already been sent.  Though you could still refund their payment in that case (using the <code>refund_to</code> field of the Payment message).</p>

<p>If the user has already given you the address (e.g. entered it in a web form) then you could generate the payment request in such a way that the <code>payment_url</code> embeds their address (<a href="https://my.server.com/pay?email=buytickets@gmail.com" rel="nofollow noreferrer">https://my.server.com/pay?email=buytickets@gmail.com</a>).  Then when they send their Payment message to that url, an appropriate application on your site can record that address as being associated with the transaction.</p>

<p>Note that in all cases the user needs a lot more than just your Bitcoin address; you have to run a publicly available secure web server to negotiate the payment protocol, and the user will need its web address.</p>

CC BY-SA 3.0
2017-02-22T00:05:38.933Z
2017-02-22T00:11:57.330Z
2017-02-22T00:11:57.330Z
Nate Eldredge
<p>I'm trying to build an application that takes bitcoin and also an email. But when you send bitcoin you cannot send a message attached to it. Supposedly BIP70 solves this problem. How does a BIP70 URI look like? Example: I sell digital tickets that I email to my customers. My customers only have my bitcoin address. When they send Bitcoin to my address, how can they also send me their email address so I can email them the "digital ticket". Don't I have to have my URI something like this:</p>

<p>bitcoin:12A1MyfXbW6RhdRAZEqofac5jCQQjwEPBu?amount=1.2&amp;message=buytickets@gmail.com</p>

<message><bip70-payment-protocol>
How does a BIP70 url look like? I want to send my email to the person I'm sending my coins to.
Patoshi パトシ
# How does a BIP70 url look like? I want to send my email to the person I'm sending my coins to.

(Asked by: username_0 on 2017-02-21)

I'm trying to build an application that takes bitcoin and also an email. But when you send bitcoin you cannot send a message attached to it. Supposedly BIP70 solves this problem. How does a BIP70 URI look like? Example: I sell digital tickets that I email to my customers. My customers only have my bitcoin address. When they send Bitcoin to my address, how can they also send me their email address so I can email them the "digital ticket". Don't I have to have my URI something like this:

bitcoin:12A1MyfXbW6RhdRAZEqofac5jCQQjwEPBu?amount=1.2&message=buytickets@gmail.com

**Tags:** message, bip70-payment-protocol


---

## 1 answers

### Answer by username_1 on 2017-02-22. Score: 2

There isn't any such thing as a "BIP70 URI" as I understand it. To use BIP70, the client fetches a payment request from somewhere, typically an ordinary https url (which can also be embedded in a bitcoin: uri, see BIP72). The payment request is passed to their Bitcoin wallet client, which generates the transaction as well as a Payment message which is sent back to the server at a given URL. There is a `memo` field in the Payment message which you could use, but filling it in would be up to the user's wallet client. I don't see any way for your payment request to instruct the software how to fill this in.

So you would have to tell the user how to fill in the `memo` field of the Payment message using their particular software (assuming their software supports it at all). And if they should fail to do so, too bad - by the time you receive their Payment message the transaction has already been sent. Though you could still refund their payment in that case (using the `refund_to` field of the Payment message).

If the user has already given you the address (e.g. entered it in a web form) then you could generate the payment request in such a way that the `payment_url` embeds their address (<https://my.server.com/pay?email=buytickets@gmail.com>). Then when they send their Payment message to that url, an appropriate application on your site can record that address as being associated with the transaction.

Note that in all cases the user needs a lot more than just your Bitcoin address; you have to run a publicly available secure web server to negotiate the payment protocol, and the user will need its web address.


---

