Sean started a discussion on the dev-identity list (https://lists.mozilla.org/listinfo/dev-identity). I really think this is the best way to do it for both developers as well as provide a better user experience.
It is really not fun trying to integrate 3rd party APIs to handle sign ins.
However, I would love to hear about the possible shortfalls of this approach.
Hmm, I don't think you are missing anything. I was wondering are there things I could do in order to improve the chance that the person on the other end will have the cash upon delivery?
I would imagine most people do want to pay for their order, however, they may forget to grab cash for their order or something along those lines.
So, keeping that in mind do you know if I as a provider could do things to help customers fulfill their orders as that would also help me a lot. I would imagine this is something others have dealt with and if I could learn from their implementations it would help a lot.
I'm not really familiar with how that works but doesn't the buyer still need to use a credit card or something to have money on their payondelivery account?
I would really like to be able to allow people to pay with cash but guarantee some sort of security that I would receive payment.
