Michiel de Jong michielbdejong

I thought the following Dutch services for user-to-user payment requests were all quite interesting developments, once you have thought about how we design Interledger Payment Requests and the W3C Payment Request API:

There's a new service for sending payment requests in the Netherlands: https://tikkie.me/ It's super simple, you get a link to a payment URL that uses the Dutch iDEAL system, to which all Dutch banks are connected. iDEAL has existed for years and people use it a lot to pay things online; usually the options would be creditcard, paypal, iDEAL. iDEAL is just a redirector service: Pick your bank, and it redirects you to your own online banking. The tikkie link can be pasted in WhatsApp or other chat/email channels. It's really taken off and I heard people mention it quite a lot, quite suddenly.

This is a response to Evan's question on Slack:

[what is the] main argument against removing connector-implemented quoting protocols

Interesting question! I still think the three main design principles of Interledger are:

we only care about payments
the complexity is in the connectors
users trust their own ledger; connectors are trustless

Alice wants Bob's balance on ledger B to go up by a certain amount. She trusts Bob to report whether this has happened or not. She is willing to pay a translated amount from her balance on ledger A, but if that

	[michiel@mbp ~]$ mkdir exampleForDavid
	[michiel@mbp ~]$ cd exampleForDavid/
	[michiel@mbp ~/exampleForDavid]$ npm install ilp-packet
	npm WARN saveError ENOENT: no such file or directory, open '/Users/michiel/exampleForDavid/package.json'
	npm notice created a lockfile as package-lock.json. You should commit this file.
	npm WARN enoent ENOENT: no such file or directory, open '/Users/michiel/exampleForDavid/package.json'
	npm WARN exampleForDavid No description
	npm WARN exampleForDavid No repository field.
	npm WARN exampleForDavid No README data
	npm WARN exampleForDavid No license field.