3 ms·
That's because there is no open standard for it, which is mentioned in the following sentence. > A room of computer science students could write an open standa
by kroltan 5y ago
That's because there is no open standard for it, which is mentioned in the following sentence.
> A room of computer science students could write an open standard for that in like a month and have a working implementation within the year.
(While I don't share the optimism regarding the timeframe, I agree with the general sentiment)
- jaywalk 5y agoThere are standards, however making them "open" wouldn't change anything. You've obviously never tried to integrate with a large number of separate entities before.
- kroltan 5y agoI have not, I've just clarified the point of the parent in case you misread. But now I'm curious, what are the challenges with having a large number of entities implement a standard? Is it "just" the shrink-wrap effect of having a few-initial or large players, is it getting the parties involved to even agree to the standard, or what?
- jaywalk 5y agoYou are talking about a many-to-many relationship here. Every payment processor has to ensure their system works with every bank, and vice versa. So the standard defines the data format, great. What happens when Payment Provider #223 has an issue communicating with Bank #16252? On an even bigger scale, who is going to maintain all of the necessary technical info for the parties to all interoperate? Who will handle fraud detection? Who will be liable for fraud that goes undetected? Credit card companies handle all of that and much more in exchange for transaction fees.