W3C home > Mailing lists > Public > public-payments-wg@w3.org > October 2017

Re: Input on "origin"

From: Ian Jacobs <ij@w3.org>
Date: Tue, 3 Oct 2017 15:40:12 -0500
Cc: "public-payments-wg@w3.org" <public-payments-wg@w3.org>
Message-Id: <3F6E5F28-DD8B-47AF-8E76-A12E29A8D15C@w3.org>
To: Laura Townsend <Laura.Townsend@merchantadvisorygroup.org>
Hi Laura,

Thanks for the comment, which I will link from the relevant payment handler issue:
  https://github.com/w3c/payment-handler/issues/217

Ian


> On Oct 3, 2017, at 3:37 PM, Laura Townsend <Laura.Townsend@merchantadvisorygroup.org> wrote:
> 
> I wanted to contribute input on use cases to enable the payment app origin in the response data for web-based payment apps.
>  
> Merchants would like this type of “origin” information to enable the ability to manage their risk (ie. Payment types that have a significantly higher fraud chargeback rate), identify and address poor performance that don’t meet SLA’s, and enable partnership opportunities for promotions, offers, or discounting based on payment type or “origin”.  
>  
> These are just a few use cases for which an “origin” could support – all of which are to enhance the customer experience (with the exception of bad issuer behaviors or customer behaviors around fraud … which should be addressed with a balance of customer experience and risk management).  
>  
> Merchants aren’t asking for the spec to make the decisions on behalf of the merchant.  We are simply in need of a spec that offers flexibility.
>  
> Laura Townsend
> SVP Operations
> Merchant Advisory Group
> 630.362.0367 | cell
> laura.townsend@merchantadvisorygroup.org
> <image001.png>
>  
>  

--
Ian Jacobs <ij@w3.org>
https://www.w3.org/People/Jacobs/
Tel: +1 718 260 9447
Received on Tuesday, 3 October 2017 20:40:23 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 3 October 2017 20:40:23 UTC