So the CurrentC people are trying to assure CurrentC's future by pissing off the very same companies that they need to authorise their app? That seems like they're shooting themselves in the foot.
What are they going to do if Apple in particular rejects CurrentC as an app? Do it via HTML5/WebKit? Cannot see the user experience on that being particularly good.
Plus as people on Reddit pointed out, with Apple Pay/Google Wallet, the liability for fraud is still with the banks. With CurrentC you MIGHT be liable for any fraud in the US (because of how credit and debit fraud is handled).
PS - The name "CurrentC" is just terrible. Least memorable name ever. They should have just called it "Vanilla."
What are they going to do if Apple in particular rejects CurrentC as an app? Do it via HTML5/WebKit? Cannot see the user experience on that being particularly good.
Plus as people on Reddit pointed out, with Apple Pay/Google Wallet, the liability for fraud is still with the banks. With CurrentC you MIGHT be liable for any fraud in the US (because of how credit and debit fraud is handled).
PS - The name "CurrentC" is just terrible. Least memorable name ever. They should have just called it "Vanilla."