Skip to main content

How to keep credit or debit card option in Android [closed]



I am doing a Application that contains debit card option. If the user wants to buy any burger or pizza we need to give him an option through debit card or credit card. I don't know exactly how to start this with this.





Can anyone please guide me on how to solve this problem?





Thanks in Advance


Comments

  1. Does the phone has NFC? Does it have a Wallet Application installed - such as Google Wallet?
    It's not sufficient if the phone has the wallet application; even the Merchants must have NFC enabled POS terminals that are either Paypass/Visawave certified.

    There are few trials conducted by Google. Not sure if it available globally. IMO, we are at least an year away before such infrastructure is available and resonably widely deployed.

    ReplyDelete

Post a Comment

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex