Apple implements interledger in safari on iOS

[Hodlezerper]

38 minutes ago, mandelbaum said:

So, Interledger Protocol might be the future chosen value protocol for the entire consumer ecosystem of Apple? Apple pay is a pretty much a competitor to creditcards right?

Not really. It uses credit cards.

 

for clarification, it can probably use whatever the hell you throw at it...just has to be Apple approved, legal, etc

 

i want nothing more than for interledger and XRP to allow me to text money to anyone in any currency

Edited April 7, 2018 by Hodlezerper

[Hodlezerper]

31 minutes ago, Zedy44 said:

On it with the Jifs tonight. 

Jk jk 

 

gifs

[Guest]

Wow, Just WOWWW

[TexasHodlem]

Something that should be made clear to readers: the payment request API has NOTHING (directly) to do with ILP, Ripple, or XRP. It's simply a way for websites to request data from clients via the browser. In the past, you've had to type in your name, billing address, shipping address, credit card/account number into every website you purchased through. AutoComplete has made this a bit more convenient, but it can still be a frustrating experience, and it requires every site designing a different form to input the data. The payment request API uses javascript in the browser to create a payment request. An installed wallet application (Google/Apple/Miscrosoft wallet app) on the device automatically provides the data, prompting the user for selections as needed in a standard way that's the same across all sites implementing the feature. It's going to be HUGE for businesses getting more mobile sales, and way more convenient for people using mobile devices to acquire goods and services.

The payment request can specify which types of payment are accepted. For instance, if you have a VISA and MasterCard in your mobile wallet, then the site requests a payment saying that they only accept VISA, the application is smart enough to auto-select your VISA card. Where the ILP component comes in is when the site is set up to receive payments through this protocol. Feasibly, if your bank has joined RippleNet (ILP network), there could come a time where your wallet application sends an ILP payment from your bank account to the merchant. If the merchant accepts a different currency than is in your bank account, the payment would be routed from your bank through the appropriate ILP connectors. One example route might be from your PHP bank account to a PHP/XRP connector to a XRP/JPY connector if you were in the Philippines and ordering from Japan.

ILP + payment request API = pay with whatever ILP connected source you have (bank, crypto, mobile wallet, etc) to whatever the website accepts without ever having to fill in a form or worry about any of the details. It'll allow for visiting a new website, pressing "Buy Now" and having your order complete in seconds. Welcome to the future.

[Guest]

1 minute ago, TexasHodlem said:

Something that should be made clear to readers: the payment request API has NOTHING (directly) to do with ILP, Ripple, or XRP. It's simply a way for websites to request data from clients via the browser. In the past, you've had to type in your name, billing address, shipping address, credit card/account number into every website you purchased through. AutoComplete has made this a bit more convenient, but it can still be a frustrating experience, and it requires every site designing a different form to input the data. The payment request API uses javascript in the browser to create a payment request. An installed wallet application (Google/Apple/Miscrosoft wallet app) on the device automatically provides the data, prompting the user for selections as needed in a standard way that's the same across all sites implementing the feature. It's going to be HUGE for businesses getting more mobile sales, and way more convenient for people using mobile devices to acquire goods and services.

The payment request can specify which types of payment are accepted. For instance, if you have a VISA and MasterCard in your mobile wallet, then the site requests a payment saying that they only accept VISA, the application is smart enough to auto-select your VISA card. Where the ILP component comes in is when the site is set up to receive payments through this protocol. Feasibly, if your bank has joined RippleNet (ILP network), there could come a time where your wallet application sends an ILP payment from your bank account to the merchant. If the merchant accepts a different currency than is in your bank account, the payment would be routed from your bank through the appropriate ILP connectors. One example route might be from your PHP bank account to a PHP/XRP connector to a XRP/JPY connector if you were in the Philippines and ordering from Japan.

ILP + payment request API = pay with whatever ILP connected source you have (bank, crypto, mobile wallet, etc) to whatever the website accepts without ever having to fill in a form or worry about any of the details. It'll allow for visiting a new website, pressing "Buy Now" and having your order complete in seconds. Welcome to the future.

honestly i don't care either way, the technology is being used. GREAT PROGRESS

[OzAlphaWolf]

Actually, to go one step back, the W3C Payment Request standard is not ILP itself. The ILP is interoperable with this standard but does not have to be used itself. The way the standard is enacted in browsers is that it can be set up so that any payment system (including ILP based ones) can be easily configured.

[XRPisVELOCITY]

Dejavu

[Ralphadayus]

56 minutes ago, Tehol_Beddict said:

I think the reddit mods don’t like me much. Anyone care to post this?

I would but I got banned yesterday, lol. 

[Harfang]

Sticking to the plan. Moving forward as intended. Not many other crypto assets, if any can,  compare when it comes to announcements in regards to infrastructure building, partnerships and implementation. 

Thank you Tehol for another interesting and constructive post.

Edited April 7, 2018 by Harfang

[Hodlezerper]

