1/
I have been looking at Web Monetization.
Partly because I am curious. And, partly because I may implement them for CrowdBucks.
One part of Web Monetization are "Payment-Pointers".
They aren't URLs. But sort of URL-like, in that they point somewhere.
For example, my web-site is:
Then I could let people people pay me with this Payment-Pointer:
$reiver.link
#CrowdBucks #FediDev #Fediverse #PaymentPointer #WebMonetization
2/
The Payment-Pointer:
$reiver.link
Would resolve to the HTTP-URL:
https://reiver.link/.well-known/pay
And, that (HTTPS-URL) would return some type of JSON document.
#CrowdBucks #FediDev #Fediverse #PaymentPointer #WebMonetization
3/
I was looking around for a specification for Web Monetization Payment-Pointers. The closest thing I could find is this:
https://github.com/interledger/paymentpointers.org
https://github.com/interledger/rfcs/blob/main/0026-payment-pointers/0026-payment-pointers.md
#CrowdBucks #FediDev #Fediverse #PaymentPointer #WebMonetization
Payment Pointers are a standardized identifier for payment accounts. In the same way that an email address provides an identifier for a mailbox in the email ecosystem a payment pointer is used by an account holder to share the details of their account with a counter-party.
4/
One thing that seems missing is — what is supposed to be returned from the HTTPS-URL that a Web Monetization Payment-Pointer resolves to?
What are the fields in the JSON?
...
I assume it is JSON because of an example HTTP request here (that does NOT show the response):
https://paymentpointers.org/flow/#example
.
#CrowdBucks #FediDev #Fediverse #PaymentPointer #WebMonetization
Perhaps I missed it, but — which page of that PDF shows an example JSON structure from the response of a Payments-Pointer?
@reiver ⊼ (Charles) 
LovesTha🥧