📅 Original date posted:2013-08-19
📝 Original message:I was just reviewing the integration work to integrate the Payment
Protocol into our products. Is there any notion of a standardized
invoice serialisation? If i pay for two Burgers and one Club Mate, how
would my Bitcoin Wallet be able to know that? Right now, i would simply
put that into "memo" and come up with my own serialisation mechanism.
Second, is there a way to communicate acceptance levels of TX
(unconfirmed, 1 conf, 6 conf) maybe using several PaymentACK?
-Andreas
Andreas Petersson [ARCHIVE] /
npub10z…qsg9a
2023-06-07 15:05:40
in reply to nevent1q…qlus
Author Public Key
npub10zyxjrelgpp85qc93pnt8e4yx0jsxm27sn9lsypkhlrttjpmjktqkqsg9aPublished at
2023-06-07 15:05:40Event JSON
{
"id": "47269c02ad4eef5f80239a93a657f2db801d6edd1b2599b23325b71e0cf3d3bb",
"pubkey": "7888690f3f40427a03058866b3e6a433e5036d5e84cbf81036bfc6b5c83b9596",
"created_at": 1686150340,
"kind": 1,
"tags": [
[
"e",
"c5e56f29f73ae037803d4c07616ae2b1311014baf62f54f10973c0b1b685df68",
"",
"root"
],
[
"e",
"0ed2f0d369858906968427f7732886ab86e273480f36fc99d9aab18c879e0e88",
"",
"reply"
],
[
"p",
"5cb21bf5d7f25a9d46879713cbd32433bbc10e40ef813a3c28fe7355f49854d6"
]
],
"content": "📅 Original date posted:2013-08-19\n📝 Original message:I was just reviewing the integration work to integrate the Payment\nProtocol into our products. Is there any notion of a standardized\ninvoice serialisation? If i pay for two Burgers and one Club Mate, how\nwould my Bitcoin Wallet be able to know that? Right now, i would simply\nput that into \"memo\" and come up with my own serialisation mechanism.\n\nSecond, is there a way to communicate acceptance levels of TX\n(unconfirmed, 1 conf, 6 conf) maybe using several PaymentACK?\n\n-Andreas",
"sig": "9c38f7c5bcbf89cec39424954bfd2d60e09c3d5c4781bbe524d0d59ee959a06d2af2ec6948e3ebf40e5c30a4adfdcebf72d34f98ca47e01b9e04d3b2350287f0"
}