<p>In Ripple <a href="https://ripple.com/wiki/Transaction_Format#Payment_.280.29" rel="nofollow">payment transactions</a> we can specify an invoice ID that is used to make payments for a particular invoice. Is there a way to specify such an invoice ID in <a href="https://ripple.com/wiki/Ripple_URIs#send" rel="nofollow">Ripple's URI scheme</a>?</p>

CC BY-SA 3.0
2013-10-29T12:00:00.483Z
I'm actually curious of this one myself.  After digging through the rippled code, I didn't readily see a way to do it.  I believe it might be a shared hash, so it could be originating from someone else.  Let me get out my Schwartz horn and see if we can call for help...
RLH
CC BY-SA 3.0
2013-10-29T14:10:08.363Z
The InvoiceID can be anything at all that communicates to the recipient how the sender intended the payment to be applied. The Bitcoin outbound bridge uses it to [designate the Bitcoin address](https://ripple.com/wiki/Services_API#Payments) of the recipient. I don't know if the URI scheme offers a way to specify it though. If not, it should.
David Schwartz
CC BY-SA 3.0
2013-10-29T16:31:29.287Z
@ThePiachu thanks for adding a github issue. I'll add InvoiceID.
Vahe Hovhannisyan
<transactions><ripple><bip21-uri>
Is there a way to specify an invoice ID in Ripple URI?
ThePiachu
# Is there a way to specify an invoice ID in Ripple URI?

(Asked by: username_0 on 2013-10-29)

In Ripple [payment transactions](https://ripple.com/wiki/Transaction_Format#Payment_.280.29) we can specify an invoice ID that is used to make payments for a particular invoice. Is there a way to specify such an invoice ID in [Ripple's URI scheme](https://ripple.com/wiki/Ripple_URIs#send)?

**Tags:** transactions, ripple, bip21-uri

> **Comments:**
> **username_1**: I'm actually curious of this one myself.  After digging through the rippled code, I didn't readily see a way to do it.  I believe it might be a shared hash, so it could be originating from someone else.  Let me get out my username_2 horn and see if we can call for help...  
> **username_2**: The InvoiceID can be anything at all that communicates to the recipient how the sender intended the payment to be applied. The Bitcoin outbound bridge uses it to [designate the Bitcoin address](https://ripple.com/wiki/Services_API#Payments) of the recipient. I don't know if the URI scheme offers a way to specify it though. If not, it should.  
> **username_3**: @username_0 thanks for adding a github issue. I'll add InvoiceID.  

---

## 0 answers

