Pull Payments

Protocol Design
, , ,
41

I can start a channel in the Interledger slack workspace.

1 Like
42

awesome idea. Iā€™ll have to dust off my slack credentials

43

@JasonArmbruster letā€™s chatā€¦

Weā€™re working to enable something like this for Coil subscriptions and are keen to extend this to be more generally useful.

Created the Slack channel:
https://interledger.slack.com/archives/CJRSD0NQY/p1558029719000300

44

Im on my way over ā€¦ Adrian, I follow you on Twitter, follow back?

45

@adrianhopebailie it does seem that you must invite me. my email is fxjason at gmail dot com

46
48

Hi @johnsmith101 and welcome!

You are correct. Anybody that learns about a pull payment pointer can potentially pull from it. I have been thinking about adding an auth layer to any payment (because you may want to know where your money is coming from, too) but especially to pull payments. @adrianhopebailie, @matdehaast, and @don have been working on delegated payments which include an auth flow. Additionally, there is a new RFC in the works on Interledger HTTP Authentication Profiles.

49

Weā€™ve started to document our POC as a protocol weā€™ve called Open Payments (OPay) which is based on OAuth for authorization.

https://github.com/adrianhopebailie/open-payments

1 Like
51

how to do fixed source amount payments with invoices ?

52

Hi @roundcubefour and welcome!

This is a bit off topic since this thread is about Pull Payments, not Invoices, but anyways.

We are not concerned about fixed source amount payments in invoices since it is assumed that the merchant wonā€™t mark an invoice as complete if they do not receive the amount they requested and hence they wonā€™t fulfill the contract. Consequently, we focus on fixed destination amount payments, which are handled at the transport layer (STREAM).

@kincaid gives a great summary here.

1 Like
53

Itā€™s not entirely clear right now how to do fixed source amount payments or tips using Open Payments. As Sabine noted, invoices are more tailored for a fixed receive amount. But we should be able to support this; I think @matdehaast suggested overpaying an invoice with an unspecified or 0 amount.

Hereā€™s a relevant issue: https://github.com/interledger/open-payments/issues/39