title: Way to expose appstore IDs but keep them secured for release
body: <p>I am working on an application that will allow the user to purchase content from the app store
  <a href="https://developer.apple.com/library/mac/#documentation/NetworkingInternet/Conceptual/StoreKitGuide/Introduction/Introduction.html#//apple_ref/doc/uid/TP40008267-CH1-SW1" rel="nofollow">https://developer.apple.com/library/mac/#documentation/NetworkingInternet/Conceptual/StoreKitGuide/Introduction/Introduction.html#//apple_ref/doc/uid/TP40008267-CH1-SW1</a></p>
  
  <p>These products require a "ProductID" that ties them to whatever is in the appstore.</p>
  
  <p>I will need to store these IDs somewhere in the application so I know what to send the server when the purchase button is clicked.</p>
  
  <p>I wish to expose these ID's and allow non-programmers to enter any ID they want in both our side and the server side, and not have to call on a programmer to go into the code and change some enum.</p>
  
  <p>I figured a config file would not be very secure, for in the end it's just a text file that a user could potentially view after purchasing the app. May not be a huge problem if a user saw the ID, but I don't like the idea of anybody seeing the innards that go through a payment process</p>
  
  <p>Assuming im making sense here, whats a good way to expose these IDs but still keep them secure so users may not find them?</p>
  
  <p>Also curious, how secure is something like an enum in c++? Can people break the .exe down and see the code and its values?</p>