12/
I have been looking for (working) Payment-Pointers being used by others.
But, ever time I find one — it doesn't work (mostly because one provides seems to have stopped working).
...
For example, over here:
https://web.archive.org/web/20250222120416/https://pupper-pages.glitch.me/
If I look at the HTML source-code, I see a Payment-Pointer.
But the host in the Payment-Pointer doesn't work.
#CrowdBucks #FediDev #Fediverse #PaymentPointer #PeerTube #WebMonetization
11/
I implemented Simple Payment Setup Protocol (SPSP) (from scratch) in the Go programming-language.
https://github.com/reiver/go-spsp
Base on the specification I found before.
#CrowdBucks #FediDev #Fediverse #Golang #PaymentPointer #PeerTube #WebMonetization
Package spsp implements the Simple Payment Setup Protocol (SPSP), for the Go programming language. The Simple Payment Setup Protocol (SPSP) is used by the Interledger Protocol, Open Payments, Web M...
10/
I found some updates for the https://paymentpointers.org/ web-site that haven't been deployed:
https://github.com/interledger/paymentpointers.org/pull/57/files
Some of it confirms things I suspected. But, there is also new information in there.
#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.
9/
I implemented Payment Pointers (from scratch) in the Go programming-language.
https://github.com/reiver/go-pymtptr
Base on the specification I found before.
#CrowdBucks #FediDev #Fediverse #Golang #PaymentPointer #PeerTube #WebMonetization
Package pymtptr implements an Payment Pointers, for the Go programming language. Payment Pointers are used by the Interledger Protocol, Open Payments, and Web Monetization. - reiver/go-pymtptr
8/
PeerTube seems to have Payment-Pointers and Web-Monetization built-in already.
#CrowdBucks #FediDev #Fediverse #PaymentPointer #PeerTube #WebMonetization
7/
And, a description of the fields in the SPSP JSON seems to be here:
https://interledger.org/developers/rfcs/simple-payment-setup-protocol/#response-body
• destination_account
• shared_secret
• receipts_enabled
.
#CrowdBucks #FediDev #Fediverse #PaymentPointer #SimplePaymentSetupProtocol #SPSP #WebMonetization
6/
Actually, that screen-shot is part of a larger example.
It does seem as if what is returned from the HTTPS-URL that a Payment Pointer resolves to is indeed SPSP JSON.
https://interledger.org/developers/rfcs/simple-payment-setup-protocol/
.
#CrowdBucks #FediDev #Fediverse #PaymentPointer #SimplePaymentSetupProtocol #SPSP #WebMonetization
5/
I am wondering if maybe what is returned from the HTTPS-URL that a Payment Pointer resolves to is:
SPSP JSON
https://interledger.org/developers/rfcs/simple-payment-setup-protocol/
.
#CrowdBucks #FediDev #Fediverse #PaymentPointer #SimplePaymentSetupProtocol #SPSP #WebMonetization
If I have the following payment-pointer:
$example.com
That resolves to this HTTP URI:
https://example.com/.well-known/pay
What is expected to be at that URL?
JSON?
If "yes", what are the fields in that JSON?
(I looked here https://paymentpointers.org but couldn't find that information.)
Is it SPSP JSON (and only SPSP JSON) that is supposed to be returned?
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
@reiver ⊼ (Charles) 