W3C home > Mailing lists > Public > public-payments-wg@w3.org > May 2016

Re: [w3c/webpayments] Clarify the concepts of enabled vs. supported (#132)

From: Adrian Hope-Bailie <notifications@github.com>
Date: Fri, 27 May 2016 09:32:18 -0700
To: w3c/webpayments <webpayments@noreply.github.com>
Message-ID: <w3c/webpayments/pull/132/r64931958@github.com>
> -            appropriate to process a given payment request.</p>
> +        <p>For a given <a>payment method</a> supported by a given <a>payment
> +            app</a>, the <a>payment method</a> can be in one of two states:</p>
> +        <dl>
> +            <dt><dfn id="payment-app-enabled-payment-method">enabled</dfn></dt>
> +            <dd>
> +                <p>A <a>payment app</a> can define a payment method as <a>enabled
> +                    </a> by adding it to the <code><a>enabled_methods</a></code>
> +                    list. If a payment app defines a payment method as <a>enabled
> +                    </a>, then it MUST be able to process any payment
> +                    request that lists that payment method as supported and is
> +                    formatted correctly according to the <a>payment method
> +                    specification</a> for that payment method.</p>
> +                <p>A <a>user agent</a> SHOULD NOT define a payment method as <a>
> +                    enabled</a> unless one of the following criteria is met:
> +                    </p>

What does it mean for a **user agent** to define a payment method as enabled? The user agent doesn't know anything except what the payment app tells it during registration.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Received on Friday, 27 May 2016 16:33:11 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 May 2016 16:33:11 UTC