Quote Originally Posted by swguy View Post
Would it make sense to do a check for Safari before enabling Apple Pay? If you're using Chrome, you get this console error:

square.js:3 Initializing Apple Pay failed PaymentMethodUnsupportedError: Method unsupported: Apple Pay is only available on Safari.
at new Wf (square.js:3:375247)
at Yf (square.js:3:383212)
at square.js:3:386948
at Generator.next (<anonymous>)
at Jf (square.js:3:383366)
at a (square.js:3:383570)
i'll add it to my list, but truly very low priority.

wrong totals getting sent to the payment processor because the $order->info object is incorrect at the time the data should be handled is far greater priority and something that really makes little sense to me.

why is there a checkout payment page if the base ZC can not provide the correct totals?