Customers could use a iPod Touch + Card+Pin-Reader mounted in a case on the desk, using the iOS-Device only as a display and not as control-interface.
That's already working quite well, with the problem that the user can access the safari-controls - guided access is not possible because of the app-switching.
You could perhaps provide a basic-browser-app with no adress-bar, using the safari engine and there would be no adressbar showing the via <META HTTP-EQUIV="refresh”> every second updating page – this page is in case of a payment filled with the URL=izettle://x-callback-url... in the header, so there would be an automatic launch of the iZettle-App to process the payment, explaining that card-insertion is required now and so on...
Right now via web-app it’s possible to call the originating page without safari-user-interface – but I found no way to x-callback to the web-app – I think because there is no such way.
As I said, the META-Refresh is working quite well already.
Customers could use a iPod Touch + Card+Pin-Reader mounted in a case on the desk, using the iOS-Device only as a display and not as control-interface.
That's already working quite well, with the problem that the user can access the safari-controls - guided access is not possible because of the app-switching.
You could perhaps provide a basic-browser-app with no adress-bar, using the safari engine and there would be no adressbar showing the via <META HTTP-EQUIV="refresh”> every second updating page – this page is in case of a payment filled with the URL=izettle://x-callback-url... in the header, so there would be an automatic launch of the iZettle-App to process the payment, explaining that card-insertion is required now and so on...
Right now via web-app it’s possible to call the originating page without safari-user-interface – but I found no way to x-callback to the web-app – I think because there is no such way.
As I said, the META-Refresh is working quite well already.
So, that's my last proposal for enhancement! ;-)