#paymentpointer — Public Fediverse posts

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

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

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

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

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

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

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

8/

PeerTube seems to have Payment-Pointers and Web-Monetization built-in already.

#CrowdBucks #FediDev #Fediverse #PaymentPointer #PeerTube #WebMonetization

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

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

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

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

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

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

3/

I was looking around for a specification for Web Monetization Payment-Pointers. The closest thing I could find is this:

https://paymentpointers.org/

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

3/

I was looking around for a specification for Web Monetization Payment-Pointers. The closest thing I could find is this:

https://paymentpointers.org/

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

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

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

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:

https://reiver.link

Then I could let people people pay me with this Payment-Pointer:

$reiver.link

#CrowdBucks #FediDev #Fediverse #PaymentPointer #WebMonetization

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:

https://reiver.link

Then I could let people people pay me with this Payment-Pointer:

$reiver.link

#CrowdBucks #FediDev #Fediverse #PaymentPointer #WebMonetization