📅 Original date posted:2014-01-27
📝 Original message:On 01/27/2014 03:54 PM, Gavin Andresen wrote:
> The purpose of PaymentACK is to give the customer reassurance that their
> payment request has been received and will be processed (or not).
>
> If it is syntactically incorrect or invalid in a way that the payment
> processor can detect right away then a PaymentACK with a message saying
> that there is a problem should be the response.
Thanks for the clarification. So I am *always* supposed to reply with an
ack. I was assuming that if I actually send a nack, I would just close
the connection without sending an ack.
Maybe that should be mentioned in the spec explicitly. I must admit that
I think the name of the message is misleading -- PaymentResponse would
make this clearer.
Andreas Schildbach [ARCHIVE] /
npub1xg…adsv7
2023-06-07 15:12:35
in reply to nevent1q…2vf0
Author Public Key
npub1xg2m84malu0cfm4444r0kysx4rgk27e75aj6sz6538kw8fcz627qeadsv7Seen on
wss://relay.noswhere.comPublished at
2023-06-07 15:12:35Event JSON
{
"id": "9d319a825fd09ae2392a0963b6930cea20bd6a2c54fb775be8f82b629016c07d",
"pubkey": "3215b3d77dff1f84eeb5ad46fb1206a8d1657b3ea765a80b5489ece3a702d2bc",
"created_at": 1686150755,
"kind": 1,
"tags": [
[
"e",
"cd2b50b4c4e42fbfc1a32e56fc92dceb6f26c7bd94e21234287a2ef4a6ea523e",
"",
"root"
],
[
"e",
"c941842671922dae1b536203869e997adf3be9f9e51eadca05767a473aab46f8",
"",
"reply"
],
[
"p",
"857f2f78dc1639e711f5ea703a9fc978e22ebd279abdea1861b7daa833512ee4"
]
],
"content": "📅 Original date posted:2014-01-27\n📝 Original message:On 01/27/2014 03:54 PM, Gavin Andresen wrote:\n\n\u003e The purpose of PaymentACK is to give the customer reassurance that their\n\u003e payment request has been received and will be processed (or not).\n\u003e \n\u003e If it is syntactically incorrect or invalid in a way that the payment\n\u003e processor can detect right away then a PaymentACK with a message saying\n\u003e that there is a problem should be the response.\n\nThanks for the clarification. So I am *always* supposed to reply with an\nack. I was assuming that if I actually send a nack, I would just close\nthe connection without sending an ack.\n\nMaybe that should be mentioned in the spec explicitly. I must admit that\nI think the name of the message is misleading -- PaymentResponse would\nmake this clearer.",
"sig": "95f4810009b60133efdb61f8cf26e705cb3cc9164ac600fa98a1e5cafae48d45d8f3adc3ca9b6dca65614d63ad3a3e05663f3528c6e5fa16cceae15360301826"
}