Re: [w3c/payment-handler] "Middleman Id/Commission %/Payeeer" provision (#335)

Cheers @ianbjacobs 

@adrianhopebailie Mate, really appreciate the feedback and the time it took to provide! You people are really accommodating here at Payments.

> I think so, if we are talking about the same thing. If you look at my example code, 
> there are 3 payment methods that the merchant accepts and all have different 
> ways of expressing split disbursement.
> 
> That example would work with the API as it is today. No changes needed.

I am in %100 agreement with you (except for rugby, cricket, and how to pronounce vowels :-)

The problem I have is that you're dreaming when it comes to MethodData volatility. No one would be happier than I to be corrected! If this is a scratchpad between Merchant and PH then "You Bewdy!" Having read the specs numerous times I think not :-(

> I.e. If Fred chose Square then why would SMC call PR API with options for the rider to 
> pay via PayPal?

No one is suggesting this.

> If you are talking about the rider paying via PayPal and Fred still getting paid via Square 
> then we're in a whole new regulatory realm where someone is acting as an intermediary 
> and receiving the funds via PayPal first before making the payout via Square.
> 
> That's not in scope for us.

Agreed. Fantasy land out-of-scope!

> I don't agree with this.

Yes but you're continually putting out fires with "Who owns the shipping address" or "Sales Tax or GST calculated at PH".

> TL;DR: I support the use case and think it could be very popular but I think it's 
> doable today without needing to make any changes to the API.

TL;DR agree with the sentiment but it is *NOT* available today.

Sadly, I still don't understand what you mean by 1. and 2.? Or more importantly which you says is deprecated or old-fashioned. I eat out a lot and catch Uber but don't understand what you are saying.


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/payment-handler/issues/335#issuecomment-493969228