question

I'm building a merchant-specific Android application for creating orders in their proprietary invoice/inventory system/database. Clover does not allow merchant-specific Android applications. In a support email conversation, @Lilly suggested I use a Web-app and the Clover REST API.

I built a little test app using the Android OAuth Example and successfully got back the Access/API token. I have a few clarification questions about (hopefully) using this token in my Android app.

1. The token expires after one year, correct? I will, of course, build in error trapping to catch when it expires.
2. Is the token tied to that merchant account? Is there a single token per merchant? In other words, if the merchant is using 5 Clover stations, can REST calls from those 5 stations use that single token?
3. This is probably more for @Raymond Lee... Am I wrong in thinking that I can use that API token to build http REST calls in my Android code in order to Create Orders and get Payment Information (really the only two things I need from Clover since the app passes off to Intent com.clover.intent.action.PAY with OrderId for the actual payment transaction).

In short, can I use an API-token for REST API calls in an Android app (side-loaded and not from the Clover App Market) that does not include the Clover SDK in order to create orders and pull payment information?