📅 Original date posted:2014-02-03 📝 Original message:Over http, the merchant ...

Christophe Biocca [ARCHIVE] /

npub1mtx…g5zm

2023-06-07 15:12:56

in reply to nevent1q…rev7

📅 Original date posted:2014-02-03
📝 Original message:Over http, the merchant doesn't have the ability to reach out to the
consumer's bitcoin wallet on their own. So sending "Cancel Payment
Request" to the user is impossible.

If the customer doesn't want to send, nothing ever needs to happen. So
sending a "Reject Payment Request" to the merchant is useless.

The unhappy path scenario with Payment Requests (customer paid, but
for whatever reason that payment is no longer valid) can be simply
solved in 1 of 2 ways:

If the merchant realizes the mistake, they can refund the money.
If the customer realizes the problem, they can contact the merchant,
provide the signed request, and ask the merchant to return the funds.

What isn't covered?

On Mon, Feb 3, 2014 at 1:08 PM, Tim Tuxworth <tim at go-taxi.biz> wrote:
> The process described in BIP70 might be ok for a simple "happy path"
> scenario, but what if things don't work so smoothly. I'm not talking
> here about technical issues, but _very common_ business scenarios such as:
>
> e.g. Merchant cancels request before payment is sent, such as when:-
> - the merchant realizes that they charged the wrong amount
> - the merchant realizes that they send the payment request to the wrong
> customer
> ...
>
> e.g. the Merchant or Customer decides to cancel the transaction after
> the payment request is sent because:-
> - the customer decides to pay by some other mechanism like cash or
> credit/debit
> - the customer doesn't have sufficient funds and decides not to purchase
> - the customer changes their mind and decides not to purchase
> ...
>
> It strikes me that a "Cancel Payment Request" message is required
> and a "Reject Payment Request" may also be required (or maybe use the
> same message for both).
>
> Tim Tuxworth
>
> ------------------------------------------------------------------------------
> Managing the Performance of Cloud-Based Applications
> Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
> Read the Whitepaper.
> http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development

Author Public Key

npub1mtxs7jztn027d9cylej99hltqq9vq84uxm80zl4naxafd9hpxqwsj9g5zm

Show more details

Published at

2023-06-07 15:12:56

Kind type

1 Short Text Note

Event JSON

{ "id": "5af3079a3eb139e829a4d401beed6b1adc36b6714ec1fbd3fd17a685ae28bf49", "pubkey": "dacd0f484b9bd5e69704fe6452dfeb000ac01ebc36cef17eb3e9ba9696e1301d", "created_at": 1686150776, "kind": 1, "tags": [ [ "e", "581e40456bf142b1bf0aa41af407881bb0efaad61a52ade99b9d2789a9147eec", "", "root" ], [ "e", "52f9fe052fcfb58c78c0a5228acc33fa5c5abfdf943986dc3fcfa576236ef16a", "", "reply" ], [ "p", "0f1e6571a51e7a632f23cdf207105be0c89446b628349a6f290d5a9dab4a5743" ] ], "content": "📅 Original date posted:2014-02-03\n📝 Original message:Over http, the merchant doesn't have the ability to reach out to the\nconsumer's bitcoin wallet on their own. So sending \"Cancel Payment\nRequest\" to the user is impossible.\n\nIf the customer doesn't want to send, nothing ever needs to happen. So\nsending a \"Reject Payment Request\" to the merchant is useless.\n\nThe unhappy path scenario with Payment Requests (customer paid, but\nfor whatever reason that payment is no longer valid) can be simply\nsolved in 1 of 2 ways:\n\nIf the merchant realizes the mistake, they can refund the money.\nIf the customer realizes the problem, they can contact the merchant,\nprovide the signed request, and ask the merchant to return the funds.\n\nWhat isn't covered?\n\nOn Mon, Feb 3, 2014 at 1:08 PM, Tim Tuxworth \u003ctim at go-taxi.biz\u003e wrote:\n\u003e The process described in BIP70 might be ok for a simple \"happy path\"\n\u003e scenario, but what if things don't work so smoothly. I'm not talking\n\u003e here about technical issues, but _very common_ business scenarios such as:\n\u003e\n\u003e e.g. Merchant cancels request before payment is sent, such as when:-\n\u003e - the merchant realizes that they charged the wrong amount\n\u003e - the merchant realizes that they send the payment request to the wrong\n\u003e customer\n\u003e ...\n\u003e\n\u003e e.g. the Merchant or Customer decides to cancel the transaction after\n\u003e the payment request is sent because:-\n\u003e - the customer decides to pay by some other mechanism like cash or\n\u003e credit/debit\n\u003e - the customer doesn't have sufficient funds and decides not to purchase\n\u003e - the customer changes their mind and decides not to purchase\n\u003e ...\n\u003e\n\u003e It strikes me that a \"Cancel Payment Request\" message is required\n\u003e and a \"Reject Payment Request\" may also be required (or maybe use the\n\u003e same message for both).\n\u003e\n\u003e Tim Tuxworth\n\u003e\n\u003e ------------------------------------------------------------------------------\n\u003e Managing the Performance of Cloud-Based Applications\n\u003e Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.\n\u003e Read the Whitepaper.\n\u003e http://pubads.g.doubleclick.net/gampad/clk?id=121051231\u0026iu=/4140/ostg.clktrk\n\u003e _______________________________________________\n\u003e Bitcoin-development mailing list\n\u003e Bitcoin-development at lists.sourceforge.net\n\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development", "sig": "3a7b4f7677176f3faa6eb079b3a4b34d4c38df1eca25c94c3bba28407ffc6923329d421921d1d1a8d1e1fbe504ab737fc3d90cbc97e8e89cd4ca57925f8041ae" }