Payment Request should include destination Tag
Wietse Wind
There's also another native field:
InvoiceID
. So... Memo (what format)? InvoiceID? Destination Tag?I assume this is from a small business retail perspective?
AtheistAgnstViolence
Wietse Wind: Hi Wietse, yes I run a very small business and I like the XRPL and see a lot of potential, and would like to help build out even if only in my very small business.
What I would like to do is to overlay a QR Code on the PDF invoices I issue (I can easily manually do that). Similar to the QR code that Xumm can produce, I would like the Xumm QR Code to also contain the InvoiceID and that would be enough for me.
So when my customer receives my invoice with the QR code, they get directed to Xumm to authorise the payment, and when I receive the payment, I get the equivalent in XRP along with the InvoiceID information. Also would need to ensure the InvoiceID is required (similar to setting that requirement for destination tag) so that I can reconcile with my invoices issued.
As a little security check, I would issue my pdf invoice in protected mode so that changes to the invoice could be detected (although not 100% guaranteed against fraud). As yet, I don't think there is some way within the QR Code/Xumm to ensure there has been no changes to the payment address contained in the QR Code, e.g. a nefarious employee of my customer overlays a new QR Code with their own XRPL address to fool their payments team.
My invoice numbers are numeric, but being able to extract alphanumeric data would be fine. If the InvoiceID is required to be in a Hex format or ASCII format, I would somehow need to be able to convert to my accounting system alphanumeric format.
Let me know if I can assist in anyway. Thanks.
Wietse Wind
AtheistAgnstViolence: Totally clear :)
While this is not supported when generating requests in XUMM (obviously, hence this suggestion), I have good news: it is already possible :D
If you generate QR contents like this:
xrpl://rwietsevLFg8XSmG3bEZzFein1g8RBqWDZ?dtag=123
So:
xrpl://{account}?dtag={somenumber}
XUMM will recognize that when scanned from the invoice and prefill the destination tag. Try it: https://mprugtl.dlvr.cloud/pasted_1.png
(No need to send obviously, you can cancel in the last confirmation screen where XUMM shows the TX overview and the tag). Hope that helps for now, printing those QRs on your invoices ;)
AtheistAgnstViolence
Thanks Wietse Wind, is it possible include two items in the one QR code that Xumm recognises, i.e. tag and amount?
dtag=123
amount=500
What would the text be? Obviously not the below but...
i.e. xrpl://rwietsevLFg8XSmG3bEZzFein1g8RBqWDZ?dtag=123 amount=500
Wietse Wind
AtheistAgnstViolence: Definitely:
xrpl://rwietsevLFg8XSmG3bEZzFein1g8RBqWDZ?dtag=123&amount=500
https://hpqs42g.dlvr.cloud/pasted_1.png
AtheistAgnstViolence
Wietse Wind: That's great and I really appreciate your responses, and finally, with the amount field, could I set that as AUD instead of XRP? So that Xumm would automatically convert to the right amount of XRP when the QR Code is scanned?
Wietse Wind
AtheistAgnstViolence: Nope, that last one we didn't implement yet. Sorry.
L P
Wietse Wind: Thanks for the response. Looking forward to the time you implement. Really appreciate the work the XRPL Labs team has done. Thanks & Cheers.
B
Bert de Hoogh
I support the idea of sending a memo with a payment request but isn't a memo field a better option than a destination tag?
Enough confusion about (forgetting) destination tags so keep the destination tag for what it is ment for.
L P
Bert de Hoogh: Yes agree the memo field would be a better option than using the SourceTag field
L P
And if multiple payments were to occur from the one payer, identify which invoice the payment relates to.