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

Re: [webpayments] ACTION: Summarize arguments for/against shipping address capture (#72)

From: fredMeignien <notifications@github.com>
Date: Fri, 12 Feb 2016 02:26:42 -0800
To: w3c/webpayments <webpayments@noreply.github.com>
Cc: webpayments <public-payments-wg@w3.org>
Message-ID: <w3c/webpayments/issues/72/183263538@github.com>
I agree with @adrianba's points too.
I would add the following: if we consider that the concept of check-out is the phase where the consumer must be obtained in a reliable way, secured for all parties, then the shippind address belongs to the key elements of consent; otherwise it would mean that a payment may be initiated with Billing address = Null, and then give room to an issue between Payer and Payee (for instance: "I never received the goods so I reject the payment"). In other words, the consumer might "withdraw his consent" using the billing address issue.
This consideration does not imply, of course, a specific technical solution, but the idea is that the billing address has to be encapsulated before payment request is generated.
In the VISA Direct API named "Create a Sales Transaction", this address is mandatory: https://developer.visa.com/products/cybersource/reference#cybersource__cybs__v1__create_sales_transaction

Reply to this email directly or view it on GitHub:
Received on Friday, 12 February 2016 10:27:48 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:43:14 UTC