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<mailto:laura.townsend@merchantadvisorygroup.org>
[cid:image001.png@01D33C65.F02D4B20]
