Added x-cashu method to NUT-18 #204

2024-12-23T18:40:25Z

Egge21M commented

2024-12-23 18:40:25 +00:00

(Migrated from github.com)

This adds a new method to NUT-18, that allows payment requests to be used with the X-Cashu protocol. This is an attempt to standardize the flow around x-cashu further, to enable interoperability between protected endpoints and wallets.

👍 1

a1denvalu3 (Migrated from github.com) approved these changes

2025-01-05 16:31:27 +00:00

18.md

					
				@ -81,0 +85,4 @@

				- tags: `[["c", "replay"]]`

				The payment is expected in the X-Cashu header on a request to the specified endpoint.

				The tags specify constraints that the request MUST have. `replay` can be found in Payment Requests on HTTP 402 responses and requires that the exact same request is send again, but with a X-Cashu header paying the PR.

Tags specify constraints that the request **MUST** satisfy. The presence of a `c` tag with `replay` value informs the payer that "replay" could be returned on HTTP 402 responses, prompting the payer to re-attempt the exact same request but with a X-Cashu header paying the Payment Request.

```suggestion Tags specify constraints that the request **MUST** satisfy. The presence of a `c` tag with `replay` value informs the payer that "replay" could be returned on HTTP 402 responses, prompting the payer to re-attempt the exact same request but with a X-Cashu header paying the Payment Request. ```

a1denvalu3 (Migrated from github.com) reviewed

2025-02-09 09:50:06 +00:00

18.md

					
				@ -81,0 +85,4 @@

				- tags: `[["c", "replay"]]`

				The payment is expected in the X-Cashu header on a request to the specified endpoint.

				The tags specify constraints that the request MUST have. `replay` can be found in Payment Requests on HTTP 402 responses and requires that the exact same request is send again, but with a X-Cashu header paying the PR.