Skip to main content
Samsung Developer Program

IAP Operating Modes and Beta Testing

Samsung In-App Purchase (IAP) can operate in three modes: two modes to support Android app development testing that do not result in actual financial transactions, and a release production mode that does result in actual financial transactions.

 

Samsung IAP supports app integration testing during development, and supports normal operations, including beta testing, after app development. You beta test your app and its in-app items either before submitting them for validation testing, or after they have passed.

IAP Operating Modes

IAP operating modes fundamentally control in-app item functions:

  • After calling getInstance() to instantiate the Helper object, call setOperationMode() to set the operating mode.
  • During Android app development and testing:
    • You must ensure actual financial transactions do not occur by setting either of two developer test modes.
    • We recommend you test your Android app under various conditions in both test modes.
  • Before validation submission, you must set the production mode to ensure actual financial transactions do occur.
  • When apps are distributed in a test mode, the following pop-up message is displayed. 
    SamsungIAP_TestModeDistributionPopup.png
     

Production Mode

Normal operating mode

  • In-app items can be retrieved, purchased, and consumed.
  • IAP Helper purchase requests:
    • Are processed as specified and may succeed or fail.
    • Successful in-app item purchases result in actual financial transactions (such as billing end-user credit cards) when:
      • The Android app is registered, validated, and being distributed in the Galaxy Store.
      • In-app items are registered and validated.
         
  • All other IAP Helper requests are processed as specified and may succeed or fail.
  • Production mode must be set:
    • After development testing has been completed.
    • Before submitting your Android app and its in-app items for beta release or validation testing.
       
  • Production mode is set by the following API call:
    mIapHelper.setOperationMode(OperationMode.OPERATION_MODE_PRODUCTION);

Caution:  When an Android app is distributed in production mode:

  • IAP Helper purchase requests:
    • Will not result in actual financial transactions. 
    • Result in displaying an Unknown Error popup.
      SamsungIAP_Overview_UnknownErrorPopup_Screenshot.png
       

Developer Test Mode

 

Testing mode that reports successful or failure results.
Failure can be caused by: improper coding or registration, or from network interruptions.

  • In-app items can be retrieved, purchased, and consumed.
  • IAP Helper purchase requests:
    • Are processed as specified and always report successful results.
    • Do not result in actual financial transactions.
       
  • All other IAP Helper requests are processed as specified and always report successful results.
  • Developer test mode is to be set only during development testing.
  • Developer test mode is set by the following API call:
    mIapHelper.setOperationMode(OperationMode.OPERATION_MODE_TEST);

     

Developer Test Mode (Failure)

Testing mode that always reports failed results

  • In-app items cannot be retrieved, purchased, or consumed.
  • All IAP Helper requests are not processed and are reported as having failed.
    Note: In-app item purchase requests do not result in actual financial transactions.
  • Developer test mode (failure) mode is to be set only during development testing.
  • Developer test mode is set by the following API call:
    mIapHelper.setOperationMode(OperationMode.OPERATION_MODE_TEST_FAILURE);
    

 

Beta Testing

The Samsung ecosystem supports distribution of your beta release Android app and its in-app items under closed beta testing conditions, which limits app download and in-app item purchase to registered beta testers, and controls the payment of fees. 


In closed beta testing:

  • You:
    • Register your free or paid Android app and its in-app items.
    • Register beta test information:
      • The Samsung Account name of up to 1000 beta testers.
      • The URL where testers can send you feedback
      • When beta testing starts and ends.
         
    • Submit your app for beta test release.
    • Send your beta testers the URL where they can download your app.
    • Respond to beta tester feedback that they provide in beta app product detail page in the Samsung Galaxy Store, or to your beta testing feedback channel address
    • Can stop beta testing before it is scheduled to end by suspending the distribution of your app.
       
  • Galaxy Store
    • Distributes your app under beta release conditions.
    • Only enables app download and in-app item support for registered beta testers between beta test start and stop dates or before you suspend it.
    • After beta testing, disables app download and in-app item support.
       
  • Beta testers:
    • Must have Samsung Galaxy phone devices with the proper Galaxy Store Client versions.
      • Galaxy phones must have installed Galaxy Store Client version 4.1.03-1 or higher.
      • Android phones must have installed Galaxy Store Client version 4.2.04 or higher.
         
    • During beta testing:
      • Must follow the beta-test URL and use their registered Samsung Account name to download the app.
      • Paid apps are downloaded for free.
      • Must use their registered Samsung Account name to get in-app items.
         
    • After suspension of beta testing:
      • Cannot download the app or get in-app items.
      • Can continue to use a previously downloaded app and purchased in-app items.
         

For more details about open and closed beta testing, see Beta Testing.

  • Was this article helpful?