[blink-dev] Re: Intent to Prototype: Link rel=payment to support push payments

['Junhui He' via blink-dev]

The public version of HTML payment link design doc is available at
bit.ly/html-payment-link-dd.

On Wed, May 8, 2024 at 11:57 AM Junhui He  wrote:

> WICG proposal was sent out at https://github.com/WICG/proposals/issues/150
>
> On Wed, May 8, 2024 at 11:03 AM Junhui He  wrote:
>
>> Contact emailsaneesh...@google.com, junhu...@google.com
>>
>> Explainer
>> https://github.com/aneeshali/paymentlink/blob/main/docs/explainer.md
>>
>> Summary
>>
>> Adds support for  as a hint that the
>> browser should notify registered payment clients about a pending push
>> payment. When Blink encounters this HTML element, then it will send a
>> message to the browser to display the user's interface to ask the user if
>> they would like to invoke Google Pay to assist payments on this page.
>>
>> Blink componentBlink>Payments
>> 
>>
>> Motivation
>>
>> This feature lets the browser assist users in push-based payment flows by
>> facilitating the transfer of payment information between the payment
>> provider (on the payee side) and the payment client (on the payer side).
>> The feature lays the foundation for payment integrators in streamlining
>> push-based payment flows, towards a consistent and low-friction user
>> experience.
>>
>> Risks
>> Interoperability and Compatibility
>>
>> We're not aware that anybody else uses payment link .
>>
>> *Gecko*: No signal
>>
>> *WebKit*: No signal
>>
>> *Web developers*: No signals
>>
>> WebView application risks
>>
>> Does this intent deprecate or change behavior of existing APIs, such that
>> it has potentially high risk for Android WebView-based applications?
>>
>> None
>>
>> Flag name on chrome://flags#enable-payment-link-detection
>>
>> Finch feature name"EnablePaymentLinkDetection"
>>
>> Requires code in //chrome?True - Detection of the payment link does not
>> need coding //chrome, but code in //chrome will eventually be required to
>> invoke Google Pay APIs.
>>
>> Tracking bughttps://crbug.com/1477049
>>
>> Estimated milestones
>>
>> M132
>>
>> Link to entry on the Chrome Platform Status
>> https://chromestatus.com/feature/5198846820352000?gate=5076188191522816
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to blink-dev+unsubscr...@chromium.org.
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAAgNxUvjY%2BW0%3D1YxXDKZr%2BUr0L%2B5%2Bbm-jTXbw0_zy_RZ5kCdLQ%40mail.gmail.com.

[blink-dev] Re: Intent to Prototype: Link rel=payment to support push payments

['Junhui He' via blink-dev]

WICG proposal was sent out at https://github.com/WICG/proposals/issues/150

On Wed, May 8, 2024 at 11:03 AM Junhui He  wrote:

> Contact emailsaneesh...@google.com, junhu...@google.com
>
> Explainer
> https://github.com/aneeshali/paymentlink/blob/main/docs/explainer.md
>
> Summary
>
> Adds support for  as a hint that the
> browser should notify registered payment clients about a pending push
> payment. When Blink encounters this HTML element, then it will send a
> message to the browser to display the user's interface to ask the user if
> they would like to invoke Google Pay to assist payments on this page.
>
> Blink componentBlink>Payments
> 
>
> Motivation
>
> This feature lets the browser assist users in push-based payment flows by
> facilitating the transfer of payment information between the payment
> provider (on the payee side) and the payment client (on the payer side).
> The feature lays the foundation for payment integrators in streamlining
> push-based payment flows, towards a consistent and low-friction user
> experience.
>
> Risks
> Interoperability and Compatibility
>
> We're not aware that anybody else uses payment link .
>
> *Gecko*: No signal
>
> *WebKit*: No signal
>
> *Web developers*: No signals
>
> WebView application risks
>
> Does this intent deprecate or change behavior of existing APIs, such that
> it has potentially high risk for Android WebView-based applications?
>
> None
>
> Flag name on chrome://flags#enable-payment-link-detection
>
> Finch feature name"EnablePaymentLinkDetection"
>
> Requires code in //chrome?True - Detection of the payment link does not
> need coding //chrome, but code in //chrome will eventually be required to
> invoke Google Pay APIs.
>
> Tracking bughttps://crbug.com/1477049
>
> Estimated milestones
>
> M132
>
> Link to entry on the Chrome Platform Status
> https://chromestatus.com/feature/5198846820352000?gate=5076188191522816
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to blink-dev+unsubscr...@chromium.org.
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAAgNxUv4GLkB3xiUo1TO3p6ravcGapKAxFPnAp9f_NjbT8DVRQ%40mail.gmail.com.