21 minutes ago, TexasHodlem said:

Something that should be made clear to readers: the payment request API has NOTHING (directly) to do with ILP, Ripple, or XRP. It's simply a way for websites to request data from clients via the browser. In the past, you've had to type in your name, billing address, shipping address, credit card/account number into every website you purchased through. AutoComplete has made this a bit more convenient, but it can still be a frustrating experience, and it requires every site designing a different form to input the data. The payment request API uses javascript in the browser to create a payment request. An installed wallet application (Google/Apple/Miscrosoft wallet app) on the device automatically provides the data, prompting the user for selections as needed in a standard way that's the same across all sites implementing the feature. It's going to be HUGE for businesses getting more mobile sales, and way more convenient for people using mobile devices to acquire goods and services.

The payment request can specify which types of payment are accepted. For instance, if you have a VISA and MasterCard in your mobile wallet, then the site requests a payment saying that they only accept VISA, the application is smart enough to auto-select your VISA card. Where the ILP component comes in is when the site is set up to receive payments through this protocol. Feasibly, if your bank has joined RippleNet (ILP network), there could come a time where your wallet application sends an ILP payment from your bank account to the merchant. If the merchant accepts a different currency than is in your bank account, the payment would be routed from your bank through the appropriate ILP connectors. One example route might be from your PHP bank account to a PHP/XRP connector to a XRP/JPY connector if you were in the Philippines and ordering from Japan.

ILP + payment request API = pay with whatever ILP connected source you have (bank, crypto, mobile wallet, etc) to whatever the website accepts without ever having to fill in a form or worry about any of the details. It'll allow for visiting a new website, pressing "Buy Now" and having your order complete in seconds. Welcome to the future.

Excellent overview. Thank you.

Is this your field?

[TexasHodlem]

9 minutes ago, Hodlezerper said:

Excellent overview. Thank you.

Is this your field?

"Software Engineer" is my official title, but I'm a bit of a hack. I was very interested when I saw W3C adding the feature, so I did some digging a while back. This video is WONDERFUL and totally worth your time if you want to know more. You'll notice my points about the API can be credited to this talk.

That one's long. If you just want a client side perspective, watch this one. Don't blink, or you'll miss the demo checkout process.

If you like Microsoft better then Google, they have a wallet demo too:

 

Edited April 7, 2018 by TexasHodlem
#grammarNazi

[invest2lose]

so how big is this news on a scale of 1-10?

[Tehol_Beddict]

36 minutes ago, TexasHodlem said:

Something that should be made clear to readers: the payment request API has NOTHING (directly) to do with ILP, Ripple, or XRP. It's simply a way for websites to request data from clients via the browser. In the past, you've had to type in your name, billing address, shipping address, credit card/account number into every website you purchased through. AutoComplete has made this a bit more convenient, but it can still be a frustrating experience, and it requires every site designing a different form to input the data. The payment request API uses javascript in the browser to create a payment request. An installed wallet application (Google/Apple/Miscrosoft wallet app) on the device automatically provides the data, prompting the user for selections as needed in a standard way that's the same across all sites implementing the feature. It's going to be HUGE for businesses getting more mobile sales, and way more convenient for people using mobile devices to acquire goods and services.

The payment request can specify which types of payment are accepted. For instance, if you have a VISA and MasterCard in your mobile wallet, then the site requests a payment saying that they only accept VISA, the application is smart enough to auto-select your VISA card. Where the ILP component comes in is when the site is set up to receive payments through this protocol. Feasibly, if your bank has joined RippleNet (ILP network), there could come a time where your wallet application sends an ILP payment from your bank account to the merchant. If the merchant accepts a different currency than is in your bank account, the payment would be routed from your bank through the appropriate ILP connectors. One example route might be from your PHP bank account to a PHP/XRP connector to a XRP/JPY connector if you were in the Philippines and ordering from Japan.

ILP + payment request API = pay with whatever ILP connected source you have (bank, crypto, mobile wallet, etc) to whatever the website accepts without ever having to fill in a form or worry about any of the details. It'll allow for visiting a new website, pressing "Buy Now" and having your order complete in seconds. Welcome to the future.

 

[Trader-to-the-Crown]

1 hour ago, OzAlphaWolf said:

XRP does not have to be used. But it is the native currency on the ILP which makes it the fastest and cheapest settlement option.

Internet... Interledger...

Ripple did it. This is huge. The Interledger is the Internet of Value. The Internet of Money. And XRP is poised to be the key to it all.

Interledger. This is going to be a big and powerful word.

Edit: I'm not just hearing about the Interledger, but the reality of how big this is, is starting to sink in.

Edited April 7, 2018 by Trader-to-the-Crown

[Hodlezerper]

56 minutes ago, Quintree said:

I see your connection here, but it seems weak. None of the recent documents that I looked at mentioned interledger or Ripple. It was just that draft document back in February that mentioned it. Show me a recent document showing the implementation of interledger on W3C Safari. 

*looks around nervously*